Event ID: 3 Source: DNS

Event ID/Source search

Keyword search

Example: Windows cannot unload your registry file

EvLog 3.0 – Monitor an unlimited number of servers with $49/year

With the current low prices for servers and the need for processing power, even a small company may end up with quite a few of them. If ten years ago it was still common to see an entire company using just one server, these days that's no longer the case.
New computers are added to the network with the understanding that they will be taken care of by the admins. Keeping an eye on these servers is a tedious, time-consuming process. Even with 5 minutes per server (to check the logs and other parameters), it may take an hour to make sure that everything is ok and no "red lights" are blinking on any of the servers.

Event ID: 3 Source: DNS

Source: DNS

Type: Information

Description:
The DNS server has shutdown.

English: Request a translation of the event description in plain English.

Concepts to understand:
What is the role of a DNS server?

Comments:
Dermot
When promoting a DC using DCPromo, after the promotion of the DC, the DNS service was starting but the DNS console was showing DNS as down with a red X against the server and I was receiving this event when restarting the DNS service. I thought for sure that something was wrong, but when promoting a DC, DNS will behave this way until a full replication of the directory completes. Check the NTDS.dit file and you will see it growing in size as replication completes on the new DC. Also check the event logs to see events indicating the end of replication. DNS worked as expected a few moments after synchronization completed.

I think that the reason this happens is that the Domain and Forest DNS partitions in AD are the last to be replicated when doing a DCPromo, and DNS would not run on a DC until it can check if there are any AD integrated zones that it needs to load.
Click if the comment is good!

^{x
1}

EventID.Net
This behavior can occur when the registry key that determines whether your DNS server initializes from a boot file or from the registry has not been updated properly. See ME171781 to solve this problem.
Click if the comment is good!

^{x
1}

EventID.Net
When you shut down a Microsoft Windows 2000-based computer that is running the DNS Server service and then restart the computer, this event might be logged. See ME875529 for a hotfix applicable to Microsoft Windows 2000.
Click if the comment is good!

^{x
1}

EventID.Net
Occurs when the DNS service is stopped or the computer is shutdown.
Click if the comment is good!

^{x
1}

Private comment: Subscribers only. See example of private comment

Links: ME171781, ME875529

Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...

Feedback: Send comments or solutions - Notify me when updated

Printer friendly