nanog mailing list archives
Re: Public DNS64
From: Tore Anderson <tore () fud no>
Date: Wed, 1 Jun 2016 10:37:07 +0200
* 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. Tore
Current thread:
- Re: Public DNS64 Tore Anderson (Jun 01)
- Re: Public DNS64 Mark Andrews (Jun 01)
- Re: Public DNS64 Tore Anderson (Jun 01)
- <Possible follow-ups>
- Re: Public DNS64 Ca By (Jun 01)
- Re: Public DNS64 Mark Andrews (Jun 01)