Windows Server 2008 R2 DC DNS Client SettingsPrint This Post
As I finish up my migration from Windows 2003 to Windows 2008 R2 for my companie’s domain controllers; I run thru my check list of settings. The migration from 2003 to 2008 R2 was flawless, however many of the pain points from when I upgraded to 2000 were revisited.
One such problem was called “DNS Islanding” detailed in Microsoft Knowledge Base article KB275278. The problem exists if you point a Windows 2000 DC/DNS or Windows 2003 DC/DNS to itself and change it’s IP address. It will update the DNS zone it is in, however other DC/DNS unit will not update because the IP has changed and they don’t know where to contact it at; thus islanding the DC/DNS unit.
After spending much time on Microsoft’s TechNet Site I found the answer and best practice. Although the problem existed in Windows 2000 and Windows 2003; it has been corrected in Windows 2003 R2. Windows 2003 R2, Windows 2008, Windows 2008 R2 will change it’s host record on a sufficient number of DNS servers before it changes it’s own DNS server’s host record for itself. This fixes the DNS islanding problem that existed in earlier version of Windows Server. This was found in a blog post on Microsoft’s site by “jdphilli” on March 25th 2008, however no KB article or TechNet article was found.
I also found the best practice for Domain Controller DNS client settings in Windows 2008 / R2. It is best practice to point the client settings for the primary DNS to itself. The secondary DNS server should be pointed to another DC/DNS server (preferably the PDC emulator) and then any other DC/DNS servers in the site.
Tags: Server 2008