R
Ryan White
Hi all,
Just figured I'd drop this here in case anybody is having a similar
problem.
My company has a few domains that our Win2k DNS servers are serving,
the two of interest being company.com and corp.company.com. We were
having an issue where every time any of our DNS/DC's were reboot or
had the DNS service restarted, the company.com zone would magically
disappear from the DNS management MMC, and wouldn't be loaded by the
DNS service. We scratched our heads on this one for a while, before I
gave up and made my first ever paid support call to MS. Luckily, they
had it fixed in about 5 minutes flat.
Turns out if you open AD User and Computers, and view the Advanced
properties, under the System folder, MicrosoftDNS, there was a ghost
entry for the zone already in there, even though nobody had ever tried
to load it as AD-integrated! (At least not since I've been working
here). Anyway, all we had to do was delete that ghost entry, and
everything started working fine after reboots and such.
The theory is that MS DNS would start up on any of our domain
controllers, and see it had a flat file zone for company.com as well
as an AD entry for the same company.com zone, so it would dump the
flat file, and try the AD zone. But, since this was just an empty or
outdated ghost entry, this zone couldn't be loaded, so MS DNS would
just give up (without ANY errors ANYWHERE), and not load the zone.
Talk about annoying! Anyway, it's been resolved, and I felt pretty
stupid after finding out it was so easy to fix.
=)
Thanks,
-ryan.
Just figured I'd drop this here in case anybody is having a similar
problem.
My company has a few domains that our Win2k DNS servers are serving,
the two of interest being company.com and corp.company.com. We were
having an issue where every time any of our DNS/DC's were reboot or
had the DNS service restarted, the company.com zone would magically
disappear from the DNS management MMC, and wouldn't be loaded by the
DNS service. We scratched our heads on this one for a while, before I
gave up and made my first ever paid support call to MS. Luckily, they
had it fixed in about 5 minutes flat.
Turns out if you open AD User and Computers, and view the Advanced
properties, under the System folder, MicrosoftDNS, there was a ghost
entry for the zone already in there, even though nobody had ever tried
to load it as AD-integrated! (At least not since I've been working
here). Anyway, all we had to do was delete that ghost entry, and
everything started working fine after reboots and such.
The theory is that MS DNS would start up on any of our domain
controllers, and see it had a flat file zone for company.com as well
as an AD entry for the same company.com zone, so it would dump the
flat file, and try the AD zone. But, since this was just an empty or
outdated ghost entry, this zone couldn't be loaded, so MS DNS would
just give up (without ANY errors ANYWHERE), and not load the zone.
Talk about annoying! Anyway, it's been resolved, and I felt pretty
stupid after finding out it was so easy to fix.
=)
Thanks,
-ryan.