ipv6 and dns name resolution

Question

Level 1

0 points

ipv6 and dns name resolution

I'm having problems trying to configuring IPv6 on mac os x. I have configured my ipv6 tunnel correctly, but I can't make ping6 resolve ipv6 addresses. IPv6 address resolving doesn't work in mozilla either.

G5:~ idave$ dig ngnet.azzurra.org AAAA
[...]
;; ANSWER SECTION:
ngnet.azzurra.org. 60 IN AAAA 2001:6b8::206:5bff:fe39:3a90
[...]
G5:~ idave$ ping6 2001:6b8::206:5bff:fe39:3a90
PING6(56=40 88 bytes) xxxxxxx --> 2001:6b8::206:5bff:fe39:3a90
16 bytes from 2001:6b8::206:5bff:fe39:3a90, icmp_seq=0 hlim=62 time=63.44 ms
16 bytes from 2001:6b8::206:5bff:fe39:3a90, icmp_seq=1 hlim=62 time=70.82 ms
^C
--- ngnet.azzurra.org ping6 statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 63.448/67.134/70.820 ms

G5:~ idave$ ping6 ngnet.azzurra.org
ping6: No address associated with nodename
G5:~ idave$

I can't understand this strange behaviour. Is there anyone that can tell me how to make things work?

PS: Sorry for my poor english.

PowerMac G5 2x2Ghz Mac OS X (10.4.5)

Posted on Mar 4, 2006 6:11 AM

Reply

Answer 1

May 14, 2006 6:47 PM in response to i Dave

What is your network setup and your computers IP address? Are you behind a router? Have you ever played around with the name resolution order?

Reply

Answer 2

i Dave Author

Level 1

0 points

May 15, 2006 6:48 AM in response to i Dave

lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
gif0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1280
tunnel inet 192.168.1.200 --> 163.162.170.177
inet6 fe80::20a:95ff:fea7:3ce4%gif0 prefixlen 64 scopeid 0x2
inet6 2001:6b8:0:600::4c52 --> 2001:6b8:0:600::4c53 prefixlen 128
stf0: flags=0 mtu 1280
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet6 fe80::20a:95ff:fea7:3ce4%en0 prefixlen 64 scopeid 0x4
inet 192.168.1.200 netmask 0xffffff00 broadcast 192.168.1.255
ether 00:0a:95:a7:3c:e4
media: autoselect (100baseTX <full-duplex>) status: active
supported media: none autoselect 10baseT/UTP <half-duplex> 10baseT/UTP <full-duplex> 10baseT/UTP <full-duplex,hw-loopback> 100baseTX <half-duplex> 100baseTX <full-duplex> 100baseTX <full-duplex,hw-loopback> 1000baseT <full-duplex> 1000baseT <full-duplex,hw-loopback> 1000baseT <full-duplex,flow-control> 1000baseT <full-duplex,flow-control,hw-loopback>
fw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 4078
lladdr 00:0a:95:ff:fe:a7:3c:e4
media: autoselect <full-duplex> status: inactive
supported media: autoselect <full-duplex>
gif1: flags=8010<POINTOPOINT,MULTICAST> mtu 1280

gif0 is the interface connected to the tunnel broker...

Reply

Answer 3

May 15, 2006 7:12 PM in response to i Dave

You won't be able to ping6 ngnet.azzurra.org, since it does not have an AAAA record in the DNS entry (AAAA is the field used to list the associated IPv6 address of a host, if one is present). You can check this with 'dig ngnet.azzurra.org'. On the other hand you should be able to ping6 www.kame.net.

Let me know how you fair.

Reply

Answer 4

i Dave Author

Level 1

0 points

May 16, 2006 1:46 PM in response to i Dave

As I said in my first post, ngnet.azzurra.org has got an aaaa address

Here you are the output of the command 'dig ngnet.azzurra.org aaaa'

G5:~ idave$ dig ngnet.azzurra.org aaaa

; <<>> DiG 9.2.2 <<>> ngnet.azzurra.org aaaa
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 36224
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 5, ADDITIONAL: 5

;; QUESTION SECTION:
;ngnet.azzurra.org. IN AAAA

