asked on
windows 2008 reverse dns zone for whole subnet?
Hi,
We have a domain that used to be a flat network (172.17.2.0 /24), but was recently changed to include other subnets too, including 172.17.3.0/23 and 172.17.5.0/24.
I created a single reverse DNS zone called:
0.17.172.in-addr.arpa
But when i try to go to a forward DNS Host (A) record and update its PTR (for a host that's now on the 172.17.3.0/24 subnet), i get the error: "Warning: The associated PTR record cannot be created, probably because the referenced reverse lookup zone cannot be found".
What am I doin wrong?
We have a domain that used to be a flat network (172.17.2.0 /24), but was recently changed to include other subnets too, including 172.17.3.0/23 and 172.17.5.0/24.
I created a single reverse DNS zone called:
0.17.172.in-addr.arpa
But when i try to go to a forward DNS Host (A) record and update its PTR (for a host that's now on the 172.17.3.0/24 subnet), i get the error: "Warning: The associated PTR record cannot be created, probably because the referenced reverse lookup zone cannot be found".
What am I doin wrong?
DNS
Last Comment
Mystical_Ice
Can you ping all the other subnets from each direction? By IP and name? I dont think you would need a reverse look up zone.
ASKER CERTIFIED SOLUTION
Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a questionASKER
This is correct - for future reference if someone is reading this question with the same problem, with reverse DNS in windows 2008 you can only specify /8, /16, or /24 subnets (or 255.0.0.0, 255.255.0.0, or 255.255.255.0 subnets respectively).
Thus even though our 172.17.2.150 /23 (255.255.254.0) contains addresses from 172.17.3.0 through 172.17.4.255, I had to create two seperate reverse lookup zones:
0.4.17.172.in-addr.arpa
and
0.3.17.172.in-addr.arpa
Did that, and right away PTR records started getting created.
Thus even though our 172.17.2.150 /23 (255.255.254.0) contains addresses from 172.17.3.0 through 172.17.4.255, I had to create two seperate reverse lookup zones:
0.4.17.172.in-addr.arpa
and
0.3.17.172.in-addr.arpa
Did that, and right away PTR records started getting created.
This is the best money I have ever spent. I cannot not tell you how many times these folks have saved my bacon. I learn so much from the contributors.
rwheeler23