Microsoft KB Archive/240942

= Active Directory DNSHostName property does not include subdomain =

Article ID: 240942

Article Last Modified on 3/1/2007

-

APPLIES TO


 * Microsoft Windows 2000 Server
 * Microsoft Windows 2000 Advanced Server
 * Microsoft Windows 2000 Datacenter Server

-



This 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  to   for  ; retrying.



CAUSE
The DNSHostName property of the computer object contains. by design. By default,  is the name of the Active Directory domain the computer is joined to. In the example above,  is MICROSOFT.COM.

To view  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:
 * Change the computer's  and give the computer the appropriate right in Active Directory to change the DNSHostName property during boot.

To change the computer's, on the Network Identification tab in the System tool in Control Panel, click Properties, and then click More. Change the Primary DNS suffix of this computer setting to include the subdomain for the computer. Click OK, click OK, and then click OK.

To give the computer the appropriate rights in Active Directory to change the DNSHostName property (do this on a domain controller):
 * Start the Active Directory Users and Computers snap-in.
 * Choose Advanced view.
 * Right-click the appropriate domain, and then click Properties.
 * On the Security tab, add the Self group to the ACL.
 * Click Advanced button.
 * Click Self, and then click View/Edit.
 * Click the Property tab. In the Apply onto box, click Computer Objects.
 * Under Permissions, click to select the Write DNS host name check box.
 * Click OK to close all dialog boxes.
 * Restart the computer to register with Active Directory again.
 * Use Group Policy to set  appropriately on all computers in the subdomain. You can set   in Group Policy by opening Computer Configuration, Administrative Templates, System, and then DNS Client.
 * Use Active Directory Services Interface (ADSI) and write a script to change the DNSHostName property.

Additional query words: FRS NTFRS

Keywords: kbenv kbprb KB240942

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.