After adding DNS to 2008 DC the primary zone is not automatically added.

We have a fairly large environment 20+ offices of mixed 2003 and 2008 servers.  Or domain and DNS are integrated on 2003 Domain Controllers.

We have added a 2008 R2 server to one of the remote offices and we have made it a DC. When we installed the AD role we elected not to add the DNS role at that time.

We are now adding the DNS role.   We added it and we notice that in the DNS manager on this server we see the primary domain -- all we see under the Forward Zone is LOCALHOST. Under the Reverse Lookup ZOnes we see many of the reverse zones that exist.  

We are not sure why the primary domain zone is not listed under the Forward Zone branch and we are not sure what we need to do to correct it.

BladesAwayAsked:
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.

Brian PiercePhotographerCommented:
Use DCDIAG to check that all is OK
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
PapertripCommented:
Did you enable zone transfers for that zone?

http://technet.microsoft.com/en-us/library/cc771652.aspx
0
BladesAwayAuthor Commented:
Papertrip,

We do not have zone transfers enabled anywhere else and all the other servers in the environment that are AD and DNS controllers have the forward zone as expected.   This DNS server is also set up as AD/DNS integrated so wouldn't that mean it gets the zone from AD and not another DNS server directly?
0
BladesAwayAuthor Commented:
Apparently this issue was due to a delay in replication. Patience is a virtue apparently.  Thats for those that tried ro help.  I'm going to split the points between the two of you because the suggestions you both put forward were valid steps to consider.

Thank you.
0
Renato Montenegro RusticiIT SpecialistCommented:
Make sure the dns directory partition is scoped correctly. May be this new server is not in the same scope, so it will not receive the updates.

Check this out:

DNS zone replication in Active Directory
http://technet.microsoft.com/en-us/library/cc779655(WS.10).aspx
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
Active Directory

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.