New Child Domain cannot be contacted

I added a new child domain to active directory.  Built a new Server 2008 R2 machine, added the domain controller role and selected add new child domain to existing forest.

When I run setup /preparedomain to add exchange objects to the new child domain I get the message "Domain cannot be contacted or does not exist".  DC is running and on the network.  I can connect to the new DC and child domain using Active Directory Users and Computers.

This may have been caused by me changing the server hostname after adding the DC role.  In Active directory sites and services the server is listed under the old name.

Is there a way to re-register the DC under the new name and ensure the proper links are in place.  If I remove the DC role then re-add it would it delete the child domain?  There are no other DC's in the child domain.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

I think you didn't follow the procedure to rename a domain controller.
Did you follow below KB or simply rename the dc? 
I think you have to do it from scratch for child domain,as you have not not followed the procedure.
There are stpes required & do you have system state backup,before renaming a dc?
Peter_CullAuthor Commented:
No didn't follow the procedure, changed the name in computer properties.  It's a brand new server so didn't back up the system state.   I have Server 2003 DC in parent domain and Server 2008 DC in child domain.  Given the mixed environment is it best to rebuild the server.  How do I completely remove the empty child domain?
Run metadata cleanup of child domain using ntdsutil command on parent domain controller & account should be member of enterprise & administrator group to perform metadata cleanup.;EN-US;230306

If you get any error,follow below;en-us;235416

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Peter_CullAuthor Commented:
Cleaned up domain objects then rebuilt server.  Now working fine.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Active Directory

From novice to tech pro — start learning today.