Link to home
Start Free TrialLog in
Avatar of gwermter
gwermter

asked on

DNS error 32 attempting to load zone

Event Type:      Warning
Event Source:      DNS
Event Category:      None
Event ID:      4521
Date:            2/15/2011
Time:            2:35:22 PM
User:            N/A
Computer:      MARS
Description:
The DNS server encountered error 32 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.


The thing that looks strange to me, the _msdcs under domainname.local is grayed out. I have been through SEVERAL posts and forums trying to find a solution to this problem and no luck.
ASKER CERTIFIED SOLUTION
Avatar of BobintheNoc
BobintheNoc
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of gwermter
gwermter

ASKER

It would be considered ok to delete the primary zone in DNS?
Safe is a relative word.  There will be a timeframe while the zone is being recreated and it will take a bit of time for each client to reregister.  During this time, DNS queries may not return results.  

How many DCs do you have and how large is your environment?  If you're an enterprise, this could be bad to do during production time.   If you're a small environment, you can be recovered within 10 minutes or so--especially if you stage your member machines to reregister right after the zone is recreated when you have a DC reregister itself.  If you've got multiple sites, replication links may fail.

In a flat, non-segmented/non-vlan'ed network, Windows is amazingly resilient when DNS doesn't function fully.  NETBIOS/Mailslots announcements are generally limited to the local subnets only.