Article ID: 240942 - Last Review: March 1, 2007 - Revision: 3.2 Active Directory DNSHostName property does not include subdomainThis article was previously published under Q240942 SYMPTOMS
When a computer joins an Active Directory domain (for example, MICROSOFT.COM), Active Directory stores the fully qualified domain name (FQDN) of the computer with the computer account in a property called DNSHostName. For example, for a computer named "W2K-CLIENT," the DNSHostName property contains a "W2K-CLIENT.MICROSOFT.COM" value. If the computer belongs to a Directory Naming Service (DNS) zone (for example, PSS.MICROSOFT.COM) whose name is different from the Active Directory domain name (in this example, MICROSOFT.COM) that the computer joined, the DNSHostName does not by default include the subdomain name (in this example, "PSS"), but only contains the value "W2K-CLIENT.MICROSOFT.COM". Because there is no W2K-CLIENT.MICROSOFT.COM entry in DNS (DNS knows only about the "W2K-CLIENT.PSS.MICROSOFT.COM" entry), some services, such as the File Replication service (FRS), may not work correctly and the following event log entry may be generated:
Error 13505: Source - NTFRS The File Replication Service is having trouble enabling replication from Computer1 to Computer2 for Directory x:\y; retrying. CAUSE
The DNSHostName property of the computer object contains Hostname.PrimaryDNSSuffix by design.
By default, PrimaryDNSSuffix is the name of the Active Directory domain the computer is joined to. In the example above, PrimaryDNSSuffix is MICROSOFT.COM. To view PrimaryDNSSuffix for a computer, use the ipconfig /all command. WORKAROUND
Changing the DNSHostName property to the current DNS name of the server, including the subdomain name, solves the FRS replication problem.
You can change the DNSHostName property by using one of the following methods:
| Article Translations
|
Back to the top
