Public DNS64

Mark Tinka mark.tinka at seacom.mu
Tue May 31 05:44:36 UTC 2016


On 31/May/16 01:28, Baldur Norddahl wrote:

>>
>>
>> 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. A more simple
>> solution is just to have the DNS64 be anycast and have a DNS64 at each
>> NAT64 location with the DNS64 returning pointers to the local NAT64.

That is what we do.

We've got NAT64 routers deployed at every PoP/region, to keep NAT64
state local and more predictable.

Needless to say, the distribution reduces the impact of the "CG" from
the "CG-NAT64".

Mark.


More information about the NANOG mailing list