Dynamic registration or deletion of one or more DNS records associated with DNS domain ‘%1’ failed. These records are used by other computers to locate this server as a domain controller (if the specified domain is an Active Directory domain) or as an LDAP server (if the specified domain is an application partition). Possible causes of failure include: – TCP/IP properties of the network connections of this computer contain wrong IP address(es) of the preferred and alternate DNS servers – Specified preferred and alternate DNS servers are not running – DNS server(s) primary for the records to be registered is not running – Preferred or alternate DNS servers are configured with wrong root hints – Parent DNS zone contains incorrect delegation to the child zone authoritative for the DNS records that failed registration USER ACTION Fix possible misconfiguration(s) specified above and initiate registration or deletion of the DNS records by running ‘nltest.exe /dsregdns’ from the command prompt or by restarting Net Logon service. Nltest.exe is available in the Microsoft Windows Server Resource Kit CD.

Details
Product: Windows Operating System
Event ID: 5781
Source: NetLogon
Version: 5.2
Symbolic Name: NELOG_NetlogonDynamicDnsServerFailure
Message: Dynamic registration or deletion of one or more DNS records associated with DNS domain ‘%1’ failed. These records are used by other computers to locate this server as a domain controller (if the specified domain is an Active Directory domain) or as an LDAP server (if the specified domain is an application partition). Possible causes of failure include: – TCP/IP properties of the network connections of this computer contain wrong IP address(es) of the preferred and alternate DNS servers – Specified preferred and alternate DNS servers are not running – DNS server(s) primary for the records to be registered is not running – Preferred or alternate DNS servers are configured with wrong root hints – Parent DNS zone contains incorrect delegation to the child zone authoritative for the DNS records that failed registration USER ACTION Fix possible misconfiguration(s) specified above and initiate registration or deletion of the DNS records by running ‘nltest.exe /dsregdns’ from the command prompt or by restarting Net Logon service. Nltest.exe is available in the Microsoft Windows Server Resource Kit CD.
   
Explanation

DNS records for the DNS domain could not be dynamically registered or deleted.

Possible causes include:

  1. The TCP/IP properties of this network connection contain incorrect IP addresses for the preferred and alternate DNS servers.
  2. The preferred and alternate DNS servers are not running.
  3. The preferred or alternate DNS servers are configured with the incorrect root hints.
  4. The parent DNS zone contains incorrect delegation information for the child zone that is authoritative for the DNS records that could not be registered.
   
User Action

To initiate dynamic registration or deletion of the DNS records, do the following:

  1. Verify that the TCP/IP properties are configured with the correct IP addresses.
  2. Verify that the DNS servers are running.
  3. Verify that the DNS servers are configured with the correct root hints.
  4. Verify that the parent DNS zone contains the correct delegation information.
  5. At the command prompt, typenltest.exe /dsregdnsThe Nltest.exe program is available on the Microsoft Windows Server 2000 Resource Kit CD.

Related:

The DNS server was unable to complete directory service enumeration of zone %1. This DNS server is configured to use information obtained from Active Directory for this zone and is unable to load the zone without it. Check that the Active Directory is functioning properly and repeat enumeration of the zone. The extended error debug information (which may be empty) is “%2”. The event data contains the error.

Details
Product: Windows Operating System
Event ID: 4004
Source: DNS
Version: 5.2
Symbolic Name: DNS_EVENT_DS_ZONE_ENUM_FAILED
Message: The DNS server was unable to complete directory service enumeration of zone
%1. This DNS server is configured to use information obtained from Active
Directory for this zone and is unable to load the zone without it. Check
that the Active Directory is functioning properly and repeat enumeration
of the zone.
The extended error debug information (which may be empty) is “%2”.
The event data contains the error.
   
Explanation

The DNS Server service uses Active Directory to store DNS data, and it encountered a Lightweight Directory Access Protocol (LDAP) error while querying the directory. This error could be caused by either a high load on the domain controller or the failure of other domain controller services.

   
User Action

If this message appears repeatedly, restart the DNS Server service, and then look in the event log for other events occurring at the same time that could be causing this problem.

For more information about DNS and DNS troubleshooting procedures, see Domain Name System(DNS)Center
.

Related:

The domain ” is currently unreachable.

Details
Product: Exchange
Event ID: 4003
Source: MSExchangeTransport
Version: 6.5.6940.0
Component: Microsoft Exchange Transport
Message: The domain ‘<name>‘ is currently unreachable.
   
Explanation

This event can occur when the named domain is not reachable for a variety of reasons, with the following three being the most common:

  • The DNS server is unable to resolve names.
  • The SMTP Virtual Server or SMTP Connector may be misconfigured.
  • Default Internet Message Format may be set to a specific domain.
   
User Action
  • Ensure that the DNS server configured for use by the Exchange 2000 Server is able to resolve names correctly.
  • Ensure that the SMTP Virtual Server and/or the SMTP Connector is/are correctly configured.
  • Change Default Internet Message Format so it has an * in the Domain field.

Related:

