You really don't want to just delete zones and hope that AD recreates them automagically. What if you have static records in there? For objects that are not able to (or actively not allowed to) register themselves in DNS? What if the zone does allow dynamic registrations?
You want to save the flat file (to a location off the server even) before you whack a zone. A "ooops. ok, let's roll it back" is better that "we a phucked, what now?"
Just saying.
Deji
"tenroc2o0o" <tenroc2o0o.3i7o3f[ at ]DoNotSpam.com> wrote in message news:tenroc2o0o.3i7o3f[ at ]DoNotSpam.com...
[Quoted Text] > > I had this happen before. Apparently a server can have an AD integrated > DNS zone as well as a standard sitting on top of it - really confusing. > DNS updates weren't working correctly and my servers weren't syncing > properly. I just *deleted* the zone (since it was standard anyway), > restarted DNS, and the AD-Integrated Zone just reappeared in the list - > like it had been there all along. Ironically it had the latest DNS info > from the other servers. > > Furthermore, even if you screw up DNS, just create a zone for your > domain, make it AD-integrated, and reboot. The DNS entries should > recreate themselves when AD starts up. > > > -- > tenroc2o0o > ------------------------------------------------------------------------ > tenroc2o0o's Profile: http://forums.techarena.in/members/tenroc2o0o.htm> View this thread: http://forums.techarena.in/server-dns/1064350.htm> > http://forums.techarena.in>
|