<div>
<br />
Are they all dynamically registered in the Forward Lookup Zone?<br />
<br />
If they are you wouldn't have to wait long before the clients added in the Reverse Lookup entries if you create the zone.<br />
<br />
Of course if you're talking about static entries it's a bit of a different matter.<br />
<br />
Chris
</div>



Are they all dynamically registered in the Forward Lookup Zone?

If they are you wouldn't have to wait long before the clients added in the Reverse Lookup entries if you create the zone.

Of course if you're talking about static entries it's a bit of a different matter.

Chris

<div>
We do have secure updates selected for dynamic updates, but all the hosts have static IPs... So, I don't know when they would re-register with DNS?
</div>


We do have secure updates selected for dynamic updates, but all the hosts have static IPs... So, I don't know when they would re-register with DNS?

<div>
<div class="content wysiwyg-content">
We currently have a Primary AD-Int forward lookup zone, but no reverse lookup zone was created. &nbsp;Names do get resolved when doing an NSLOOKUP by IP, so I suppose it is doing this by NBT queries. &nbsp;Anyway, I'd like to create the reverse lookup zone, but we have over 100 records in the forward lookup zone. &nbsp;Rather than going into each record and checking 'Update associated PTR record', is there a faster way to do a bunch of them at once?
</div>
</div>


We currently have a Primary AD-Int forward lookup zone, but no reverse lookup zone was created.  Names do get resolved when doing an NSLOOKUP by IP, so I suppose it is doing this by NBT queries.  Anyway, I'd like to create the reverse lookup zone, but we have over 100 records in the forward lookup zone.  Rather than going into each record and checking 'Update associated PTR record', is there a faster way to do a bunch of them at once?

Is there a way to move all the records into a new reverse lookup zone?

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.