MEATBALLHERO
asked on
Where should I point my backup domain controller & DNS server
My main domain controller is setup to point to itself.
Primary DNS 192.168.1.100
Secondary 192.168.1.101
On backup domain controller/dns should I point it to itself for primary or use the same as above?
Primary DNS 192.168.1.100
Secondary 192.168.1.101
On backup domain controller/dns should I point it to itself for primary or use the same as above?
Brian Pierce
In the real world it doesn't really matter - some would argue that each should point to the other as the preferred DNS server and to themselves as the alternate,
ASKER
What if both of these server are also DHCP servers but the scope is split. That is what I'm shooting for.
I'd argue that it does matter so you can avoid race condition issues. See my answer here:
https://www.experts-exchange.com/questions/27556645/DNS-Client-Settings-for-Domain-Controllers.html
You are good to go with DHCP, split scope is fine.
Thanks
Mike
https://www.experts-exchange.com/questions/27556645/DNS-Client-Settings-for-Domain-Controllers.html
You are good to go with DHCP, split scope is fine.
Thanks
Mike
I knew someone would say that :-)
Microsoft's Best Practice recommendation is:
Primary: server's own private IP (192.168.1.101)
Secondary: next best DNS server (192.168.1.100)
Tertiary: loopback (127.0.0.1)
Primary: server's own private IP (192.168.1.101)
Secondary: next best DNS server (192.168.1.100)
Tertiary: loopback (127.0.0.1)
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Directly from Microsoft's engineering team and Best Practices Analyzer.
Unfortunately there are internal debates within Microsoft regarding this (as the article also suggests).
A read through http://technet.microsoft.com/en-us/library/dd391963(v=ws.10).aspx and http://technet.microsoft.com/en-us/library/ff807362(v=ws.10).aspx should provide enough information to make an informed decision.
Unfortunately there are internal debates within Microsoft regarding this (as the article also suggests).
A read through http://technet.microsoft.com/en-us/library/dd391963(v=ws.10).aspx and http://technet.microsoft.com/en-us/library/ff807362(v=ws.10).aspx should provide enough information to make an informed decision.