;; ANSWER SECTION:
ngnet.azzurra.org. 60 IN AAAA 2001:6b8::206:5bff:fe39:3a90

;; AUTHORITY SECTION:
azzurra.org. 5706 IN NS auth01.ns.azzurra.org.
azzurra.org. 5706 IN NS auth02.ns.azzurra.org.
azzurra.org. 5706 IN NS auth03.ns.azzurra.org.
azzurra.org. 5706 IN NS auth04.ns.azzurra.org.
azzurra.org. 5706 IN NS auth05.ns.azzurra.org.

;; ADDITIONAL SECTION:
auth01.ns.azzurra.org. 2307 IN A 194.246.127.2
auth02.ns.azzurra.org. 5705 IN A 195.78.223.14
auth03.ns.azzurra.org. 5705 IN A 213.203.143.50
auth04.ns.azzurra.org. 5705 IN A 217.220.29.150
auth05.ns.azzurra.org. 5705 IN A 193.254.240.99

;; Query time: 78 msec
;; SERVER: 213.92.5.54#53(213.92.5.54)
;; WHEN: Tue May 16 22:42:58 2006
;; MSG SIZE rcvd: 251

G5:~ idave$

Please note that if you only type 'dig ngnet.azzurra.org', dig will look for the A record, not for the AAAA record. The same goes for www.kame.net.

G5:~ idave$ dig www.kame.net

; <<>> DiG 9.2.2 <<>> www.kame.net
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 13884
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0

;; QUESTION SECTION:
;www.kame.net. IN A

;; ANSWER SECTION:
www.kame.net. 7200 IN A 203.178.141.194

;; AUTHORITY SECTION:
kame.net. 7200 IN NS ns1.itojun.org.
kame.net. 7200 IN NS orange.kame.net.

;; Query time: 355 msec
;; SERVER: 213.92.5.54#53(213.92.5.54)
;; WHEN: Tue May 16 22:45:27 2006
;; MSG SIZE rcvd: 95

G5:~ idave$ dig www.kame.net aaaa

; <<>> DiG 9.2.2 <<>> www.kame.net aaaa
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 5564
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0

;; QUESTION SECTION:
;www.kame.net. IN AAAA

;; ANSWER SECTION:
www.kame.net. 7200 IN AAAA 2001:200::8002:203:47ff:fea5:3085

;; AUTHORITY SECTION:
kame.net. 7193 IN NS ns1.itojun.org.
kame.net. 7193 IN NS orange.kame.net.

;; Query time: 336 msec
;; SERVER: 213.92.5.54#53(213.92.5.54)
;; WHEN: Tue May 16 22:45:33 2006
;; MSG SIZE rcvd: 107

G5:~ idave$ <br>
PowerMac G5 2x2Ghz Mac OS X (10.4.5)

Reply

Answer 5

May 16, 2006 7:37 PM in response to i Dave

Ok, though I was getting the AAAA entries for some sites even without that option.

Can you ping the IPv6 address directly? I am wondering whether your DNS cache could be out of date. I was experiencing a few issues myself trying to ping the site, and then suddenly it started working.

Let me know if Miredo makes a difference for you:

http://www.simphalempin.com/dev/miredo/

you will also need the tun/tap driver:

http://www-user.rhrk.uni-kl.de/~nissler/tuntap/

PowerBook G4 15" 1.67GHz Mac OS X (10.4.5)

Reply

Answer 6

i Dave Author

Level 1

0 points

May 17, 2006 5:55 AM in response to i Dave

Pinging the IPv6 address works. See my first post for details.

It works without any special app. It's enough to set ipv6 tunneling as follows:set /sbin/ifconfig gif0 create
/sbin/ifconfig gif0 tunnel 192.168.1.200 163.162.170.177
/sbin/ifconfig gif0 inet6 2001:06b8:0000:0600::4c52 2001:06b8:0000:0600::4c53 prefixlen 128
/sbin/route -n add -inet6 default 2001:06b8:0000:0600::4c53
/sbin/ifconfig gif0 up

Where 192.168.1.200 is my ip address behind the nat. Please note that this tunnel already works, but only with the IPv6 address...

Reply