I was thinking more along the lines of, "nightmares of the past." :-)
-- ME2 On Mon, Mar 1, 2010 at 8:48 AM, Michael B. Smith <[email protected]>wrote: > Wow, shades of the past... > > Aren't you running SP4? Then what your boss did is fine. > > A reboot will be enough. (Actually you can stop netlogon, remove > netlogon.dns, restart netlogon, then do an ipconfig /registerdns, if you > don't want to reboot - a reboot might be easier.) > > Regards, > > Michael B. Smith > Consultant and Exchange MVP > http://TheEssentialExchange.com > > > -----Original Message----- > From: Michael Leone [mailto:[email protected]] > Sent: Monday, March 01, 2010 10:53 AM > To: NT System Admin Issues > Subject: "Island" DNS server problem for a forst/ > > I have a Win2000 AD, in a parent-child configuration. I have the "island" > DNS server problem > > The so-called "island" problem occurs when a domain controller that is the > primary DNS server for the domain, points to itself as the preferred or > alternate DNS server for the zone _msdcs.<DNS > Forest-name>. > <http://technet.microsoft.com/en-us/library/cc749944.aspx > > > That's my problem - the primary DNS for my parent domain (i.e., > forest) points to itself as primary DNS server (secondary DNS server points > to another DNS server in that domain). We want to demote this server back to > a member server, but continue to have it act as primary DNS server for the > forest (temporarily). We plan on upgrading the domain to Win2003 this > weekend, and we'd like to have the current primary DNS server remain as the > primary DNS server for the forest - that will save us from having to change > the static DNS settings on all my servers. > > So, my boss changed the order of the DNS servers setting in the properties > of TCP/IP on that server; the primary DNS setting for that DC now points to > another DC in that domain, and the secondary DNS server is itself. > > DC1 - primary DNS set to DC2; secondary DNS set to DC1 > DC2 - primary DNS set to DC1; secondary DNS set to DC2 > > I think that's how the DNS should be set. The question is: do I need to > "ipconfig /registerdns" on DC1 after changing the settings to the above? Or > will a reboot be enough? > > The server passes the "dnslint" test properly, BTW - I'm just afraid what > will happen if we demote DC1. I think the DNS server will stop working, or > lose it's configuration totally. That would be BAD .... > > Thanks > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ < > http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
