I run a small business with a Windows Server handling DNS for our machines, and we're currently using Google DNS on our Cisco equipment. I want to transition to NextDNS, but I'm not sure of the best approach. Should I disable Windows DNS and just install NextDNS on the server? Maybe set up a virtual machine or a dedicated device? I'm inclined to keep it on the domain controller to avoid updating all static DNS addresses across our network, but I worry about compatibility with Windows DNS. If I swap out Windows DNS for NextDNS, should I make changes on our Cisco devices as well, or just configure them to point to the server instead? I'm open to any advice, experiences, or warnings you might have!
4 Answers
I’m new to all this, but I’d love to hear what goes wrong when you mess with Windows DNS. It’s a part of the system I haven’t challenged yet, so knowing potential pitfalls would help a lot!
For sure, keep it on your Domain Controllers unless there’s a pressing reason to change. We use InfoBlox successfully, but that was due to specific business needs. If your engineers are experienced, then maybe consider alternatives, but tread carefully with DNS!
If your computers are domain-joined, it’s probably best to keep your Windows Domain Controllers, which usually serve as DNS servers in small business settings. Set the NextDNS server IPs as the only DNS forwarders on your Windows DNS servers. This way, it will effectively work with your existing setup without needing a major overhaul.
Honestly, I'd advise against messing with Windows DNS unless you have a really good reason. If NextDNS is an external service, just configure it as a forwarder on your existing setup. It's safer that way.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures