Hurricane Electric's IPv6 Tunnel Broker Forums

Advanced search  

News:

Welcome to Hurricane Electric's Tunnelbroker.net forums!

Author Topic: Hostname Null on ipv6-test.com- How to fix?  (Read 3482 times)

elliottveares

  • Newbie
  • *
  • Posts: 5
    • View Profile
Hostname Null on ipv6-test.com- How to fix?
« on: January 25, 2016, 02:02:24 PM »
I ran a IPv6 test over at http://ipv6-test.com/ and everything passed expect the Hostname test for the IPv6 connectivity.

I have set all the rDND delegations to dns.he.net (ns1.he.net, ns2.he.net, etc...) in my tunnel details, although not sure if this will be of any use. For the DNS servers, I am using the IPv6 ones from OpenDNS what are configured in the IPv6 section of my Asus RT-AC66U router.

How can I pass a full 20/20 score at http://ipv6-test.com/

Hope this makes sense, regards Elliott.
Logged

cholzhauer

  • Hero Member
  • *****
  • Posts: 2560
    • View Profile
Re: Hostname Null on ipv6-test.com- How to fix?
« Reply #1 on: January 25, 2016, 05:15:27 PM »
What is your domain?
Logged

elliottveares

  • Newbie
  • *
  • Posts: 5
    • View Profile
Re: Hostname Null on ipv6-test.com- How to fix?
« Reply #2 on: January 25, 2016, 06:50:42 PM »
Domain for what, my WAN IPv4 address from my ISP is fully static and I simply have the the tunnelbroker tunnel details in my routers IPv6 config section to access IPv6 websites.