The DNS server could not find protocol “%1” specified for the well known service (WKS) resource record (RR) in zone file %2 at line %3. Although the DNS server continues to load, ignoring this RR, it is strongly recommended that you either correct this WKS RR or remove it from the zone file. The zone file is located in the %SystemRoot%\\System32\\Dns directory.

Details
Product: Windows Operating System
Event ID: 1618
Source: DNS
Version: 5.0
Symbolic Name: DNS_EVENT_UNKNOWN_PROTOCOL
Message: The DNS server could not find protocol “%1” specified for the well known service (WKS) resource record (RR) in zone file %2 at line %3. Although the DNS server continues to load, ignoring this RR, it is strongly recommended that you either correct this WKS RR or remove it from the zone file. The zone file is located in the %SystemRoot%\\System32\\Dns directory.
   
Explanation

The protocols for WKS (Well Known Service) records are usually TCP and UDP, but can be any of the entries listed in the Protocol file in the Systemroot\System32\Drivers\Etc folder. The services that can be used for the DNS WKS records have numbers that are less than or equal to 256, and are listed in the Services file in the Systemroot\System32\Drivers\Etc folder. Use these files to view the protocols and services that are available for the WKS records.

   
User Action

To delete this record from the specified database file:

1) In DNS Manager, double-click the specified database file.
2) Right-click the WKS record and then click Delete Record.
3) Stop and restart DNS.

If you need to add a WKS record to the specified database file, select a service from the Services file in the Systemroot\System32\Drivers\Etc folder.

To add a WKS record:
1) In DNS Manager, right-click the specified database file, and then click New Record.
2) Select WKS Record from the Record Type list. Use the context sensitive help to assist you in configuring the WKS record.

Related:

The DNS server encountered invalid domain name “%1”.

Details
Product: Windows Operating System
Event ID: 1542
Source: DNS
Version: 5.0
Symbolic Name: DNS_EVENT_INVALID_DOTTED_DOMAIN_NAME
Message: The DNS server encountered invalid domain name “%1”.
   
Explanation

Domain names must conform to certain naming restrictions. Domain names allow the use of the characters a-z, A-Z, 0-9, and the dash, or minus, sign ( – ). They can contain uppercase and lowercase characters, and they are not case-sensitive. Identical names are not allowed. The maximum length of domain names is 254 characters.

   
User Action

In DNS Manager:

1. Search the database files for the specified domain name.
2. Open each resource record and edit the specified name based on the restrictions defined in the explanation.
3. Stop and restart DNS.

Related:

The DNS server encountered invalid domain name “%1” in zone file %2 at line %3. Although the DNS server continues to load, ignoring this name, it is strongly recommended that you either correct the name or remove the resource record from the zone file, which is located in the %SystemRoot%\\System32\\Dns directory.

Details
Product: Windows Operating System
Event ID: 1541
Source: DNS
Version: 5.0
Symbolic Name: DNS_EVENT_PARSED_INVALID_DOMAIN_NAME
Message: The DNS server encountered invalid domain name “%1” in zone file %2 at line %3. Although the DNS server continues to load, ignoring this name, it is strongly recommended that you either correct the name or remove the resource record from the zone file, which is located in the %SystemRoot%\\System32\\Dns directory.
   
Explanation

Domain names must conform to certain naming restrictions. Domain names allow the use of the characters a-z, A-Z, 0-9, and the dash, or minus, sign ( – ). They can contain uppercase and lowercase characters, and they are not case-sensitive. Identical names are not allowed. The maximum length of domain names is 254 characters.

   
User Action

Edit the database file:

1. In Windows Explorer, go to the Systemroot\Wystem32\Dns folder.
2. Double-click the specified file, and then select Notepad to open it.
3. Edit the specified line to correct the domain name.
4. Save and close the database file.
5. Stop and restart DNS.

Related:

The DNS server encountered domain name “%1” exceeding maximum length. Although the DNS server continues to load, ignoring this name, it is recommended that you either correct the name or remove the resource record from the zone file, which is located in the %SystemRoot%\\System32\\Dns directory.

Details
Product: Windows Operating System
Event ID: 1543
Source: DNS
Version: 5.0
Symbolic Name: DNS_EVENT_DOMAIN_NAME_TOO_LONG
Message: The DNS server encountered domain name “%1” exceeding maximum length. Although the DNS server continues to load, ignoring this name, it is recommended that you either correct the name or remove the resource record from the zone file, which is located in the %SystemRoot%\\System32\\Dns directory.
   
Explanation

The specified domain name exceeds the 254 character limit.

   
User Action

In DNS Manager:

1. Search the database files for the specified domain name.
2. Open each resource record and edit the specified name to correct it.
3. Stop and restart DNS using Services in Administrative Tools.
4. Check the domain name defined on the Identification tab of the TCP/IP Properties dialog box.

Related:

Process %1 (PID=%2). Error DNS_ERROR_RCODE_NAME_ERROR (0x%3) occurred when DNS was queried for the service location (SRV) resource record used to locate a domain controller for domain %4 The query was for the SRV record for %5 Common causes of this error include the following: – The DNS SRV records required to locate a domain controller for the domain are not registered in DNS. These records are registered with a DNS server automatically when a domain controller is added to a domain. They are updated by the domain controller at set intervals. This computer is configured to use DNS servers with following IP addresses:%6 – One or more of the following zones do not include delegation to its child zone:%7 For information about correcting this problem, %8%9

