[6bone] 3.f.f.e.ip6.int. delagations removed?
Jeroen Massar
jeroen at unfix.org
Thu May 6 07:55:17 PDT 2004
On Thu, 2004-05-06 at 16:32, Petr Baudis wrote:
> Dear diary, on Thu, May 06, 2004 at 03:30:51PM CEST, I got a letter,
> where Jeroen Massar <jeroen at unfix.org> told me, that...
> > On Thu, 2004-05-06 at 10:45, Christian Schild wrote:
> > > Dear all,
> > >
> > > it looks like that since a few days ago the delegation for
> > > 4.0.e.f.f.3.ip6.int. to our name server is gone. Is there a reason why?
> > > I'd like to help repairing that as quick as possible.
> > >
> > > Checking the e.f.f.3.ip6.int. zone it is pretty empty compared to the
> > > number of valid 6bone prefixes? Was there some cleanup lately?
> >
> > Cool, finally some movement! ;)
> [ip6.arpa hopes]
>
> Is there? Well, I for one still see no e.f.f.3.ip6.arpa. delegation :-(.
> And our (3ffe:80e0::/28) delegation disappeared from ip6.int. as well,
> but it looks it reappeared right now. I asked Bob Fink about what's up
> yesterday but got no reply yet (perhaps because I should've probably got
> in touch with Bill Manning instead).
If you query z.ip6.int directly it works indeed.
z.ip6.int:
e.f.f.3.ip6.int. 6400 IN SOA dot.ep.net.
hostmaster.ep.net. 2002091315 900 900 4800 9600
flag.ep.net:
e.f.f.3.ip6.int. 6400 IN SOA dot.ep.net.
hostmaster.ep.net. 2002091315 900 900 4800 9600
y.ipt.int doesn't know of anything
imag.imag.fr:
e.f.f.3.ip6.int. 6400 IN SOA dot.ep.net.
hostmaster.ep.net. 2002091315 900 900 4800 9600
and on ns3.nic.fr, suddenly we see hexago suddenly with a new serial:
e.f.f.3.ip6.int. 259200 IN SOA sonata.hexago.com.
postmaster.hexago.com. 2004043002 10800 900 259200 86400
BUT:
1.1.8.e.f.f.3.ip6.int. 259200 IN NS ns1.ipng.nl.
1.1.8.e.f.f.3.ip6.int. 259200 IN NS ns2.ipng.nl.
1.1.8.e.f.f.3.ip6.int. 259200 IN NS ns3.ipng.nl.
That is from a *old* zonefile, it had been changed to ns1/2/3.sixxs.net
about a year ago, if it isn't more. Not that it matters much as that
prefix will be taken out of use and returned per 6/6/2004 when IPng.nl
will be laid next to the roses.
One *COOL* thing here though:
$ dig @sonata.hexago.com e.f.f.3.ip6.arpa
$ dig @sonata.hexago.com e.f.f.3.ip6.arpa soa
; <<>> DiG 9.2.4rc2 <<>> @sonata.hexago.com e.f.f.3.ip6.arpa soa
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 51575
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 3
;; QUESTION SECTION:
;e.f.f.3.ip6.arpa. IN SOA
;; ANSWER SECTION:
e.f.f.3.ip6.arpa. 259200 IN SOA sonata.hexago.com.
postmaster.hexago.com. 2004043002 10800 900 259200 86400
;; AUTHORITY SECTION:
e.f.f.3.ip6.arpa. 259200 IN NS ns3.nic.fr.
e.f.f.3.ip6.arpa. 259200 IN NS flag.ep.net.
e.f.f.3.ip6.arpa. 259200 IN NS imag.imag.fr.
e.f.f.3.ip6.arpa. 259200 IN NS sonata.hexago.com.
;; ADDITIONAL SECTION:
imag.imag.fr. 6404 IN A 129.88.30.1
sonata.hexago.com. 259200 IN A 209.71.226.2
sonata.hexago.com. 259200 IN AAAA 2001:5c0:0:1::2
Joy joy... Hexago is going to run ip6.arpa for 6bone!!! ;)
Now they'll just have to kick ICANN, but they probably won't.
Also:
;; ANSWER SECTION:
e.f.f.3.ip6.arpa. 259200 IN NS sonata.hexago.com.
e.f.f.3.ip6.arpa. 259200 IN NS ns3.nic.fr.
e.f.f.3.ip6.arpa. 259200 IN NS flag.ep.net.
e.f.f.3.ip6.arpa. 259200 IN NS imag.imag.fr.
Also good to see that there are both US and European boxes there.
They might want to add a box in the APNIC region, maybe APNIC can help
them out there? The connection to Hexago seems flay though:
jeroen at purgatory:~$ traceroute6 2001:5c0:0:1::2
traceroute to 2001:5c0:0:1::2 (2001:5c0:0:1::2) from
2001:7b8:300:0:290:27ff:fe24:c19f, 30 hops max, 16 byte packets
1 gw-1.ede-01.nl.sixxs.net (2001:7b8:2ff::1) 32.611 ms 11.677 ms
12.514 ms
2 sixxs-gw.ipv6.network.bit.nl (2001:7b8:3:4f:290:6900:4fc6:d81f)
11.959 ms 14.168 ms 14.931 ms
3 jun1.sara.ipv6.network.bit.nl (2001:7b8::205:8500:120:7c1f) 13.186
ms 13.347 ms 13.308 ms
4 nikhef.ams-ix.ipv6.intouch.net (2001:7f8:1::a500:8954:1) 69.685 ms
45.262 ms 38.101 ms
5 tu-0.viagenie.mlpsca01.us.b6.verio.net (2001:418:0:4000::26)
170.824 ms 145.213 ms 163.389 ms
6 * * *
7 * * *
Tracing to 6bone, which is supposed to also be hosted by Hexago, traces
correctly over Viagenie (also Hexago, or was it... argh politics)...
$ dig @ns3.nic.fr 1.1.8.e.f.f.3.ip6.arpa ns
; <<>> DiG 9.2.4rc2 <<>> @ns3.nic.fr 1.1.8.e.f.f.3.ip6.arpa ns
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 56623
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 3, ADDITIONAL: 0
;; QUESTION SECTION:
;1.1.8.e.f.f.3.ip6.arpa. IN NS
;; AUTHORITY SECTION:
1.1.8.e.f.f.3.ip6.arpa. 259200 IN NS ns1.ipng.nl.
1.1.8.e.f.f.3.ip6.arpa. 259200 IN NS ns2.ipng.nl.
1.1.8.e.f.f.3.ip6.arpa. 259200 IN NS ns3.ipng.nl.
Thus they *are* working on it, would have been nice if they told us so
though (and if they had used a recent zone file etc...)
Notez bien that nic.fr is also the box hosting .fr/.nl and various
others. And the best thing: they have a very anxious IPv6 person who
will make sure that IPv6 will stay working.
> BTW, we (XS26) are not "production v6" people but we were asking about
> e.f.f.3.ip6.arpa. for ages, especially on RIPE mailing lists etc. We've
> only pretty much given up after things didn't move a single bit for
> about 1.5 years...
RIPE has no business with 6bone, except maybe for the fact that David is
the RIPE IPv6 wg chair and runs the whois service. But the relation ends
there...
Complaining should be done here, but alas, not much response or updates
:(
Greets,
Jeroen
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 240 bytes
Desc: This is a digitally signed message part
Url : http://mailman.isi.edu/pipermail/6bone/attachments/20040506/47c6dd5f/attachment.bin
More information about the 6bone
mailing list