[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Proposal for shutdown of ip6.int?
On Thu, Feb 12, 2004 at 12:14:59AM +0200, Pekka Savola wrote:
> As soon as the 6bone space is available through ip6.arpa, I think the
> resolvers should remove support for ip6.int. That'll force (more or
> less) people who wouldn't be otherwise bothered to change from ip6.int
> to ip6.arpa.
Is it my imagination, or are chunks of the ip6.int tree still broken
by various odd deligations? y.ip6.int and z.ip6.int don't seem to
agree with other name servers and are deligating to some lame
servers. I'd guess this is a pretty strong motivation to move to
ip6.arpa.
David.
servers: y.ip6.int z.ip6.int
7.0.1.0.0.2.ip6.int. 86400 IN NS auth03.ns.uu.net.
7.0.1.0.0.2.ip6.int. 86400 IN NS flag.ep.net.
7.0.1.0.0.2.ip6.int. 86400 IN NS munnari.oz.au.
7.0.1.0.0.2.ip6.int. 86400 IN NS ns.apnic.net. Lame?
7.0.1.0.0.2.ip6.int. 86400 IN NS ns.ripe.net.
7.0.1.0.0.2.ip6.int. 86400 IN NS ns3.nic.fr.
7.0.1.0.0.2.ip6.int. 86400 IN NS sunic.sunet.se.
7.0.1.0.0.2.ip6.int. 86400 IN NS svc00.apnic.net. Lame?
servers: ns3.nic.fr flag.ep.net ns.ripe.net munnari.oz.au
7.0.1.0.0.2.ip6.int. 432000 IN NS auth03.ns.uu.net.
7.0.1.0.0.2.ip6.int. 432000 IN NS munnari.oz.au.
7.0.1.0.0.2.ip6.int. 432000 IN NS ns.ripe.net.
7.0.1.0.0.2.ip6.int. 432000 IN NS ns3.nic.fr.
7.0.1.0.0.2.ip6.int. 432000 IN NS sec1.apnic.net.
7.0.1.0.0.2.ip6.int. 432000 IN NS sec3.apnic.net.
7.0.1.0.0.2.ip6.int. 432000 IN NS sunic.sunet.se.
7.0.1.0.0.2.ip6.int. 432000 IN NS tinnie.arin.net.