tracepath6 -n is supposed to return numeric values only. Hence it should resolve FQDN to their numeric ipv6 address. Apparently it fails to do so.
tracepath6 -n 2001:xxxx::xxxx works normally though, so it's just a matter of solving that getaddrinfo I guess.
Confirmed on 3 different hosts and archs.
Steps to Reproduce:
getaddrinfo: Resolver Error 0 (no error)
Resolve address then tracepath6 -n
In all cases, resolv.conf contained at least one valid nameserver entry, and that nameserver was able to resolve the FQDN to its AAAA record.
this still a problem with iputils-20100418 ?
(In reply to comment #1)
> this still a problem with iputils-20100418 ?
It seems to be fixed, thanks :-)