Public DNS64

Mark Andrews marka at
Mon May 30 21:40:44 UTC 2016

In message <alpine.DEB.2.02.1605301725200.28372 at>, Mikael Abrah
amsson writes:
> On Mon, 30 May 2016, Hugo Slabbert wrote:
> > specifically regarding the idea of a public, anycast NAT64 service, 
> > rather than the public DNS64 service Google is doing.
> Like HE is doing?
> swmike at uplift:~$ dig +short AAAA
> 2001:470:64:ffff::d4f7:c88f
> swmike at uplift:~$ ping6 2001:470:64:ffff::d4f7:c88f
> PING 2001:470:64:ffff::d4f7:c88f(2001:470:64:ffff::d4f7:c88f) 56 data 
> bytes
> 64 bytes from 2001:470:64:ffff::d4f7:c88f: icmp_seq=1 ttl=42 time=316 ms
> 64 bytes from 2001:470:64:ffff::d4f7:c88f: icmp_seq=2 ttl=42 time=315 ms
> Now, pinging myself via DNS64/NAT64 service and getting 315ms RTT means 
> the NAT64 isn't very local to me... :P

I don't know if that is a anycast NAT64.  Just because pings get
through doesn't mean that other traffic will get through.  It really
depends upon whether all the IPv6 traffic in the stream all gets
routed to the same NAT64 instance.  For short lived session this
is highly likely.  For long lived sessions not so much.

For ping there is a single packet each direction.  For other protocols
there isn't.


> -- 
> Mikael Abrahamsson    email: swmike at
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka at

More information about the NANOG mailing list