Changed secondary domain controller name

i have domain controller that i renamed. while doing wireshark capture notice packet containing old name.

632 12.966401 192.168.0.114 192.168.7.255 nbns name query nb nsi1a<20>

the computers new name nsi1, , not nsi1a. can fix this?

hi,

have find error log after domain controller rename process, or have meet issue after domain controller rename?

by default, after domain controller rename, new name of domain controller automatically updated domain name system (dns) , active directory. once new name propagates dns , active directory, clients capable of locating , authenticating renamed domain controller. dns , active directory replication latency may delay client ability locate or authenticate renamed domain controller. length of time takes depends on specifics of network , replication topology of particular organization.

during replication latency, clients may not able access newly renamed domain controller. might acceptable clients try locate , authenticate particular domain controller since other domain controllers should available process authentication request.

for more information please refer following ms articles:

renaming domain controllers
http://technet.microsoft.com/en-us/library/cc740045(v=ws.10).aspx
renaming domain controller
http://technet.microsoft.com/en-us/library/cc794951(v=ws.10).aspx
http://technet.microsoft.com/en-us/library/cc782761(v=ws.10).aspx

---

lawrence

technet community support

Windows Server  >  Windows Server General Forum