Hurricane Electric's IPv6 Tunnel Broker Forums

Advanced search  

News:

Welcome to Hurricane Electric's Tunnelbroker.net forums!

Author Topic: Reverse DNS not working?  (Read 5301 times)

lastninja

  • Newbie
  • *
  • Posts: 2
Reverse DNS not working?
« on: August 27, 2008, 10:20:53 AM »

Hi,

I've been assigned the tunnel 2001:470:c:137::/64. I delegated my reverse to ns1.lastninja.net and ns2.afraid.org.

The reverse DNS on my end indeed works:

Code: [Select]
$ dig -x 2001:470:c:137::2 @ns1.lastninja.net +short
armakuni.lastninja.net.

$ # to show ipv6 works on ns1.lastninja.net aswell
$ dig -x 2001:470:c:137::2 @2001:470:c:137::2 +short
armakuni.lastninja.net.

$ dig -x 2001:470:c:137::2 @ns2.afraid.org +short
armakuni.lastninja.net.

Running a dig -x 2001:470:c:137::2 +trace it terminates at the he.net DNS servers rather than show delegation to mine.

Any ideas what I maybe doing wrong?

Logged

broquea

  • Sr. Network Engineer, HE.NET AS6939
  • Administrator
  • Hero Member
  • *****
  • Posts: 1733
Re: Reverse DNS not working?
« Reply #1 on: August 27, 2008, 10:46:39 AM »

Like the tunnelbroker.net interface explains, we do not delegate rDNS for your tunnel's point-to-point allocation, only the routed allocations which in your case is 2001:470:d:137::/64

« Last Edit: August 27, 2008, 10:51:51 AM by broquea »
Logged

lastninja

  • Newbie
  • *
  • Posts: 2
Re: Reverse DNS not working?
« Reply #2 on: August 27, 2008, 03:16:30 PM »

Thanks for the information. When I read that information on the broker page earlier, I wasn't quite sure what a point-to-point link meant (i'm more familiar with the term routing block), but it makes a lot of sense now.

Thanks for clarifying.
Logged