Details
Product: Exchange
Event ID: 2119
Source: MSExchangeADAccess
Version: 8.0
Symbolic Name: DSC_EVENT_DNS_NAME_ERROR
Message: Process %1 (PID=%2). Error DNS_ERROR_RCODE_NAME_ERROR (0x%3) occurred when DNS was queried for the service location (SRV) resource record used to locate a domain controller for domain %4 The query was for the SRV record for %5 Common causes of this error include the following: – The DNS SRV records required to locate a domain controller for the domain are not registered in DNS. These records are registered with a DNS server automatically when a domain controller is added to a domain. They are updated by the domain controller at set intervals. This computer is configured to use DNS servers with following IP addresses:%6 – One or more of the following zones do not include delegation to its child zone:%7 For information about correcting this problem, %8%9
   
Explanation

This event indicates that Domain Name System (DNS) service (SRV) records for the specified domain controller cannot be found. The specified domain controller will not be used by ADAccess. As long as there is sufficient capacity in suitable domain controllers, there is no mail flow interruption. We recommend that you investigate the issue and fix it.

This event may be caused if a DNS SRV resource record is not registered in DNS. One or more of the zones listed in the error message do not include a delegation to its child zone.

This event may be caused when the following conditions are true:

  • A DNS SRV resource record is not registered in DNS.

  • One or more of the zones listed in the error message do not include a delegation to its child zone.

See the event description for detailed information about the cause of this event.

   
User Action

To resolve this event, verify that the SRV resource record for the requested domain and service type exists in DNS. You can do this using the Dcdiag command-line tool. To do this, run dcdiag /s:<Domain Controller Name> from a command prompt on the Exchange Server. Use the output of Dcdiag to discover the root cause of any failures or warnings that it reports. For more information, see Dcdiag Overview at the Microsoft Windows Server TechCenter.

If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.

Related:

Protocol Analysis warning. No DNS entries were found for this server’s authoritative domains. Open proxy detection is not available.

Details
Product: Exchange
Event ID: 200
Source: MSExchange Antispam
Version: 8.0
Symbolic Name: ProtocolAnalysisBg
Message: Protocol Analysis warning. No DNS entries were found for this server’s authoritative domains. Open proxy detection is not available.
   
Explanation

This Warning event indicates that the server could not resolve the domain for which it is authoritative in the domain records on the Domain Name System (DNS) servers it uses for name resolution. This Warning event is logged every five minutes until the server can resolve the domain in DNS.

   
User Action

No user action is required if this event is no longer logged. However, if the warning persists, follow one or more of these steps:

  • Review the Application log for related events. For example, events that occur immediately before and after this event may provide more information about the root cause of this error.

  • Try to resolve the DNS issue in your Exchange environment by following these steps:

    • Use the command prompt command pconfig to determine the DNS servers that are used by this server.

    • Make sure that the DNS server entries are correct.

    • Determine and correct the problem that removed the domain record from the domain records on the DNS server.

      Note   You may be able to resolve this issue by stopping and restarting the Netlogon service on a domain controller in the domain that uses the DNS server. Restarting the Netlogon service will update the DNS entries required by Microsoft Exchange Server and the Active Directory directory service if the forward lookup zone for the domain record exists in DNS.

  • If this event seems to cause mail flow interruptions or other problems in your Exchange environment, contact Microsoft Customer Support. For information about how to contact support, visit Microsoft Help and Support.

If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.

Related:

The zone %1 is configured to accept updates but the A record for the primary server in the zone’s SOA record is not available on this DNS server. This may indicate a configuration problem. If the address of the primary server for the zone cannot be resolved DNS clients will be unable to locate a server to accept updates for this zone. This will cause DNS clients to be unable to perform DNS updates.

Details
Product: Windows Operating System
Event ID: 800
Source: DNS
Version: 5.2
Symbolic Name: DNS_EVENT_ZONE_BAD_PRIMARY_SERVER
Message: The zone %1 is configured to accept updates but the A record for the primary server
in the zone’s SOA record is not available on this DNS server. This may indicate
a configuration problem. If the address of the primary server for the zone cannot
be resolved DNS clients will be unable to locate a server to accept updates for this
zone. This will cause DNS clients to be unable to perform DNS updates.
   
Explanation

The host address (A) resource record associated with the start of authority (SOA) resource record for this zone
is missing. Host (A) resource records are used in a zone to associate DNS domain names of computers (hosts) to their IP addresses.

The host (A) resource record could be missing because it was not registered, because it was accidentally deleted, or because the SOA is preventing any host address (A) resource records from being registered.

   
User Action

Manually create a host (A) resource record using the DNS console and then inspect the SOA record to ensure that it is correct.

For more information about how to configure and manage DNS resource records, see Managing resource records in Microsoft TechNet.

For more information about DNS and DNS troubleshooting procedures, see Domain Name System(DNS)Center.

Related: