Originally Posted by
Ron
The problem re-appeared after the DNS servers rebooted from installing the
latest WSUS updates (KB925902). This was the first time the DNS service was
restarted since I fixed the problem. By using DNSCMD, I found out that the .
zone is the DNS cache and that it was AD-integrated (/ZoneInfo). Things I
tried that didn't work: clearing the cache and deleting the RootDNS object
from AD.
What finally worked: changing the "Load zone data on startup" from AD +
registry to just registry. Now DNSCMD /ZoneInfo tells me that the cache is no
longer AD-integrated but file based which will probably be okay with me.
Bookmarks