Best practise for reverse lookup zones for multiple subnets

[Curtis Fray]

Hi,

I've set up a Windows 2003 DNS server which is used by computers in multiple
subnet zones. At the moment I'm setting up a Reverse Lookup Zone for each
subnet, ie:

192.168.151.x
192.168.174.x
192.168.182.x

Would it be better for me to simply create one <192.168.x.x> zone rather
than lots of seperate ones? Are there any advantages or disadvantages to
either method?

If I did change this now, what would be the best way to get the existing
records in to the one <192.168.x.x> zone and remove all the seperate ones?

Thanks,

Curtis.

====================================
When replying by email please remove the X
====================================

 

[Kevin D. Goodknecht Sr. [MVP]]

In

Hi,

I've set up a Windows 2003 DNS server which is used by
computers in multiple subnet zones. At the moment I'm
setting up a Reverse Lookup Zone for each subnet, ie:

192.168.151.x
192.168.174.x
192.168.182.x

Would it be better for me to simply create one
<192.168.x.x> zone rather than lots of seperate ones?

The truth?
What ever works for you.

Are
there any advantages or disadvantages to either method?

If you only have one DNS server for all three subnets it doesn't matter.
If you have different DNS servers for each subnet, use separate zones if the
clients only use the DNS server on its subnet.

If I did change this now, what would be the best way to
get the existing records in to the one <192.168.x.x> zone
and remove all the seperate ones?

If the Clients all support DDNS, create the zone, set it to allow dynamic
updates and let the clients register there own PTR records.
The truth be known though, unless you have an application that requires a
reverse lookup, a reverse lookup zone is not required.