I have a domain (ipv6.mydomain.com) of mine going to my desktop's NIC's IPv6 address what I will use to test a IPv6 web server. (The IPv6 DNS A record is set to xxxx:xxxx:xxxx:xxxx::3  - where the X's are my Routed IPv6 /64 Prefix)

Could you please clarify what domain your talking about?

Elliott.
Logged

broquea

  • Sr. Network Engineer, HE.NET AS6939
  • Administrator
  • Hero Member
  • *****
  • Posts: 1671
    • View Profile
    • Another IPv6 Blog...
Re: Hostname Null on ipv6-test.com- How to fix?
« Reply #3 on: January 25, 2016, 10:53:17 PM »
"Hostname" means reverse DNS on their test. If you click the thing to the right of "Score", it tells you that you are missing rDNS for the IPv6 address you connected from, or at least their host was unable to look any up. At least, that was true for my Comcast connection I just tested with.
Logged

elliottveares

  • Newbie
  • *
  • Posts: 5
    • View Profile
Re: Hostname Null on ipv6-test.com- How to fix?
« Reply #4 on: January 26, 2016, 01:39:57 AM »
Quote
you are missing rDNS for the IPv6 address you connected from

So having the rDNS delegations set to ns1.he.net, nst.he.net, ns3.he.net, etc... at https://www.tunnelbroker.net/tunnel_detail.php is not correct then. I will wait a couple of days though in case the DNS system has not updated yet. Or should the rDNS be set to ipv6.mydomain.com ?
Logged

broquea

  • Sr. Network Engineer, HE.NET AS6939
  • Administrator
  • Hero Member
  • *****
  • Posts: 1671
    • View Profile
    • Another IPv6 Blog...
Re: Hostname Null on ipv6-test.com- How to fix?
« Reply #5 on: January 26, 2016, 02:18:48 AM »
You haven't posted what IPv6 IP you were sourcing from. If you did, we can all see if rDNS delegation and records look correct.
Logged

elliottveares

  • Newbie
  • *
  • Posts: 5
    • View Profile
Re: Hostname Null on ipv6-test.com- How to fix?
« Reply #6 on: January 26, 2016, 05:03:51 AM »
Quote
You haven't posted what IPv6 IP you were sourcing from. If you did, we can all see if rDNS delegation and records look correct.

My public IPv6 one for my desktop that I am currently browsing on, I guess I need to host a server first??
Logged

broquea

  • Sr. Network Engineer, HE.NET AS6939
  • Administrator
  • Hero Member
  • *****
  • Posts: 1671
    • View Profile
    • Another IPv6 Blog...
Re: Hostname Null on ipv6-test.com- How to fix?
« Reply #7 on: January 26, 2016, 06:45:13 AM »
Great, but WHAT is that IP configured on your desktop was my question? If we run a dig -x against it, we should see a record. No server required, if you pointed rDNS to the HE servers. That means you are managing your rDNS using dns.he.net.

I already ran a dig -x against the IP you are signing into the forums on, and see a really broken rDNS configuration, but I want to be certain about what IP you think you are sourcing from.
Logged

broquea

  • Sr. Network Engineer, HE.NET AS6939
  • Administrator
  • Hero Member
  • *****
  • Posts: 1671
    • View Profile
    • Another IPv6 Blog...
Re: Hostname Null on ipv6-test.com- How to fix?
« Reply #8 on: January 26, 2016, 09:46:03 AM »
Yeah, your rDNS is broken badly. You should revisit whatever you did:

Code: [Select]
$ dig -x 2001:470:1f1d:4ff::3

; <<>> DiG 9.9.5-11ubuntu1.2-Ubuntu <<>> -x 2001:470:1f1d:4ff::3
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 43329
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;3.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. IN PTR

;; Query time: 83 msec
;; SERVER: 127.0.1.1#53(127.0.1.1)
;; WHEN: Tue Jan 26 09:45:03 PST 2016
;; MSG SIZE  rcvd: 90

broquea@broquea-ThinkPad-T430s:~$ dig -x 2001:470:1f1d:4ff::3 +trace

; <<>> DiG 9.9.5-11ubuntu1.2-Ubuntu <<>> -x 2001:470:1f1d:4ff::3 +trace
;; global options: +cmd
. 3599838 IN NS d.root-servers.net.
. 3599838 IN NS l.root-servers.net.
. 3599838 IN NS a.root-servers.net.
. 3599838 IN NS c.root-servers.net.
. 3599838 IN NS e.root-servers.net.
. 3599838 IN NS j.root-servers.net.
. 3599838 IN NS f.root-servers.net.
. 3599838 IN NS b.root-servers.net.
. 3599838 IN NS k.root-servers.net.
. 3599838 IN NS g.root-servers.net.
. 3599838 IN NS m.root-servers.net.
. 3599838 IN NS h.root-servers.net.
. 3599838 IN NS i.root-servers.net.
;; Received 241 bytes from 127.0.1.1#53(127.0.1.1) in 230 ms

ip6.arpa. 172800 IN NS a.ip6-servers.arpa.
ip6.arpa. 172800 IN NS c.ip6-servers.arpa.
ip6.arpa. 172800 IN NS b.ip6-servers.arpa.
ip6.arpa. 172800 IN NS e.ip6-servers.arpa.
ip6.arpa. 172800 IN NS f.ip6-servers.arpa.
ip6.arpa. 172800 IN NS d.ip6-servers.arpa.
ip6.arpa. 86400 IN DS 45094 8 2 E6B54E0A20CE1EDBFCB6879C02F5782059CECB043A31D804A04AFA51 AF01D5FB
ip6.arpa. 86400 IN DS 64060 8 2 8A11501086330132BE2C23F22DEDF0634AD5FF668B4AA1988E172C6A 2A4E5F7B
ip6.arpa. 86400 IN DS 13880 8 2 068554EFCB5861F42AF93EF8E79C442A86C16FC5652E6B6D2419ED52 7F344D17
ip6.arpa. 86400 IN RRSIG DS 8 2 86400 20160205090000 20160126080000 50829 arpa. Sb4wCFg+xnXDTt/7OeGebXSy4CflspF6wZhgu6ascxRxWWZYlQ9RBnjb +XpnbizdOUkzpHEky+YVcqkvPm476w+nOn/Y6hY9+UG+MqgTdZvVIQC5 d1uaIJZPuZci86YThmn+RkOIqd4f6YrcdzhUgnCxg3md1u+p/m5IMrHv QrI=
;; Received 781 bytes from 202.12.27.33#53(m.root-servers.net) in 420 ms

4.0.1.0.0.2.ip6.arpa. 86400 IN NS x.arin.net.
4.0.1.0.0.2.ip6.arpa. 86400 IN NS sec1.authdns.ripe.net.
4.0.1.0.0.2.ip6.arpa. 86400 IN NS sec3.apnic.net.
4.0.1.0.0.2.ip6.arpa. 86400 IN NS w.arin.net.
4.0.1.0.0.2.ip6.arpa. 86400 IN NS u.arin.net.
4.0.1.0.0.2.ip6.arpa. 86400 IN NS z.arin.net.
4.0.1.0.0.2.ip6.arpa. 86400 IN NS ns2.lacnic.net.
4.0.1.0.0.2.ip6.arpa. 86400 IN NS sec1.apnic.net.
4.0.1.0.0.2.ip6.arpa. 86400 IN NS v.arin.net.
4.0.1.0.0.2.ip6.arpa. 86400 IN DS 64824 5 1 CFA09B683849459CA3E6DBAFBADD38A86548AE2C
4.0.1.0.0.2.ip6.arpa. 86400 IN RRSIG DS 8 8 86400 20160207095836 20160117031954 41469 ip6.arpa. VwmQW3MG5hUIiwIneTZZyiE9LU6+pYASsqZ/zZm95BdQilVfqzMpfx5O oIiEkiOch+dNwb6c1Rj2QPwhV6+/GLkksX4zmr+7Q2tGZzRZZ351VURe vTXy6tQsSHV8oWu6cviFiegppNyLm4siIrehuz7WY3E39Cy+MP0K2iJ6 Xr3fD6U=
;; Received 497 bytes from 199.212.0.73#53(a.ip6-servers.arpa) in 166 ms

0.7.4.0.1.0.0.2.ip6.arpa. 86400 IN NS ns3.he.net.
0.7.4.0.1.0.0.2.ip6.arpa. 86400 IN NS ns1.he.net.
0.7.4.0.1.0.0.2.ip6.arpa. 86400 IN NS ns2.he.net.
0.7.4.0.1.0.0.2.ip6.arpa. 86400 IN NS ns4.he.net.
0.7.4.0.1.0.0.2.ip6.arpa. 86400 IN NS ns5.he.net.
0.7.4.0.1.0.0.2.ip6.arpa. 10800 IN NSEC 8.7.4.0.1.0.0.2.ip6.arpa. NS RRSIG NSEC
0.7.4.0.1.0.0.2.ip6.arpa. 10800 IN RRSIG NSEC 5 10 10800 20160209170004 20160126160004 58008 4.0.1.0.0.2.ip6.arpa. QhnWyNnNWQCPv5ldwKSG9xKn46aHF3b6Kw9X/ZRLIZwJGQdAy9lgvDZf s2vk3xLJWvnh9Pygq0HkOmstkpeqY2TzSxFoJexJo1pTH7wZpLIkd7T2 wfBTjbTGLLPiKoTccoDcPjoutby1/WWsg9uLThzzQ3P5/hy1/f2xr+89 Pr8=
;; Received 423 bytes from 2001:dc0:1:0:4777::140#53(sec3.apnic.net) in 112 ms

f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns1.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns2.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns3.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns4.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns5.he.net.
;; Received 389 bytes from 2001:470:400::2#53(ns4.he.net) in 6 ms

f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns1.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns2.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns3.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns4.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns5.he.net.
;; BAD (HORIZONTAL) REFERRAL
;; Received 389 bytes from 2001:470:500::2#53(ns5.he.net) in 13 ms

f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns1.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns2.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns3.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns4.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns5.he.net.
;; BAD (HORIZONTAL) REFERRAL
;; Received 389 bytes from 216.66.1.2#53(ns4.he.net) in 15 ms

f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns1.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns2.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns3.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns4.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns5.he.net.
;; BAD (HORIZONTAL) REFERRAL
;; Received 389 bytes from 216.66.1.2#53(ns4.he.net) in 6 ms

f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns1.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns2.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns3.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns4.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns5.he.net.
;; BAD (HORIZONTAL) REFERRAL
;; Received 389 bytes from 216.218.131.2#53(ns2.he.net) in 7 ms

f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns1.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns2.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns3.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns4.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns5.he.net.
;; BAD (HORIZONTAL) REFERRAL
;; Received 389 bytes from 216.218.130.2#53(ns1.he.net) in 5007 ms

f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns1.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns2.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns3.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns4.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns5.he.net.
;; BAD (HORIZONTAL) REFERRAL
;; Received 389 bytes from 216.218.130.2#53(ns1.he.net) in 5 ms

f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns1.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns2.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns3.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns4.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns5.he.net.
;; BAD (HORIZONTAL) REFERRAL
;; Received 389 bytes from 216.66.80.18#53(ns5.he.net) in 6 ms

f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns1.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns2.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns3.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns4.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns5.he.net.
;; BAD (HORIZONTAL) REFERRAL
;; Received 389 bytes from 216.218.130.2#53(ns1.he.net) in 5 ms

f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns1.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns2.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns3.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns4.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns5.he.net.
;; BAD (HORIZONTAL) REFERRAL
;; Received 389 bytes from 216.218.130.2#53(ns1.he.net) in 5 ms

f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns1.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns2.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns3.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns4.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns5.he.net.
;; BAD (HORIZONTAL) REFERRAL
;; Received 389 bytes from 216.66.80.18#53(ns5.he.net) in 6 ms

f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns1.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns2.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns3.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns4.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns5.he.net.
;; BAD (HORIZONTAL) REFERRAL
;; Received 389 bytes from 2001:470:200::2#53(ns2.he.net) in 6 ms

f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns1.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns2.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns3.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns4.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns5.he.net.
;; BAD (HORIZONTAL) REFERRAL
;; Received 389 bytes from 216.218.130.2#53(ns1.he.net) in 7 ms

f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns1.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns2.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns3.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns4.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns5.he.net.
;; BAD (HORIZONTAL) REFERRAL
;; Received 389 bytes from 2001:470:200::2#53(ns2.he.net) in 7 ms

f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns1.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns2.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns3.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns4.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns5.he.net.
;; BAD (HORIZONTAL) REFERRAL
;; Received 389 bytes from 2001:470:200::2#53(ns2.he.net) in 5 ms

f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns1.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns2.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns3.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns4.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns5.he.net.
;; BAD (HORIZONTAL) REFERRAL
;; Received 389 bytes from 216.218.130.2#53(ns1.he.net) in 5013 ms

f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns1.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns2.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns3.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns4.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns5.he.net.
;; BAD (HORIZONTAL) REFERRAL
;; Received 389 bytes from 216.66.80.18#53(ns5.he.net) in 8 ms

f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns1.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns2.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns3.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns4.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns5.he.net.
;; BAD (HORIZONTAL) REFERRAL
;; Received 389 bytes from 2001:470:300::2#53(ns3.he.net) in 11 ms

f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns1.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns2.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns3.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns4.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns5.he.net.
;; BAD (HORIZONTAL) REFERRAL
;; Received 389 bytes from 216.218.131.2#53(ns2.he.net) in 8 ms

f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns1.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns2.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns3.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns4.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns5.he.net.
;; BAD (HORIZONTAL) REFERRAL
;; Received 389 bytes from 2001:470:500::2#53(ns5.he.net) in 11 ms

f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns1.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns2.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns3.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns4.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns5.he.net.
;; BAD (HORIZONTAL) REFERRAL
;; Received 389 bytes from 2001:470:500::2#53(ns5.he.net) in 9 ms

f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns1.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns2.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns3.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns4.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns5.he.net.
;; BAD (HORIZONTAL) REFERRAL
;; Received 389 bytes from 2001:470:200::2#53(ns2.he.net) in 8 ms

f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns1.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns2.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns3.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns4.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns5.he.net.
;; BAD (HORIZONTAL) REFERRAL
;; Received 389 bytes from 2001:470:300::2#53(ns3.he.net) in 12 ms

f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns1.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns2.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns3.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns4.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns5.he.net.
;; BAD (HORIZONTAL) REFERRAL
;; Received 389 bytes from 216.66.80.18#53(ns5.he.net) in 10 ms

f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns1.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns2.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns3.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns4.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns5.he.net.
;; BAD (HORIZONTAL) REFERRAL
;; Received 389 bytes from 2001:470:200::2#53(ns2.he.net) in 7 ms

f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns1.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns2.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns3.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns4.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns5.he.net.
;; BAD (HORIZONTAL) REFERRAL
;; Received 389 bytes from 2001:470:400::2#53(ns4.he.net) in 5010 ms

f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns1.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns2.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns3.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns4.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns5.he.net.
;; BAD (HORIZONTAL) REFERRAL
;; Received 389 bytes from 216.218.131.2#53(ns2.he.net) in 11 ms

f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns1.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns2.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns3.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns4.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns5.he.net.
;; BAD (HORIZONTAL) REFERRAL
;; Received 389 bytes from 2001:470:200::2#53(ns2.he.net) in 8 ms

f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns1.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns2.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns3.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns4.he.net.
f.f.4.0.d.1.f.1.0.7.4.0.1.0.0.2.ip6.arpa. 4900 IN NS ns5.he.net.
;; BAD (HORIZONTAL) REFERRAL
dig: too many lookups
Logged

elliottveares

  • Newbie
  • *
  • Posts: 5
    • View Profile
Re: Hostname Null on ipv6-test.com- How to fix?
« Reply #9 on: January 26, 2016, 01:50:13 PM »
I am confused by all of this  :-\, what exactly should the rDNS Delegations in the Tunnel details at tunnelbroker.net be set to?

So far I have the AAAA record for ipv6.grottotree.com set to 2001:470:1f1d:4ff::3   ipv6.grottotree.com is a sub domain of grottotree.com that I have set up to test a IPv6 web server that I have on my local machine. In my 1&1 control panel, I see no option to change the host name or rDNS of my sub domain (ipv6.grottotree.com) All I have is what is displayed below:



Logged

broquea

  • Sr. Network Engineer, HE.NET AS6939
  • Administrator
  • Hero Member
  • *****
  • Posts: 1671
    • View Profile
    • Another IPv6 Blog...
Re: Hostname Null on ipv6-test.com- How to fix?
« Reply #10 on: January 26, 2016, 02:46:18 PM »
Reverse DNS if delegated to HE nameservers, is created and managed at dns.he.net.

If you delegate it to other nameservers, those must host the records in a proper reverse zonefile.

Forward AAAA entries are not Reverse PTR entries.
Logged

tjeske

  • Newbie
  • *
  • Posts: 25
    • View Profile
Re: Hostname Null on ipv6-test.com- How to fix?
« Reply #11 on: April 11, 2016, 04:53:35 AM »
I see that you rDNS seems fixed now. If you access ipv6-test.com from the ::3-device, do you get the full 20/20 score now?
Logged

bimmerdriver

  • Newbie
  • *
  • Posts: 43
    • View Profile
Re: Hostname Null on ipv6-test.com- How to fix?
« Reply #12 on: October 21, 2016, 05:00:25 PM »
I hope no one minds me bumping this old thread. When I run ipv6-test.com, I get 19/20 due to the rdns. The hostname for the ipv6 address missing. Is it possible to fix this?
Logged

cholzhauer

  • Hero Member
  • *****
  • Posts: 2560
    • View Profile
Re: Hostname Null on ipv6-test.com- How to fix?
« Reply #13 on: October 22, 2016, 08:48:17 AM »
You just need to run rdns somewhere for the routed /64 or /48.

You should start your own thread though
Logged

bimmerdriver

  • Newbie
  • *
  • Posts: 43
    • View Profile
Re: Hostname Null on ipv6-test.com- How to fix?
« Reply #14 on: October 22, 2016, 01:15:45 PM »
Quote from: cholzhauer on October 22, 2016, 08:48:17 AM
You just need to run rdns somewhere for the routed /64 or /48.

You should start your own thread though
Done. https://forums.he.net/index.php?topic=3630.0
Logged