I aim to keep this NAT64+DNS64 service as useful as possible. By my own measurements I am doing a good job at that. However I also understand that not everyone have the same needs so possibly some users will find other providers more suitable.
The primary goal of this service is to make IPv6 as useful as possible. I believe I do that best by letting users make their own informed choice between available providers. Here is the list of all public NAT64 and DNS64 providers known to me.
Provider | DNS64 | NAT64 | Redundancy | DNS64 addresses | NAT64 prefixes |
---|---|---|---|---|---|
nat64.net | ✔ | ✔ | ✔ | 5 | 4 |
Trex | ✔ | ✔ | ❌ | 2 | 1 |
level66 | ✔ | ✔ | ❌ | 2 | 1 |
IPng | ✔ | ✔ | ❌ | 1 | 1 |
✔ | ❌ | ❌ | 2 | 0 | |
Cloudflare | ✔ | ❌ | ❌ | 2 | 0 |
In this table redundancy means the provider has redundant DNS64 instances providing addresses in redundant NAT64 infrastructure. Both DNS64 and NAT64 must have multi-site redundancy to qualify.
The providers with DNS64 and no NAT64 use the well-known prefix such that you can use the public DNS64 with your own NAT64. This will not work if your NAT64 is using a different prefix or if you do not have a NAT64.
Currently I know of no provider with only NAT64 and no DNS64. However that does not prevent you from using your own DNS64 together with any of the public NAT64 providers. Using your own DNS64 it is even possible to have failover between multiple NAT64 providers - even mixing public and private NAT64s.
Provider | Location | DNS64 address | NAT64 prefixes |
---|---|---|---|
nat64.net | Amsterdam | 2a00:1098:2c::1 | 3 |
nat64.net | Ashburn | 2a01:4ff:f0:9876::1 | 3 |
nat64.net | Helsinki | 2a01:4f9:c010:3f02::1 | 3 |
nat64.net | London | 2a00:1098:2c::1 | 3 |
nat64.net | Nuremberg | 2a01:4f8:c2c:123f::1 | 3 |
IPng | Amsterdam | 2a02:898:146:64::64 | 1 |
Trex | Tampere | 2001:67c:2b0::4 | 1 |
Trex | Tampere | 2001:67c:2b0::6 | 1 |
level66 | Germany | 2001:67c:2960::64 | 1 |
level66 | Germany | 2001:67c:2960::6464 | 1 |
Cloudflare | Global anycast | 2606:4700:4700::6400 | 0 |
Cloudflare | Global anycast | 2606:4700:4700::64 | 0 |
Global anycast | 2001:4860:4860::64 | 0 | |
Global anycast | 2001:4860:4860::6464 | 0 |
In this table location denotes the location of the DNS64 server. The NAT64 prefixes column indicates how many public NAT64 prefixes are used in DNS64 responses. The NAT64 gateways may be in a different location than the DNS64 server. DNS64 servers which use 64:ff9b::/96 require you to bring your own NAT64 gateway and are listed as 0 in the table.
If you find any outdated information on this page you are welcome to contact me with updated information. I will only include information which I am able to verify myself by communicating with the respective DNS64 and NAT64 instances.