[6bone] y.ip6.int, munnari.oz.au broken (ip6.int)?
Bill Manning
bmanning@ISI.EDU
Mon, 16 Jun 2003 09:19:59 -0700 (PDT)
% On Jun 15, Ben Winslow <rain@bluecherry.net> wrote:
%
% >I was wondering if I was the only person seeing this (I don't think
% >that's the case), or if it's a known problem, or whatever. I'm also
% I think munnari has been lame for ip6.int most of the time, you can find
% old threads about this in the archive (but I cannot remember any good
% explanation of this situation).
% Y used to work some weeks ago, IIRC.
%
%
% BTW, this is even nicer:
% dig +norec 8.1.4.1.1.0.0.2.ip6.int ns @z.ip6.int
%
% --
% ciao, |
% Marco | [1521 suqKOOW.dH4lI]
first off, several of these systems are IPv6 -ONLY-
and there is the interesting issue of route propogation... :(
that said:
$ dig +norec 8.1.4.1.1.0.0.2.ip6.int ns @z.ip6.int
; <<>> DiG 9.3.0s20021217 <<>> +norec 8.1.4.1.1.0.0.2.ip6.int ns @z.ip6.int
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58647
;; flags: qr; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;8.1.4.1.1.0.0.2.ip6.int. IN NS
;; AUTHORITY SECTION:
4.1.1.0.0.2.ip6.int. 86400 IN NS noserver.
;; Query time: 0 msec
;; SERVER: 3ffe:0:1::c620:242#53(z.ip6.int)
;; WHEN: Mon Jun 16 09:18:05 2003
;; MSG SIZE rcvd: 63
.... so, whats the big problem here? other than they were given
a delegation and never registered their nameserverss?
--bill
Opinions expressed may not even be mine by the time you read them, and
certainly don't reflect those of any other entity (legal or otherwise).