DNS Reverse Lookup Zone for a 22 bit subnet

[machin05]

Hi folks,

 

Need a bit of help setting up a reverse lookup zone on our new DNS AD server.

 

I'm building a new Active Directory from scratch so am trying to get everything as neat and tidy as possible. Our IP range is 10.122.36.0 with a subnet mask of 255.255.252.0 giving us up to 10.122.39.254 on our address range.

 

On our existing setup I have created reverse lookup zones for each subnet - eg: 36.122.10.in-addr.arpa , 37.122.10.in-addr.arpa etc. which worked fine, but that seems a little messy to me.

 

I have done a little googling and thought I had the answer of setting up the following zone: 1-22.36.122.10.in-addr.arpa in which the two Name Server entries are present as is the SOA record (this points to itself). However when I look in the forward lookup zone and try and create an associated PTR record on any existing hosts I get the following error:

 

"Warning; The associated pointer (PTR) record cannot be created, probably because the referenced reverse lookup zone cannot be found"

 

No new PTR records are being automatically created in the reverse lookup zone I have created.

 

Am I going about this all wrong??

[jinnantonnixx]

Just make a single reverse lookup zone 122.10.in-addr.arpa.

 

That's all you need.

Edited April 8, 2014 by jinnantonnixx

[machin05]

There's a chance we might, in the future, connect to our neighbouring school which is on a 10.122.164/22 network so I wanted to avoid any overlap with that subnet TBH.

[stomie]

I would also like to know the answer. Same issue. I don't want to input 200 class C addresses in Reverse lookup.

[Ric_]

We have a similar problem adding PTR records to our /27 and /28 ranges... it's a Windows bug and you'll probably find that using the command line tools rather than the GUI will let you add the records. I'm not sure if this will work for auto-registration though.