Reverse Lookup Zone - issue

I have 2 DNS servers, both Windows 2008 R2 servers. One is the primary and one is the secondary. My network IP range is 10.x.x.x. I created my forward lookup zone and it started populating with workstation. I had to manually create a reverse lookup zone called 0.0.10.in-addr.arpa. It populated with the Name Server (NS) dns1.name.corp and dns2.name.corp and thats it. When I go to the forwarding lookup zone and try to check the box "Update associated pointer (PTR) record" I get the following message...

Warning: The Associated pointer (PTR) record cannot be created, probably because the reference reverse lookup zone cannot be found"

Any ideas?
clynch302Asked:
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.

MaheshArchitectCommented:
Ensure that reverse lookup zone is set with allow secure dynamic updates and it is replicated to all domain controllers in domain
0
Vaseem MohammedCommented:
Does the PTR record for Host(A) record exist in Reverse lookup zone?
The Host(A) record was created manually or by the computer account?
Try to run ipconfig /registerdns from the client PC and see if the PTR gets created.
0
clynch302Author Commented:
Mahesh - Yes it is set up that way.

Vaseem - There are no PTR records. The Host(A) was created by the computer account. I did an ipconfig /registerdns on all machines on the network.
0
Become a Leader in Data Analytics

Gain the power to turn raw data into better business decisions and outcomes in your industry. Transform your career future by earning your MS in Data Analytics. WGU’s MSDA program curriculum features IT certifications from Oracle and SAS.  

clynch302Author Commented:
I just figured out my bonehead mistake. My DHCP clients are on 10.10.1.x and 10.10.2.x. The reverse lookup zone was set at 10.0.0.0. When I created the zone for 10.10.1.x it started to populate.
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
Vaseem MohammedCommented:
:-) good luck
0
clynch302Author Commented:
I was able to figure it out on my own...
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.