We help IT Professionals succeed at work.

Proper DNS settings for 2008 R2 Domain Controllers

tenover
tenover asked
on
I just replaced our two old 2003 domain controllers with new 2008 DC's.  Both are GC's and both run DNS for our local domain.  I keep reading conflicting opinions on what the proper DNS settings should be in the network settings for each DC.  Should each DC point to ITSELF as the primary DNS server and the other DC as it's secondary?  Vice Versa?  Should the server's own IP, whether it's primary or secondary, be the actual IP od the server or the 127.0.0.1 address?  Thanks.
Comment
Watch Question

BRONZE EXPERT
Top Expert 2012
Commented:
The DCs should point to themselves with the actual IP address not the loopback address. Now some Admins point the DCs to another DC but here is the thing with this if the other DC goes down or is rebooted you will some delay or issue on the other DC that points to this DC.

For the reason above a DC should be able to function fully without depending on another DC in my opinion so this is why I point mine to themselves.

Author

Commented:
Thanks.  Will having the DC point to itself as the primary cause a long delay when booting up a DC while it looks at itself for DNS and Active Directory??
BRONZE EXPERT
Top Expert 2012

Commented:
No we don't see this issue. There are ways to delay the start until everything is properly working which is configured with "depend on".
brwwigginsIT Manager

Commented:
I point my DCs to itself as primary and another DC as secondary. I do not see any performance issues.

You should have another DC in your environment as secondary DNS to avoid a DC from becoming an island (but I think that's been worked out in 2008) http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/a2cc4edd-334b-46b2-bbd2-6e380b8788d7/

Author

Commented:
I have two DC's, both DNS servers.  Thanks.

Explore More ContentExplore courses, solutions, and other research materials related to this topic.