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 understand that this is the way a PTR record would be made on a Class A subnet (

dnscmd /RecordAdd 100.250.100 PTR host.domain.tld

To clarify the syntax, this is what it should be for a Class C subnet (

dnscmd /RecordAdd 100 PTR host.domain.tld

Is that right?

Now how do I do this for a host with the IP address on a network? I'm not sure how to do this with a classless subnet mask.

share|improve this question
You have to ask the person who transferred control of that block to you. There's more than one way to do it. See RFC 2317 for the basic method. They use a CNAME to a name inside a zone they delegate to you. – David Schwartz Apr 3 '12 at 10:57
@DavidSchwartz: But there are already PTR records for other hosts in the subnet, and I cannot see any CNAME records in the forward lookup zone. – paradroid Apr 3 '12 at 11:02
You would look in the reverse zone for CNAME records. If there are none, ask the person who manages that block to put them in for you. – David Schwartz Apr 3 '12 at 11:46
up vote 0 down vote accepted

Given the heirarchal nature of PTR records, a "zonefile" can only contain a C, B, or A block of PTR records. However, RFC 2317 offers a solution to this in short by having the owner of the larger block delegate (by use of ~254 CNAME records) the PTR records in question. Of course, this will require your upstream provider to implement this correctly.

Many upstream providers simply will accept requests for updates to your PTR records. In the case of public address space, I would suggest contacting them to see what their preferred method is.

In either case, within your Windows DNS server, you will manage a single zonefile that contains a series of PTR records, which can be appended to by (e.g.):

dnscmd /RecordAdd 210 PTR host.domain.tld
share|improve this answer
I've updated my original answer to incorporate RFC 2317. Thanks for the information @DavidSchwartz! – Kyle Smith Apr 3 '12 at 22:38

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.