| Event Id | 4016 |
| Source | dns |
| Description | The DNS server timed out attempting an Active Directory service operation on DC=RootDNSServers,cn=MicrosoftDNS,cn=System,DC=MHMS-LAW,DC=com. Check Active Directory to see that it is functioning properly. The event data contains the error. Data: 0000: 55 00 00 00 U... |
| Event Information | Information From One Of The News Group May help You 1. I had the same problem. I have 2 servers running DNS; both are Win2k w/SP4, one primary and one secondary. They were working fine, until one day when the CPU usage on both servers plunged to 100% and stayed there. If I stopped the DNS service on either server, the CPU usage dropped to about 4% on both servers. I rebooted both systems with no help; once they come up they run fine for 2 or 3 minutes then the CPU hit 100% again. I stopped replication between my 2 servers and the CPU usage dropped to normal. I had a feeling that it was a replication issue with the reverse lookup zones. As the primary server was the first server to plunge to 100% CPU usage when this started I figured to start there. I deleted all of the reverse lookup zones and then replicated them from the secondary server one by one. After rebuilding them, the CPU usage reached normal levels on both servers 2. Microsoft suggests that this is a caching problem, without providing additional information. Several newsgroup posts suggest that this is an indication of a problem with the Active Directory and that netdiag should be run to diagnose the problem. A Microsoft engineer suggested the following: 1. - Stopping the dns service 2. - Delete your zone(s) 3. - Delete your system32\dns folder and your netlogon.dns file 4. - Uninstall dns and reinstall it |
| Reference Links |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.