Hurricane Electric's IPv6 Tunnel Broker Forums

Advanced search  

News:

Welcome to Hurricane Electric's Tunnelbroker.net forums!

Author Topic: This prefix has been tagged as UNDELEGATED  (Read 5643 times)

kfl62

  • Newbie
  • *
  • Posts: 5
This prefix has been tagged as UNDELEGATED
« on: March 06, 2013, 05:34:23 PM »

Code: [Select]
telnet mail.ipv6.trst.ro 25
Trying 2a02:2f0e:3030:c0::3...
Connected to mail.ipv6.trst.ro.
Escape character is '^]'.
220 mail.ipv6.trst.ro ESMTP Postfix

dig mx ipv6.trst.ro +short
10 mail.ipv6.trst.ro.

dig aaaa mail.ipv6.trst.ro  +short
2a02:2f0e:3030:c0::3

If I try to create the 2a02:2f0e:3030:c0::/64 reverse zone I got
Code: [Select]
This prefix has been tagged as UNDELEGATED and will be removed after 7 days. Please correct this issue.
and
Code: [Select]
dig -x 2a02:2f0e:3030:c0::3 +short


dig @ns1.he.net -x 2a02:2f0e:3030:c0::3 +short
ipv6.trst.ro.

any chance to pass "An IPv6 enabled mail system, with working RDNS." test?
Logged

cholzhauer

  • Hero Member
  • *****
  • Posts: 2724
Re: This prefix has been tagged as UNDELEGATED
« Reply #1 on: March 06, 2013, 05:40:31 PM »

Probably best to email ipv6@he.net
Logged

kfl62

  • Newbie
  • *
  • Posts: 5
Re: This prefix has been tagged as UNDELEGATED
« Reply #2 on: March 06, 2013, 05:46:57 PM »

I just send an email with a link to this topic  ;)
Logged

broquea

  • Sr. Network Engineer, HE.NET AS6939
  • Administrator
  • Hero Member
  • *****
  • Posts: 1729
Re: This prefix has been tagged as UNDELEGATED
« Reply #3 on: March 06, 2013, 06:06:13 PM »

Why not email the people responsible for delegating rDNS for the IPv6 range instead? Maybe ask them to, oh just a wild idea here, DELEGATE rDNS to ns1-5.he.net so you can use dns.he.net to host your reverse zones. Or in the interest of science, maybe learn how to set up a nameserver and host your own rDNS zone :)

The IPv6 certification tests DO NOT perform direct lookups against ns1-5.he.net.

Code: [Select]
dig -x 2a02:2f0e:3030:c0:: +trace

; <<>> DiG 9.8.1-P1 <<>> -x 2a02:2f0e:3030:c0:: +trace
;; global options: +cmd
.                       83443   IN      NS      h.root-servers.net.
.                       83443   IN      NS      k.root-servers.net.
.                       83443   IN      NS      c.root-servers.net.
.                       83443   IN      NS      g.root-servers.net.
.                       83443   IN      NS      i.root-servers.net.
.                       83443   IN      NS      b.root-servers.net.
.                       83443   IN      NS      d.root-servers.net.
.                       83443   IN      NS      e.root-servers.net.
.                       83443   IN      NS      f.root-servers.net.
.                       83443   IN      NS      l.root-servers.net.
.                       83443   IN      NS      j.root-servers.net.
.                       83443   IN      NS      m.root-servers.net.
.                       83443   IN      NS      a.root-servers.net.
;; Received 449 bytes from 127.0.0.1#53(127.0.0.1) in 474 ms

ip6.arpa.               172800  IN      NS      d.ip6-servers.arpa.
ip6.arpa.               172800  IN      NS      b.ip6-servers.arpa.
ip6.arpa.               172800  IN      NS      a.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      c.ip6-servers.arpa.
;; Received 462 bytes from 2001:500:2f::f#53(2001:500:2f::f) in 25 ms

0.a.2.ip6.arpa.         86400   IN      NS      ns3.nic.fr.
0.a.2.ip6.arpa.         86400   IN      NS      pri.authdns.ripe.net.
0.a.2.ip6.arpa.         86400   IN      NS      sec1.apnic.net.
0.a.2.ip6.arpa.         86400   IN      NS      sec3.apnic.net.
0.a.2.ip6.arpa.         86400   IN      NS      sns-pb.isc.org.
0.a.2.ip6.arpa.         86400   IN      NS      tinnie.arin.net.
;; Received 246 bytes from 2001:43f8:110::11#53(2001:43f8:110::11) in 342 ms

0.f.2.2.0.a.2.ip6.arpa. 172800  IN      NS      ns2.rdsnet.ro.
0.f.2.2.0.a.2.ip6.arpa. 172800  IN      NS      ns.ripe.net.
0.f.2.2.0.a.2.ip6.arpa. 172800  IN      NS      ns1.rdsnet.ro.
;; Received 204 bytes from 2001:dc0:1:0:4777::140#53(2001:dc0:1:0:4777::140) in 606 ms

0.f.2.2.0.a.2.ip6.arpa. 86400   IN      SOA     ns1.rdsnet.ro. dns-adm.rdsnet.ro. 2013020600 10800 3600 1209600 86400
;; Received 147 bytes from 193.231.236.17#53(193.231.236.17) in 194 ms
« Last Edit: March 06, 2013, 06:15:44 PM by broquea »
Logged

