fredmartinmaine
IS-IT--Management
We had a pair of Domain Controllers that offered AD Authentication, DNS and DHCP. Dynamic DNS actually.
A decision has been made to move DHCP and DNS to another device, a firewall. I moved DHCP a while ago, and other than not having Dynamic DNS, it's worked well.
However, when I start up DNS on the firewall, and stop the DNS Server service on the Domain Controller, server shares start asking users to authenticate to browse to a share, and eventually logging in to a domain PC fails because it can't find a domain controller.
I've read in a handful of places that domain controllers don't need to be DNS servers but they don't offer any information on how that's properly set up.
Does anyone know what I'm missing here?
A decision has been made to move DHCP and DNS to another device, a firewall. I moved DHCP a while ago, and other than not having Dynamic DNS, it's worked well.
However, when I start up DNS on the firewall, and stop the DNS Server service on the Domain Controller, server shares start asking users to authenticate to browse to a share, and eventually logging in to a domain PC fails because it can't find a domain controller.
I've read in a handful of places that domain controllers don't need to be DNS servers but they don't offer any information on how that's properly set up.
Does anyone know what I'm missing here?