Share via


Consolidating DNS Reverse Zones to a single zone

Question

Thursday, October 24, 2013 9:53 PM

Hi guys,

We have a 2008R2 single domain forest.  We use standard Class A private network for our entire company.  We use the 2nd octet to specify which site and the 3rd octet to specify the different vlans in each site.  So we use 10.X for everything.  We have a single forward lookup zone and a bunch of different 10.X reverse zones.  Like 1.10.in-addr.arpa and 22.10.in-addr.arpa, etc.  Can I combine all of the reverse zones to a single 10.in-addr.arpa?  It makes it easier for zone transfer setups, etc.  I do not know what on our network might rely on a reverse lookup, but if I can simplify this to a single zone, any recommendations for how the clients will reregister their reverse address would be appreciated.  Biggest concerns are probably servers, but not even sure how important those reverse records might be.  I am guessing that clients reverse addresses are not as important and DHCP might handle when they renew(We use DDNS).

Thanks,

Dan

Dan Heim

All replies (2)

Friday, October 25, 2013 2:47 PM âś…Answered

Dan,

See if these help.

How to Consolidate Many Reverse DNS Zones into Fewer Larger Reverse DNS Zones
The Tool:  DNSExporter (obtainable from Microsoft Support under the toolbox search phrase of "DNS Record Export")
http://blogs.msdn.com/b/richpec/archive/2008/08/24/how-to-consolidate-many-reverse-dns-zones-into-fewer-larger-reverse-dns-zones.aspx

PowerShell Script To Combine DNS Zones
http://blogs.technet.com/b/ashleymcglone/archive/2010/09/02/powershell-script-to-combine-dns-zones.aspx

Ace Fekay
MVP, MCT, MCITP/EA, MCTS Windows 2008/R2 & Exchange 2007, Exchange 2010 EA, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services
Technical Blogs & Videos: http://www.delawarecountycomputerconsulting.com/

This post is provided AS-IS with no warranties or guarantees and confers no rights.


Sunday, October 27, 2013 2:25 PM

Hi,

Based on my research, reverse lookup zones and PTR resource records are not necessary for Active Directory to work, but you need them if you want clients to be able to resolve FQDNs from IP addresses. Also, PTR resource records are commonly used by some applications to verify the identities of clients.

More information:

Understanding Reverse Lookup

http://technet.microsoft.com/en-us/library/cc730980.aspx

Best regards,

Susie