Renaming Domain Controllers

   

---

The ability to rename domain controllers running Windows Server 2003 provides you with the flexibility to make changes in a Windows Server 2003 domain whenever the need arises. Rename a domain controller to

• Restructure your network for organizational and business needs.

• Make management and administrative control easier.

When you rename a domain controller, you must ensure that there will be no interruption in the ability of clients to locate or authenticate to the renamed domain controller except when the domain controller is restarted.

Another requirement for renaming a domain controller is that the domain functional level must be set to Windows Server 2003. The new name of the domain controller is automatically updated to DNS and Active Directory. Once the new name propagates to DNS and Active Directory, clients are then able to locate and authenticate to the renamed domain controller. DNS and Active Directory replication latency can delay client ability to locate or authenticate to the renamed domain controller. The length of delay depends on specifics of your network and the replication topology of your particular organization.

During replication latency, clients might not be able to access the newly renamed domain controller. This might be acceptable for clients that try to locate and authenticate to a particular domain controller because other domain controllers should be available to process the authentication request.

---

Top