kfl62

  • Newbie
  • *
  • Posts: 5
Re: This prefix has been tagged as UNDELEGATED
« Reply #4 on: March 06, 2013, 06:20:20 PM »

Quote
Why not email the people responsible for delegating rDNS for the IPv6 range instead?

I have dynamic IP from my ISP and I don't believe they 'll delegate :(

I tried with tunnel also but I can't configure my router with ppoe ipv4 (dynamic IP) and tunnel for ipv6. LoL I spend almost a day with this :)

Quote
Or in the interest of science, maybe learn how to set up a nameserver and host your own rDNS zone

I started playing with IPv6 just when I moved my nameserver to he.net and I find this certification quiz. Somehow it's odd to change again the nameservers at Registrar just to complete this process.
« Last Edit: March 06, 2013, 06:30:45 PM by kfl62 »
Logged

broquea

  • Sr. Network Engineer, HE.NET AS6939
  • Administrator
  • Hero Member
  • *****
  • Posts: 1729
Re: This prefix has been tagged as UNDELEGATED
« Reply #5 on: March 06, 2013, 06:23:13 PM »

Quote
I have dynamic IP from my ISP and I don't believe they 'll delegate :(

Ask anyways, especially since you delegate to hostnames and not IPs. Use some sort of DynDNS system (in fact dns.he.net offers one).

In fact, create a host record in your domain for something like "ns#.trst.ro" with an IPv6 address (maybe even IPv4 too!), because that is the last step anyways for the IPv6 Glue test.
That IPv6 address could be your IPv6 address!
Then they delegate to that specific hostname!
Then you spin up a DNS server that serves reverse zones, and pass with flying colors!
« Last Edit: March 06, 2013, 06:31:28 PM by broquea »
Logged

broquea

  • Sr. Network Engineer, HE.NET AS6939
  • Administrator
  • Hero Member
  • *****
  • Posts: 1729
Re: This prefix has been tagged as UNDELEGATED
« Reply #6 on: March 06, 2013, 06:33:18 PM »

Quote
I started playing with IPv6 just when I moved my nameserver to he.net and I find this certification quiz. Somehow it's odd to change again the nameservers at Registrar just to complete this process.

This has nothing to do with your domain's registration, but the reverse delegation of the IPv6 address space you are trying to use.

Authoritative name servers for your domain are the next 2 steps after this test, and if you use HE, will pass.
Logged

kfl62

  • Newbie
  • *
  • Posts: 5
Re: This prefix has been tagged as UNDELEGATED
« Reply #7 on: March 06, 2013, 06:44:32 PM »

Code: [Select]
dig aaaa ns1.trst.ro +short
2a02:2f0e:3030:c0::3

dig @ns1.he.net -x 2a02:2f0e:3030:c0::3 +short
ns1.trst.ro.
Logged

cholzhauer

  • Hero Member
  • *****
  • Posts: 2724
Re: This prefix has been tagged as UNDELEGATED
« Reply #8 on: March 06, 2013, 06:50:43 PM »

Whoops, my apologies, I overlooked the IP address and assumed it was an he tunnel address and that he was trying to do rdns at he..guess I need to get a phone with a larger screen
Logged

kfl62

  • Newbie
  • *
  • Posts: 5
Re: This prefix has been tagged as UNDELEGATED
« Reply #9 on: March 06, 2013, 06:56:53 PM »

Kelly Cochran reply to email

Quote
You may want to look at broquea's reply.  Delegation has to work all the
way up the tree.  You can't just drop in a delegation on any nameserver
and have it work.  The upstream range has to delegate the subnet, and so on.

That's true I just cleaned my trst.ro zone and I'll try an other method.
If I decide to finish certification :)
« Last Edit: March 06, 2013, 07:08:58 PM by kfl62 »
Logged

kasperd

  • Founder, Netiter ApS
  • Hero Member
  • *****
  • Posts: 955
Re: This prefix has been tagged as UNDELEGATED
« Reply #10 on: March 07, 2013, 10:35:37 AM »

Code: [Select]
0.f.2.2.0.a.2.ip6.arpa. 172800  IN      NS      ns2.rdsnet.ro.
0.f.2.2.0.a.2.ip6.arpa. 172800  IN      NS      ns.ripe.net.
0.f.2.2.0.a.2.ip6.arpa. 172800  IN      NS      ns1.rdsnet.ro.
That part looks strange to me. Why would ns.ripe.net be in there?

It doesn't matter which of them is queried next. They all give NXDOMAIN.
Logged

broquea

  • Sr. Network Engineer, HE.NET AS6939
  • Administrator
  • Hero Member
  • *****
  • Posts: 1729
Re: This prefix has been tagged as UNDELEGATED
« Reply #11 on: March 07, 2013, 11:33:04 AM »

Quote
It doesn't matter which of them is queried next. They all give NXDOMAIN.

My best guess is because no rDNS zone exists for the covering prefix or the specific /64. But that provider would know, I'd hope :D
Logged

kasperd

  • Founder, Netiter ApS
  • Hero Member
  • *****
  • Posts: 955
Re: This prefix has been tagged as UNDELEGATED
« Reply #12 on: March 07, 2013, 01:39:12 PM »

But that provider would know, I'd hope
You'd hope so. I have come across a hosting provider, who didn't know what a PTR record is.
Logged