Replaced DC - all FSMO roles and Primary DNS (an issue)

[monsterjta]

I'll get right into it.

ROOT domain and CHILD domain. Reprovisionaing ALL DC's with new hardware. Have 5 Dell 860's to take the place of current DCs' hardware.

Introduced first DC into the CHILD domain last Friday. Also installed as a DNS server to replacate records from current CHILD ROLES MASTER. I transfer the roles immediately. I shut down the current DC within 15 minutes. DNS appears to be fully replicated at this point, as well as AD objects and tools. The replacement is now hosting DNS for CHILD domain, as well as all FSMO Roles.

Today I re-addressed the CHILD domain. traffic flowing fine all around. I can ping A records from and to every domain and hostname, EXCEPT from anything in ROOT TO anything in CHILD. I can ping everything from everywhere using IP address or FQDN.

Here's the wierd part. There is one server I didn't re-address in CHILD. This server I can still ping to from the ROOT.

One other detail worth mentioning. There are 2 DC's in each domain.

There are more details to be provided upon request.

 

[markdmac]

Hi monsterjta,

Did you make the new server a GC? did you check in AD Sites and Services to see that the new server is listed and that other servers show up there too?

I hope you find this post helpful.

Regards,

Mark

Check out my scripting solutions at

http://www.thespidersparlor.com/vbscript

 

[monsterjta]

I did not specify any GC settings. We do not have sites, so no need for AD S&S.

It is my belief that previous to re-addressing the child domain, hostnames were resolvable using NetBios due to the broadcast domain envoloping both root and child.

My fix, or workaround, was to add the child domain FQDN to this suffix list. Everything work's great now.

I mentioned earlier the one server I did NOT re-address. That was resolvable throughout this whole process. This fact solidifies the theory.

Happy New year!