0

We have 2 DNS domains:

  • example.com, and various in-addr.arpa zones hosted by our ISP. Dynamic updates are not allowed.
  • example.local and various in-addr.arpa zones for our private networks, hosted internally and used for AD, dynamic updates configured and working just fine.

Some of our Windows servers are located at a hosting datacentre and are using public IP addresses. When these servers attempt to update their PTR records dynamically, the attempts fail because the ISP's DNS does not allow it, and an informational event is logged.

These servers happily update their A records in example.local and we maintain the example.com and PTR records manually via the ISP.

Is there some registry hack that I can use to tell these servers to only register the relevant A records and not PTR records, so that they will stop logging redundant informational events in the event log?

3

Yes, you can edit a registry key on the servers themselves to tell them not to register ptr records, you can find it here:

 SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

The registry key is

DisableReverseAddressRegistrations 

Set it to 1 to not register PTR records, 0 to turn it back on.

Usual Registry editing warnings apply

  • Hmmm, that looks 100% like exactly what I need but for some reason it's not working. I still get an event 11160 from source Dnsapi, "The system failed to register pointer (PTR) resource records (RRs) for network adapter....." – ThatGraemeGuy Nov 17 '09 at 7:28
  • I've accepted your answer because it is correct, but it still doesn't work for some reason. – ThatGraemeGuy Dec 2 '09 at 13:54

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.