Quantcast
Viewing all articles
Browse latest Browse all 31638

DomainDNSZones, and ForestDNSzones are empty

I’m experiencing a problem with DomainDNSZones, and ForestDNSzones. These DNS sub zones are empty. Well actually they contain entries for legacy (removed) 2003 domain controllers, but no entries for the newly installed 2008 domain controllers. I’ve looked for the entries in the netlogon.dns files for each domain controller, and find no references for these zones. Thousands of entries for A  + SRV type records for the remain AD zones, which are being correctly registered.

When I check this in my test and preprod environments over a thousand entries can be found in the DNS and in each netlogon.dns file. The only difference between my test environments and production is DNS is Infoblox in prod, and Microsoft DNS is used in test environments.

I have neither netlogon errors nor any DCdiag errors. I stopped the netlogon, renamed the netlogon.dns to .old and restarted the netlogon service. No change, the netlogon.dns file was regenerated once again without any entries for DomainDNSZones, and ForestDNSzones.

Any ideas? How does the netlogon service determine what DNS entries are required? How does it know what to put in the netlogon.dns file?


Ernie Prescott


Viewing all articles
Browse latest Browse all 31638

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>