IIRC, the 'island problem' in W2K happened when a DC that pointed to itself for DNS registered its GUID CNAME record in its own AD-integrated copy of the _msdcs zone, but since nobody else knew about it they could never replicate it from there to the rest of the domain. Can you elaborate on how this is fixed in W2K3 ? Is it because of placing the AD-integrated DNS data into app partitions instead of the domain NC ? Something else ? Just curious.... Dave
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of [EMAIL PROTECTED] Sent: Thursday, April 22, 2004 10:12 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: [ActiveDir] DNS Server Using its own IP as a Primary DNS Yes - the island issue is only in Windows 2000 and is resolved in Windows 2003. In fact, you are forced in Windows 2003 if I recall correctly to change the second DNS IP address to something different on the server running DNS. Chuck Gafford MCSE (Windows 2003, 2000, NT 4.0), MCSE+I, MCT Systems Architect, Unisys List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
