Hi all,
can someone kindly check this:dig -n 3ffe:whatever ???
if I use dig -x that use ip6.arpa is ok but the most strange thing is that dig -n should simply switch to ip6.int In my case my local dns is able to solve both of them but after upgrading to *-9.2.0 now I get this:
diapolon:~# dig -n 3ffe:100:e:1::1
; <<>> DiG 9.2.0 <<>> -n 3ffe:100:e:1::1 ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 56915 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION: ;3ffe:100:e:1::1. IN A
;; AUTHORITY SECTION:
. 10164 IN SOA A.ROOT-SERVERS.NET. nstld.verisign-grs.com. 2001120900 1800 900 604800 86400
;; Query time: 17 msec ;; SERVER: 192.168.2.6#53(192.168.2.6) ;; WHEN: Sun Dec 9 18:54:47 2001 ;; MSG SIZE rcvd: 108
and with tcpdump I can see the packets directed to the rootserver and coming back.
Any clue?? please is quite urgent for me.
Thanks a lot! Fabio
PS btw the reverse from some ipv6 looking glass is working perfectly (www.6bone.net). I guess they are still running "old" stuff.
-- Debian GNU/Linux Unstable Kernel 2.4.15aa1 fabbione on irc.atdot.it #coredump #kchat | [EMAIL PROTECTED]
