Skip to content
pflog's profile

New problem solver

 • 

21 Messages

Thursday, November 21st, 2013 11:00 AM

rDNS Delegation

Hi,

 

I have a /29 block and would like to request reverse DNS delegation of my IP block via RFC 2317.

 

I can send an IM with the pertinent information, just let me know what info you need.

 

Thanks!

Retired Employee

 • 

1.9K Messages

11 years ago

HI pflog.  In order to proceed with the request our IP Engineers will need the following information:

1.Your full name

2. Account number

3. IP Scope

4. Server information (ex: ns.yourdomain.com)

Please send it to me via private message and I will contact the appropriate department.

 

Thank You

 

New problem solver

 • 

21 Messages

11 years ago

Hi Jon,

 

Just to be clear, the way this is being done is via RFC 2317, right? I want to make sure I set my bind configuration up ahead of time.

 

Thanks!

New problem solver

 • 

21 Messages

11 years ago

I sent you a PM with the info, and my nameserver is setup and ready to go!

New problem solver

 • 

21 Messages

11 years ago

Hi  John,

 

Is there some problem with the information I've provided? I see others who requested the same changes AFTER me have theirs setup, but mine is still not active.

 

Please let me know if there is anything I need to do on my end.

 

Regards,

Josh

New problem solver

 • 

28 Messages

11 years ago

Hello!

 

Comcast_John is pretty solid with stuff, especially the rDNS. Actaully, I am pretty sure he is just a bot, but I could be wrong :).

Anyways, is it possible that you are looking for a different reverse zone naming format?

 

The classless rDNS zone naming is ISP dependent. For me, Comcast used a zone name of  :

 

28-208.12.11.10.in-addr-arpa

 

For an ip block of 10.11.12.208/28

 

Take care!

 

John

New problem solver

 • 

21 Messages

11 years ago

Hi John, thanks for the reply 🙂

 

I'm fairly sure I have it setup correctly on my end. If I do a dig +trace:

 

dig ptr +trace 1895.73.xxx.yyy.in-addr.arpa

 

It shows comcast's NS not mine and the PTR record doesn't match what I have on my end:

 

189.73.yyy.xxx.in-addr.arpa. 3600 IN     PTR     yyy-xxx-73-189-Sacramento.hfc.comcastbusiness.net.

So I think it's not even setup on their end, but it's been a while since I've done an RFC2317 setup. What should I be querying my local nameserver for to confirm it's working? I thought it would be this which works:

 

$ dig +short ptr 189.184/29.73.xxx.yyy.in-addr.arpa @ns.pflog.net
test.MYDOMAINHERE.net.

The zone's origin looks like this:

 

$ORIGIN 184/29.73.xxx.yyy.in-addr.arpa.

 

Should that be this instead?

 

$ORIGIN 184-29.73.xxx.yyy.in-addr.arpa.

 

Even if I had things wrong, I'd expect with a dig +trace to get an NXDOMAIN if it were setup already and my NS was misconfigured, but I'm getting a valid PTR response, just the wrong (old) one.

 

Thanks!

New problem solver

 • 

28 Messages

11 years ago

Hello!

 

DNS is not my forte, but maybe this info will help.

 

My rDNS is delegated and working. My static ip block is yyy.xxx.50.208/28. When I do a reverse lookup on yyy.xxx.50.209, I get the following response :

 

209.50.xxx.yyy.in-addr.arpa. CNAME IN 3600 71ms 209.28-208.50.xxx.yyy.in-addr.arpa.

 

Trying a reverse lookup on the network/broadcast IP will return a PTR record, like :

 

208.50.xxx.yyy.in-addr.arpa. PTR IN 3600 83ms yyy-xxx-50-208-static.hfc.comcastbusiness.net.

 

It kind of looks like it might not be setup, but when it is, my guess is that the zone name might be :

 

$ORIGIN 29-184.73.xxx.yyy.in-addr.arpa.

 

Take care!

 

John