Hey everyone! I'm a developer and DevOps engineer who's getting really tired of the hassle that comes with internal DNS in development and staging environments. So, I'm working on a project to create a multi-tenant private DNS service with an API that aims to make DNS management as simple as using `/etc/hosts`, but with added features like access control, logging, and scalability for teams. It's still in the works, and I'd love your thoughts.
From my experience, this tool could help alleviate issues like:
- Reducing dependence on public DNS servers or intricate configurations with tools like Consul.
- Providing a transparent audit trail for who resolved or modified entries.
- Isolating domains by different projects or teams.
Does this sound like something that resonates with you? What are some of the major frustrations you face with DNS management and service discovery? I're eager for your feedback!
5 Answers
What specific problems does your tool address that Infrastructure as Code doesn’t? In our setup, we only allow DNS changes through code that is triggered via a pipeline and peer reviewed. This works great with Cloudflare for us.
We usually just create subdomains for each team and let them manage it however they want, often with Terraform. The hosting provider doesn't really matter in our workflows.
Have you ever faced challenges with isolating domains for teams? That’s what I'm trying to improve on!
Before diving into a new solution, make sure the problem isn't already solved—sometimes the community has already tackled these issues.
I've done my homework, and it seems like there's a real gap in tools that cater specifically to my use case. But I really want your honest critiques!
Honestly, how is just adding another configuration file simpler than using a zone file? It feels like you might be making things more complicated instead! Please reconsider this approach.
I feel your concern! But the goal is to simplify DNS management in transient environments; sometimes traditional methods don’t cut it for rapid development cycles.
Decentralizing DNS might seem odd at first. Have you considered tools like BIND? It's a tried and tested solution. For audit trails, using infrastructure as code might be worth considering—Terraform with Git repos can provide version control and peer review. And as for isolating domains, unique hosted zones might suffice. It sounds like you're trying to reinvent the wheel a bit.
I appreciate your feedback! BIND and Terraform are great for static infrastructure, but I'm focusing on dynamic environments like dev and staging where speed is crucial. Think of my tool as `/etc/hosts` with team permissions and logging—something BIND doesn’t offer out-of-the-box. It's aimed at making the messy middle before production smoother.
I get where you're coming from! I want to create a more flexible environment that fits dynamic setups, unlike manual processes that can bog things down.