How to manage internal DNS without running a domain controller
Retaining traditional domain controllers solely for local network name resolution creates unnecessary complexity and overhead for on-prem environments. This leaves administrators struggling to manually sync records across multiple sites when hardware or legacy servers are phased out.
What people tried
Every workaround mentioned in the threads below. We haven’t tested any of them — and nobody here is claiming they worked.
Found another way around this?
Share your steps and trade-offs so fellow engineers don't have to reinvent the wheel. No account required.
- 1Running BIND9 on a Linux virtual machineDid this help you?
- 2Running DNS directly on network routers or firewallsDid this help you?
- 3Using lightweight alternatives like Unbound or DnsmasqDid this help you?
- 4Manually modifying the hosts file on every clientDid this help you?
In their words
Unedited, grouped by where they were said, most upvoted first within each place, each linked to the thread it came from.
“we still have a need for internal DNS because we have a lot of on-prem stuff that may never go away, and the domain controllers were also serving as internal DNS servers.”source ↗
“The part that sucks usually, is if you have more than one site, it can be a pain to remember to update DNS for each site.”source ↗
Where this came up
People with this problem also raised
- 2How to manage on-premises servers without an Active Directory domain
- 3Why does our website only work with its internal IP?
- 4Which hostname should be included in a mail server TLS certificate?
- 2Why does DNS stop working across the domain after an update?
- 2Secure European email provider for custom domains
- 5Why are websites and APIs suddenly unreachable?