DNS warning
I am recieving warnings on one of my dns servers
The DNS server encountered error 9002 attempting to load zone . from Active Directory. The DNS server will attempt to load this zone again on the next timeout cycle. This can be caused by high Active Directory load and may be a transient condition.
Thats the warning. This is 2003 box. They are just warnings and I wanted to see if anyone else has run into these. I have not.
Thanks
The DNS server encountered error 9002 attempting to load zone . from Active Directory. The DNS server will attempt to load this zone again on the next timeout cycle. This can be caused by high Active Directory load and may be a transient condition.
Thats the warning. This is 2003 box. They are just warnings and I wanted to see if anyone else has run into these. I have not.
Thanks
Who is Participating?
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
All Courses
From novice to tech pro — start learning today.
-
Course of the Month10 days, 3 hours left to enrollMonitoring and Operating a Private Cloud with System Center 2012 R2 273 lessons
http://community.spiceworks.com/topic/70047-dns-error-9002-attempting-to-load-zone-dns-ad-not-working-properly
90% of the time this is DNS issues. Since you are having problems, here's what I recommend to start:
1. Locate your PDC Emulator. On all domain controllers point their primary DNS to that server. Secondary goes to themselves (ChristopherO and I have an ongoing debate about this, but you have an orphaned DC--at least it sounds like it--and just trying to get this fixed)
2. Check your DNS and make sure you don't have any extra DC's, search through ALL of the folders under your zone (the _MSDSC folders). Delete any DC that shouldn't be there.
3. Do a NETDOM /QUERY FSMO and make sure all of your FSMO roles are found.
4. Check Sites and Services and make sure your sites are setup properly. Make sure every DC has a global catalog. Delete any DC's that are in there but shouldn't be.
5. From each DC make sure you can ping every other one by name and by FQDN (ping servername, and ping servername.domain.com).