<div>
<div class="content wysiwyg-content">
How granular do the reverse lookup zones need to get? &nbsp;For instance.. if I have several subnets under 172.16.0.0, should create reverse lookup zones for each or is the 172.16.0.0 reverse lookup zone enough? &nbsp;What difference does it make in either case?
</div>
</div>


How granular do the reverse lookup zones need to get?  For instance.. if I have several subnets under 172.16.0.0, should create reverse lookup zones for each or is the 172.16.0.0 reverse lookup zone enough?  What difference does it make in either case?

Reverse lookup zones in DNS (Windows 2003)

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).

Windows Server 2003

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.