Hi folks
We have a single site Windows W2k3 active directory domain. The site used to be run by a single domain controller (htl-newserver). I added another domain controller (Titan) because the original was failing.
After the original failed (it eventually BSOD'd on every reboot), I made Titan authoritative and seized all AD roles. I then reformatted the failed machine, reinstalled the OS, called it Restored and then ran DCPROMO on it to make it a 'backup' DC (yeah - I know they are equal).
I used the instructions located here:
to removed the failed DC from the active directory.
I recently had problems with FRS not replicating data between Restored and Titan. After solving it I checked every single node in DNS and discovered that there are still records relating to the original domain controller, htl-newserver, which obviously no longer exists. However, where these records exist, the records Titan also exist, but corresponding records for Restored do not.
The records are:
DNS\Forward Lookup Zones\htlincs.local\DomainDnsZones\_sites\Default-First-Site-Name\_tcp
contains 2 records:
_ldap Service Location (SRV) [0][100][389] htl-newserver.htlincs.local
_ldap Service Location (SRV) [0][100][389] titan.htlincs.local
the same 2 records are also located in:
..\_sites\_tcp
..\htlincs.local\ForestDnsZones\_sites\Default-First-Site-Name\_tcp
..\ForestDnsZones\_sites\_tcp
Two A records, one for Titan and one for htl-newserver are located at:
DNS\Forward Lookup Zones\htlincs.local\ForestDnsZones
Two name server records are located at:
DNS\Reverse Lookup Zones\0.168.192.in.addr.arpa
What I would like to know is can I safely edit the _ldap records and replace htl-newserver.htlincs.local with restored.htlincs.local. Or, should I delete them?
And, can I safely remove the htl-newserver.htlincs.local from the name server list and add restored.htlincs.local.
Any pointers (pun intended) will be appreciated
Thanks!
We have a single site Windows W2k3 active directory domain. The site used to be run by a single domain controller (htl-newserver). I added another domain controller (Titan) because the original was failing.
After the original failed (it eventually BSOD'd on every reboot), I made Titan authoritative and seized all AD roles. I then reformatted the failed machine, reinstalled the OS, called it Restored and then ran DCPROMO on it to make it a 'backup' DC (yeah - I know they are equal).
I used the instructions located here:
to removed the failed DC from the active directory.
I recently had problems with FRS not replicating data between Restored and Titan. After solving it I checked every single node in DNS and discovered that there are still records relating to the original domain controller, htl-newserver, which obviously no longer exists. However, where these records exist, the records Titan also exist, but corresponding records for Restored do not.
The records are:
DNS\Forward Lookup Zones\htlincs.local\DomainDnsZones\_sites\Default-First-Site-Name\_tcp
contains 2 records:
_ldap Service Location (SRV) [0][100][389] htl-newserver.htlincs.local
_ldap Service Location (SRV) [0][100][389] titan.htlincs.local
the same 2 records are also located in:
..\_sites\_tcp
..\htlincs.local\ForestDnsZones\_sites\Default-First-Site-Name\_tcp
..\ForestDnsZones\_sites\_tcp
Two A records, one for Titan and one for htl-newserver are located at:
DNS\Forward Lookup Zones\htlincs.local\ForestDnsZones
Two name server records are located at:
DNS\Reverse Lookup Zones\0.168.192.in.addr.arpa
What I would like to know is can I safely edit the _ldap records and replace htl-newserver.htlincs.local with restored.htlincs.local. Or, should I delete them?
And, can I safely remove the htl-newserver.htlincs.local from the name server list and add restored.htlincs.local.
Any pointers (pun intended) will be appreciated
Thanks!