<div>
Yes, you can do that.<br />
<br />
Tools: At least you only have one record type to deal with :)<br />
<br />
My PowerShell DNS module can do it:<br />
<br />
<a href="http://dnsshell.codeplex.com/" rel="ugc">http://dnsshell.codeplex.com/</a><br />
<br />
Something along the lines of this, although I reserve the right to have forgotten and may need to check tomorrow:<br />

<pre><code class="code-1 nolinks" id="code-20-35771888-1"><span>Get-DnsZone -Reverse | Where-Object { $_.ZoneName -Match '\d{3}\.200\.199' } | ForEach-Object {</span>
<span>  Get-DnsRecord -RecordType PTR -Zone $_.ZoneName | New-DnsRecord -Zone &quot;200.199.in-addr.arpa&quot;</span>
<span>}</span>
</code></pre>
Once I fix the syntax, I kind of assume it'll break, there are a few things to watch out for. Most notably all dynamic records will be imported as static.<br />
<br />
Chris
</div>


<div>
Thanks Chris!<br />
<br />
Not to pile on to the question but... how hard would it be for you to whip up a PowerShell script that would report all static records that are not of SOA or NS type? &nbsp;The script could run against all reverse lookup zones in the entire domain.<br />
<br />
I'm essentially looking for static stragglers or dynamics that I might need to watch out for. &nbsp;Is this a royal pain?
</div>


<div>
Not hard at all, but I'll have to test it properly in the morning, no MS DNS servers at home, only BIND.<br />
<br />
Chris
</div>


<div>
Tell you what, hold off on that if you would. &nbsp;I don't want you to do something I might not need.<br />
<br />
I'm just struggling with how to properly do this. &nbsp;I don't want to run off haphazardly deleting zones.<br />
<br />
If I create a zone that &quot;overlaps&quot; others with a small mask, will clients register there instead? &nbsp;In other words, let's say I create a zone for 199.200.x.x and I have a bunch of other zones already defined with a larger mask, say 199.200.100 and 199.200.101. &nbsp;Will the registrations begin to occur against 199.200? &nbsp;Or will the PTR records continue to update against the old zones, at least until the timestap expires?<br />
<br />
My worry is wiping out records and temporarily breaking an application that does require a reverse lookup record until DNS registration reoccurs. &nbsp;So I'd rather create a new zone, have clients begin to register there, move over the static records manually as there aren't that many, and then delete the old zones in time, perhaps weeks. &nbsp;Is this a valid strategy?<br />
<br />
Thanks for all the help Chris. &nbsp;Most appreciated.
</div>


<div>
Beautiful. &nbsp;Thanks for all the help Chris.
</div>


<div>
<div class="content wysiwyg-content">
Folks -<br />
<br />
I'd like to reduce the number of Reverse Lookup Zones I have in my forest. &nbsp;I'm wondering if its possible to do this by specifying a zone with a smaller bit mask and removing the zones with larger masks?<br />
<br />
In other words... let us say I own the entire 199.200.x.x Class B range. &nbsp;If I have a reverse lookup zone for 199.200.100, 199.200.101, 199.200.102, etc. &nbsp;Is it possible to consolidate these into one zone named 199.200.x.x rather than specifying each Class C segment? &nbsp;This would allow me to significantly reduce my number of zones with no impact (as far as I see it - am I wrong?)<br />
<br />
Second question - Are there any tools to help me migrate the records, static or otherwise, from one zone to another?<br />
<br />
Let me know if I need to clarify what I'm after here.
</div>
</div>


Folks -

I'd like to reduce the number of Reverse Lookup Zones I have in my forest.  I'm wondering if its possible to do this by specifying a zone with a smaller bit mask and removing the zones with larger masks?

In other words... let us say I own the entire 199.200.x.x Class B range.  If I have a reverse lookup zone for 199.200.100, 199.200.101, 199.200.102, etc.  Is it possible to consolidate these into one zone named 199.200.x.x rather than specifying each Class C segment?  This would allow me to significantly reduce my number of zones with no impact (as far as I see it - am I wrong?)

Second question - Are there any tools to help me migrate the records, static or otherwise, from one zone to another?

Let me know if I need to clarify what I'm after here.

Can I consolidate my Reverse Lookup Zones by specifying a more general zone?  Are there tools to help me with the records migration?

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.

Active Directory

The Domain Name System (DNS) is a hierarchical, globally distributed system responsible for associating the name of a computer, service or other resource into an IP address for connecting to the Internet or a private network. Most prominently, it translates domain names to the numerical IP addresses needed for the purpose of computer services and devices worldwide.

Windows Server 2008 and Windows Server 2008 R2, based on the Microsoft Vista codebase, is the last 32-bit server operating system released by Microsoft. It has a number of versions, including including Foundation, Standard, Enterprise, Datacenter, Web, HPC Server, Itanium and Storage; new features included server core installation and Hyper-V.