Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We have 2 DNS domains:

  •, and various zones hosted by our ISP. Dynamic updates are not allowed.
  • example.local and various 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 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?

share|improve this question
up vote 3 down vote accepted

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


The registry key is


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

Usual Registry editing warnings apply

share|improve this answer
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 posting your answer, you agree to the privacy policy and terms of service.

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