GUID Records Are Not Registered If MX Record with Wildcard Character Is Present

Windows 2000 domain controllers may fail to dynamically register the globally unique identifier (GUID) DNS records in the forest root zone.

The following event will be logged:

When the Netlogon service tries to register the GUID record in the _msdcs.forestrootzone, the GUID record may not be registered if there is an MX record that is wildcard character (*). The Netlogon service does a DNS query of type ALL for the guid._msdcs.forestrootzone. If a wildcard record exists, the DNS server responds to the query with the MX server information and the dynamic update does not succeed.

Example:

Windows 2000 Domain Controller Request:
Question Section: 0ae9d36d-1c8c-4aa4-8130-11a140138bc6._msdcs.Name.com. of Req type for All on class INET addr.


DNS Server Reply:
Answer section: 0ae9d36d-1c8c-4aa4-8130-11a140138bc6._msdcs.Name.com. of type Mail Xchg on class INET addr.

To resolve this problem, obtain the latest service pack for Microsoft Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

Method 1

Delete the MX record or change the record from a wildcard character to a specific mail host or domain.

Method 2

Create the GUID record manually. If DNS zone scavenging is enabled, select the advanced properties of the GUID record, and then click to clear the Delete this record when it becomes stale check box.