Domain name change, forward lookup zone issue

I"ve got a new server 2008, not currently in use yet.  I was asked to change the domain name and did so following the instructions below.  

http://it.toolbox.com/blogs/techscrawl/server-2008-domain-rename-28069

My problem is that I am unable to join computers to the domain.  I'm getting an error message that says

An attempt to resolve the DNS name of a comain controller in the domain being joined has failed.  Please verify this client is configured to reach a DNS server that can resolve DNS names.....

When I check on the DNS on the server, the forward look zones have the old domain name.  I'm guessing I need to delete those and create new ones w/ the new domain name, but that will be a new process for me.

Any thoughts?  Thanks.
SupermanTBAsked:
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.

dmf415Commented:
You must add your domains DNS server to the domain controller.  Basically you goto your new domain controllers network properties and change the dns server in the tcp/ip settings
0
kevinhsiehCommented:
You probably need to create a new authoratitive DNS zone on your DNS server hosted by the domain controller. I bet that the domain rename didn't create a new DNS zone, so you effectively don't have DNS for your AD domain and that breaks AD.
0
SupermanTBAuthor Commented:
Should I just delete the old zones?
0
How do you know if your security is working?

Protecting your business doesn’t have to mean sifting through endless alerts and notifications. With WatchGuard Total Security Suite, you can feel confident that your business is secure, meaning you can get back to the things that have been sitting on your to-do list.

SupermanTBAuthor Commented:
I have the DNS pointing to itself in the TCP/IP properties
0
dmf415Commented:
you may need to make the server a global catalog server. try this
0
kevinhsiehCommented:
If you have zones for an old, non-existant domain, then yes I would delete them. Make sure you have the new one in place and that the DC put its information in there.
0

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
Darius GhassemCommented:
When you recreate make sure you make them AD integrated this could have fixed the problem when you domian renamed
0
SupermanTBAuthor Commented:
It actually end up being easier to delete the domain entirely and recreate a new one.  I'll divy up points for effort.  Thanks.
0
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
DNS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.