Renaming a 2k3 Domain

[adamf]

We are preparing to rename our domain in the coming months and are in the process of testing the procdeure in a virtual environment. I am able to rename the domain following the guide from Microsoft, but when I do this the DNS zone name does not change.

 

In the XML file generated by rendom.exe I change all the relevant bits of information (DomainDNSZones and ForestDNSZones) but they seem to remain the same, this naturally leads to a screwed DNS and clients not able to join the domain.

 

Any ideas where I am going wrong?

[ChrisH]

When I did it I am sure I ended up with 2 zones in DNS one for the old and on for the new.

[mattx]

Just out of interest, why are you renaming your domain ? Is it vital ?

 

Step-by-Step Guide to Implementing Domain Rename:

 

http://download.microsoft.com/download/c/f/c/cfcbff04-97ca-4fca-9e8c-3a9c90a2a2e2/Domain-Rename-Procedure.doc

 

Windows Server 2003 Active Directory Domain Rename Tools

 

http://download.microsoft.com/download/5/6/d/56df978b-9a76-487e-80b7-0250289f2579/domainrename.exe

[adamf]

We are restructuring the forest and this is the best way we can think of doing it short of completly rebuilding AD from scratch.

 

I've already got (and am following) those guides, but don't seem to be getting anywhere with the DNS

[powdarrmonkey]

I seem to remember having to create the new DNS zones myself and then have the migration tool populate them. It was a few months ago now though, can't really remember much about it.

[ajbritton]

We are restructuring the forest and this is the best way we can think of doing it short of completly rebuilding AD from scratch.

 

I've already got (and am following) those guides, but don't seem to be getting anywhere with the DNS

 

I think that what Mattx may be getting at is that, the general wisdom on domain renames is only do it if you really have to. I've seen numerous posts on sites like Experts Exchange where there has been a lot of 'experts' trying to talk others out of doing domain renames.

 

Incidentally, and I'm sure you know this, but it's not possible to change the forest or domain tree membership of a domain simply by renaming it so that the DNS name looks right. Eg. If you start with two domains in different forests, domain1.int and domain2.int, although you can rename domain2.int to become somthing like subdomain.domain1.int, it won't be in the same tree or forest as domain1.int.

[PiqueABoo]

Haven't ever done a rename so take the wisdom of doing this in your scenario with a pinch of salt: If everything is basically fine and only DNS is being stubborn, I would be very tempted to try turning it into old-school DNS with zone files, quickly edit a copy of the old zone file into a the new zone file, then manually create the new primary zone importing that new zone file.

[GlennT]

When I did it I am sure I ended up with 2 zones in DNS one for the old and on for the new.

 

This is the easiest way to go.

[FN-GM]

How big is the forest?

[mattx]

I think that what Mattx may be getting at is that, the general wisdom on domain renames is only do it if you really have to.

 

Got it in one - I've done one, [ on a test network ] and that was a pain.

Unless its really really vital I would leave it. Still, nothing like a challenge !!

[ajbritton]

I'm just looking through the MS notes on Domain Rename and I note that this doc (http://technet2.microsoft.com/windowsserver/en/library/4d0c3b6e-e6f5-4ab3-9d81-106ae3a715491033.mspx?mfr=true) states that 'DNS zones must exist for the new domainss'