Greetings, (First time writing to this Mailing list) Are there any temporary solutions to this ip6.int. broken problem? or do we just have to wait until 9/9? Some applications keep asking for ip6.int. and servers not responding cause delays to the application services. Would be very helpful if someone could give me tips. Thank you ----- Seiichi 2004/08/20 09:39:40 +0200にRobert Martin-Leg鈩e <robert@martin-legene.dk>さんに頂いた 「Re: [ipv6-wg@ripe.net] Re: 9/9/2004 IP6.INT Removal (Was: 9/9/2006 : ip6.int shutdown?)」への返事です。
On Thu, Aug 19, 2004 at 09:59:51PM +0200, Daniel Roesen wrote:
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.
Shouldn't you be asking these servers for ip6.int instead of asking them for int.? Either way, I seem to be getting the same results.
For int. itself, it seems that only ns.isi.edu is not authoritative.
-- Robert Martin-Leg鈩e