[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 9/9/2004 IP6.INT Removal (Was: 9/9/2006 : ip6.int shutdown?)
On Wed, Aug 04, 2004 at 03:59:35AM +0000, bmanning@vacation.karoshi.com wrote:
> > So the whole delegation thing is broken. The int. TLD servers delegate
> > ip6.int to imag.imag.fr which feels it self authoritative, but isn't
> > in the NS RRset of the ip6.int zone. And ip6.int is delegated to
> > munnari.oz.au which doesn't know about this (anymore).
>
> so... this was apparently enough to get the attention it
> deserved. the long postponed migration from imag.imag.fr.
> to ns3.nic.fr. is now "done" and imag.imag.fr. has been removed
> from the NS list in the INT zone.
> and munnari.oz.au has been removed. - more cleanup in the
> next week or two.
Well, two weeks down the road and things got even worse:
NS list summary for ip6.int. from parent (int.) servers
== flag.ep.net. ns3.nic.fr. y.ip6.int.
== z.ip6.int.
$ dig @flag.ep.net. int. SOA +norec | fgrep status:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 9740
$ dig @ns3.nic.fr int. SOA +norec | fgrep status:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 334
$ dig @y.ip6.int int. SOA +norec | fgrep status:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 17872
$ dig @z.ip6.int int. SOA +norec
;; connection timed out; no servers could be reached
So we have 3 out of 4 servers totally broken.
Looks like the importance of ip6.int is way overstated by some folks.
Regards,
Daniel