The DNS server is bound to a large number of IP addresses. Each of these server IP addresses consumes additional system resources and can add a slight increase in performance overhead for DNS query reception. In most cases, you can remove secondary IP addresses that are not required to support server networking hardware. For more information, see "Configuring multihomed servers" in the online Help.
The DNS server has encountered numerous run-time events. To determine the initial cause of these run-time events, examine ...
The DNS server has invalid or corrupted registry parameter %1. To correct the problem, you can delete the applicable registry ...
The DNS server has moved the AD-integrated root hint data for all DNS servers in this domain to the %1 directory partition. ...
The DNS server has written a new version of the boot file. Either new zones or changes to existing zone information were ...
The DNS server is bound to a large number of IP addresses. Each of these server IP addresses consumes additional system resources ...
The DNS server is configured to forward to a non-recursive DNS server at %1. DNS servers in forwarders list MUST be configured ...
The DNS server is ignoring an invalid resource record in zone file %1 at line %2. See the previously logged event for a description ...
The DNS server is not root authoritative and no root hints were specified in the cache.dns file. Where the server is not ...
The DNS server is now booting from the registry or directory. The existing server boot file will no longer be read by the ...