Public DNS64

Wed Jun 1 11:49:30 UTC 2016

In message <20160601103707.7de9d97f at envy.e5.y.home>, Tore Anderson writes:
> * Baldur Norddahl
> 
> > It goes to the USA and back again. They would need NAT64 servers in
> > every region and then let the DNS64 service decide which one is close
> > to you by encoding the region information in the returned IPv6
> > address. Such as 2001:470:64:[region number]::/96.
> > 
> > An anycast solution would need a distributed NAT64 implementation,
> > such that the NAT64 servers could somehow synchronize state.
> 
> Or you could simply accept that active sessions are torn down whenever
> the routing topology changes enough to flip traffic to the anycast
> prefix to another NAT64 instance in a different region.
> 
> It would be no different from any other anycasted service.

But some services are inherently short lived.  NAT64 has no such
property.

> Tore
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka at isc.org