IPv6 Ping does not work with domain names

I tried to Ping ipv6.google.com from the Ping tool without success.

I got the error “Error in Ping To - ip address expected” from winbox, or from the command line :

ping address=ipv6.google.com
while resolving ip-address: could not get answer from dns server

Same try from a Linux machine on the same network as this router is working without problem. So i’m sure there is no problem with our DNS servers :

ping6 ipv6.google.com

PING ipv6.google.com(2a00:1450:8002::63) 56 data bytes
64 bytes from 2a00:1450:8002::63: icmp_seq=0 ttl=53 time=48.8 ms
64 bytes from 2a00:1450:8002::63: icmp_seq=1 ttl=53 time=45.8 ms
64 bytes from 2a00:1450:8002::63: icmp_seq=2 ttl=53 time=46.0 ms
64 bytes from 2a00:1450:8002::63: icmp_seq=3 ttl=53 time=44.4 ms


If i ping directly the IP address 2a00:1450:8002::63 it’s working :

ping address=2a00:1450:8002::63
HOST SIZE TTL TIME STATUS
2a00:1450:8002::63 56 55 58ms echo reply
2a00:1450:8002::63 56 55 57ms echo reply
2a00:1450:8002::63 56 55 57ms echo reply
2a00:1450:8002::63 56 55 57ms echo reply
2a00:1450:8002::63 56 55 56ms echo reply

Seems like there is a problem with IPv6 AAAA pointers resolution.

There is no problem with IPv4 pointers : pinging google.com does work from the ping tool.

ping google.com
HOST SIZE TTL TIME STATUS
74.125.230.81 56 58 46ms
74.125.230.81 56 58 46ms
74.125.230.81 56 58 45ms
74.125.230.81 56 58 44ms

I tried to enter our IPv6 DNS server addresses in the DNS setup, to see if direct resolution on a IPv6 enabled DNS server was working, but this does not help.


Mikrotik can you correct this for 5.0 rc6 because it is a fondamental tool for IPv6 tests. Don’t forget that the end of IPv4 pool is 03 march 2011. Only four monthes. We have now less than one year to fully test and deploy IPv6.

Direct resolution on IPv6 enabled DNS servers is important too because futur clients near 2012 and later will not have access to IPv4 DNS servers. (they will get IPv6 only addresses so they will not be able to contact IPv4 DNS server to get AAAA records).

it used to work, will look into the problem.

Hello, It seems the problem is still there.
I upgraded to ROS 5.1 and set DNS (ip->DNS) and added HE.net anycast ipv6 dns server but from mikrotik itself it doesn’t resolve any domain into ipv6 address. (ipv6.google.com).
But any machine in the networks resolves very good.

What’s the problem?

Cheers.-

Same problem here with 5.1.

I can’t understand how Mikrotik can get positiv results here.


Mikrotik, did you try through a PPPoE IPv6 connection, or Ethernet IPv6 ?


I’m trying through PPPoE.

Perhaps that binding to PPPoE interfaces does not work from the router ? Missing glue code ??

Resolving ipv6.google.com from other machines on the Network works without problems.

I recall it never working on any version of RouterOS.

At the moment:

Broken on v4.17:

[admin@Ranume] > ping ipv6.google.com
invalid value for argument address
[admin@Ranume] >

Broken on v4.16:

[admin@Skhal] > ping ipv6.google.com
invalid value for argument address
[admin@Skhal] >

Broken on v5.0:

[admin@Jeekim] > ping ipv6.google.com
dns name exists, but no appropriate record
invalid value for argument ipv6-address
[admin@Jeekim] >

Working on Fedora 14 behind these MT boxes and using the same DNS servers:

[ivo@haskaa ~]$ ping6 ipv6.google.com
PING ipv6.google.com(2a00:1450:8003::68) 56 data bytes
64 bytes from 2a00:1450:8003::68: icmp_seq=1 ttl=52 time=55.3 ms
64 bytes from 2a00:1450:8003::68: icmp_seq=2 ttl=52 time=53.4 ms
^C
--- ipv6.google.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1000ms
rtt min/avg/max/mdev = 53.486/54.393/55.301/0.936 ms
[ivo@haskaa ~]$

Testing on 5.4 but not functional yet regular.

[admin@mikrotik] > :put [:resolve ipv6.google.com]
failure: dns name exists, but no appropriate record

on linux behind this MT resolv works good.

v5.11 and still the same situation. Why is is so difficult to get fixed/supported?

not sure how to react:

RouterOS 5.11 (c) 1999-2011


[admin@hs] > /ping [:resolve ipv6.google.com]
HOST                                     SIZE TTL TIME  STATUS                                                                      
2a00:1450:8005::6a                         56  49 73ms  echo reply                                                                  
2a00:1450:8005::6a                         56  49 59ms  echo reply                                                                  
    sent=2 received=2 packet-loss=0% min-rtt=59ms avg-rtt=66ms max-rtt=73ms 

[admin@hs] > :put [:resolve ipv6.google.com] 
2a00:1450:8005::6a

and i have actually IPv6 working with global ipv6 addressing working.

Working for me.

But i did not see this syntax in the Wiki :

http://wiki.mikrotik.com/wiki/Manual:Troubleshooting_tools


Woud be simpler to have a ping6 tool or a parameter for ping.

I concur. The behavior isn’t consistent with the ipv4 ping syntax where the name resolution automatically happens, but thanks for the post! Google lead me right to the answer here. [:resolve …] doesn’t seem real intuitive and it’s not in the mikrotik command help. Verified it works on 5.9 with the [:resolve …] syntax.

Devs want to address this in general manner not hacking each place with domain separately. So the change is coming.

It’s been almost ten months now, is this change any closer?

It’s been over eleven months now, is this change any closer?

yes, it is on the feature list and will be removed only when implemented.

ROS 6.0rc5:

[admin@MikroTik] > ping ipv6.google.com
dns name exists, but no appropriate record
invalid value for argument ipv6-address
[admin@MikroTik] > ping 2a00:1450:4017:800::1012
HOST SIZE TTL TIME STATUS
2a00:1450:4017:800::1012 56 57 64ms echo reply
2a00:1450:4017:800::1012 56 57 64ms echo reply
2a00:1450:4017:800::1012 56 57 64ms echo reply
2a00:1450:4017:800::1012 56 57 66ms echo reply
sent=4 received=4 packet-loss=0% min-rtt=64ms avg-rtt=64ms max-rtt=66ms

that is problem with ping and requires a lot of changes to make it work. So in the mean time do this instead
/ping [:resolve ipv6.google.com]since workaround is pretty trivial

Then where definitely should be at least something like resolve6! :confused: Damn, two years is almost done since the promised feature.

Not a resolve6, but the ping6.

Traceroute with IPv6 and use-dns=yes does not resolve PTR of the hops, too.

Not confirmed. ROS 6.25. Traceroute with IPv6 and use-dns = yes resolve PTR.
2015-01-27 20-52-23 Скриншот экрана.png