On Thu, 2006-04-06 at 21:27 +0000, [EMAIL PROTECTED] wrote: > On Thu, Apr 06, 2006 at 10:18:08PM +0200, Jeroen Massar wrote: > > On Thu, 2006-04-06 at 10:21 -0700, David Conrad wrote: > > > Hi, > > > > > > Looking for a bit of advice... > > > > > > On 1 June 2006, the RIRs are going to stop providing support for > > > ip6.int. > > > > > > Is there any reason anyone can think of that says we shouldn't remove > > > ip6 from the int zone? > > > > Only one, which is the same as RFC1918: misconfigured (they are not > > updated) implementations will try to query for it. Thus it might be an > > idea to point ip6.int to the AS112 boxes. > > since it is not a configuration option, i'm not sure > this is an accuate statement...
On Solaris it is a configuration option. And the version of a resolver certainly also falls under 'configuration' of the machine. Upgrade it. That has been said to you and many other people already for the last couple of years already. > however the results are the same. > There is no good reason to dump yet more > traffic onto the unsuspecting auth servers. They get the lookup for ip6.int anyway, thus that does not matter and the query rate is nice and low and almost non-existent. Especially when 3ffe::/16 disappears 6 days after the shutdown of ip6.int. Recall that most of the 'old' resolvers, who are only able to do ip6.int exist on the 6bone. Those people who still use it clearly don't care about it and they can use their local ip6.int resolver to keep it running. But if you really want, just stick a: ip6.int DNAME ip6.arpa. in the roots and everybody will be happy (except Bill who looses his domain) > > On the other side, the query rate is so low that configuring it on AS112 > > is more of an overhead and annoyance than getting the queries in the > > first place. > > > > IMHO you can safely remove ip6.int from DNS. > > and IMHO, no is not the time. There is no harm in leaving the > delegations in place. Bill, even *YOU* are not using it: $ dig +trace ip6.int [..] ;; Received 25 bytes from 2001:200:0:1800::1d4c:0#53(y.ip6.int) in 265 ms $ ~/ip6_arpa.pl 2001:200:0:1800::1d4c:0 0.0.0.0.c.4.d.1.0.0.0.0.0.0.0.0.0.0.8.1.0.0.0.0.0.0.2.0.1.0.0.2.ip6.arpa $ dig +trace 0.0.0.0.c.4.d.1.0.0.0.0.0.0.0.0.0.0.8.1.0.0.0.0.0.0.2.0.1.0.0.2.ip6.arpa [..] 0.0.0.0.0.0.2.0.1.0.0.2.ip6.arpa. 3600 IN SOA ns-wide.wide.ad.jp. two.wide.ad.jp. 351 3600 900 3600000 3600 ;; Received 148 bytes from 2001:200:0:1::8#53(ns.tokyo.wide.ad.jp) in 285 ms $ host -t ptr 0.0.0.0.c.4.d.1.0.0.0.0.0.0.0.0.0.0.8.1.0.0.0.0.0.0.2.0.1.0.0.2.ip6.arpa 0.0.0.0.c.4.d.1.0.0.0.0.0.0.0.0.0.0.8.1.0.0.0.0.0.0.2.0.1.0.0.2.ip6.arpa does not exist (Authoritative answer) So come on get over it and shut it down. It was fun watching it being broken for the last decade; see 6bone mailinglist and several other ops lists which you read. Greets, Jeroen
signature.asc
Description: This is a digitally signed message part
