Hurricane Electric's IPv6 Tunnel Broker Forums

Advanced search  


Welcome to Hurricane Electric's forums!

Author Topic: Forward DNS for tunnel endpoints  (Read 4217 times)


  • Newbie
  • *
  • Posts: 1
Forward DNS for tunnel endpoints
« on: November 20, 2008, 07:02:37 AM »

The tunnel endpoints (*::1 and *::2) have automatic rDNS, but the corresponding forward lookup always results in NXDOMAIN for me. Is this normal, or did I make a mistake in the setup? Basically, do a rDNS lookup on the client endpoint, and then try to look up the resulting hostname. This results in NXDOMAIN here.

So mail servers which do the standard reverse-and-forward DNS validation (IPv6 -> rDNS -> IPv6 must match connecting IPv6), will block me because they can't do the last step.

Am I not supposed to use the tunnel endpoint directly? Do I have to use a different IPv6 and setup rDNS delegation to make this work? That'd be a pain...

The tunnel itself works fine though.


  • Hero Member
  • *****
  • Posts: 786
Re: Forward DNS for tunnel endpoints
« Reply #1 on: November 22, 2008, 12:25:33 AM »

No, you're nost supposed to use the tunnel endpoints directly.  Use your routed /48 or /64 allocation for your mail server.


  • Newbie
  • *
  • Posts: 12
  • Sage
Re: Forward DNS for tunnel endpoints
« Reply #2 on: December 02, 2008, 11:36:28 AM »

You need to set up both forward DNS and reverse DNS for the IPv6 address that your mail server uses. You need to give your mail server an IPb6 address in your subnet other than the *::1 and *::2 and set up all the DNS records yourself.