Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

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

I've inherited a Windows network with Windows server based DNS and there are issues, such as not being able to update PTR records, etc.

So, I am at a branch office with our own AD domain and DNS on the DCs. Currently, for our local domain, all Forward lookup zones are AD integrated and controlled by us.

Reverse look up zones seem to be setup differently and no one knows why. The main corporate private class A (10.x.x.x) for the company is set up as a single secondary zone from the main office overseas. Most of our infra here falls into a few 16 bit ranges within that. (like 10.101.x.x through 10.102.x.x).

What should be done here?

Do I need some sort of Reverse DNS delegation from the primary overseas DNS owner for our segments? If there is one large 10.x.x.x Reverse DNS zone, can I just create the 10.101.x.x and 10.102.x.x zones with the most specific being resolved first (like a routing table)? Or would I have to completely breakout the larger 10.x.x.x scope into all the individual segments?

share|improve this question
A question before I post an answer: What is your underlying concern regarding the rDNS zone(s)? rDNS zones and records aren't used by any function or component of AD, aren't normally used by hosts or by Windows clients, and are seldom used by applications. – joeqwerty Aug 27 '12 at 16:08

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.