Repository navigation
|
Hi folks, I installed DNSCrypt (v2.1.15 in ports) on a FreeBSD box and I applied the Anonymized DNS configuration. IPv4 and IPv6 are working on this box. I enabled IPv6 in config file: I also set the following values for Anonymized DNS: I set load-balancing values too: I get a strange result because with these values, I don't get any IPv6 DNS resolver. List written in dnscrypt-proxy.log file only show IPv4 DNS resolvers (~160 servers). But with the following I get a list with IPv4 and IPv6 DNS resolvers in dnscrypt-proxy.log (~320 servers): Even with only one relay, I get a list with IPv4 and IPv6 DNS resolvers in dnscrypt-proxy.log (~320 servers): or The “Sources” and “Relays” lists are the default ones: I haven't made any changes to them. Is there any mistake in my setup or am I misunderstanding something? Kind regards. |
Replies: 5 comments 4 replies
|
Your setup is fine. What you see is how relay selection works for wildcard routes, and it explains both results (
So if you want IPv6 resolvers and the "farthest relay" logic, add IPv6 relays to the wildcard route. Near you, for example [anonymized_dns]
routes = [
{ server_name='*', via=['anon-kama', 'anon-cs-fr', 'dnscry.pt-anon-paris-ipv6', 'anon-cs-de6'] }
]IPv4 servers then use one of the IPv4 relays and IPv6 servers one of the IPv6 relays. Keep at least two of each family, so the farthest-relay choice still has options. Also make sure the relay list source ( |
|
Both With a wildcard route and multiple relays, automatic selection requires the relay and resolver to use the same address family. So, IPv6 resolvers have no relays they can be reached through. With just one relay, that selection step is bypassed. An IPv4 relay can forward to an IPv6 resolver, if the relay itself has IPv6 |
|
Thank you for your prompt responses and for your valuable information! I tried the suggested solution, even with foreign IPv4 relays and near IPv6 relays, I only get IPv4 resolvers: With a single IPv4 relay (anon-kama), I get the list of resolvers for both IP version families. I think it still better for reliability to set two IPv4 relays with wildcard server_name: |
|
I finally set these into my config file: This way I get ~340 servers on both IP families (IPv4 & IPv6), and if one DNS server or Relay become offline, I will still continue to get DNS name resolution. Should I have to set static as below, or is it unecessary? |
|
[anonymized_dns] In the mean time, I tried others settings. I successfully get IPv4 and IPv6 resolvers using two relays. I also set this one to dissociate the usage of this resolver because I am using the relay operated by the same organization. |
Sorry, my suggestion to mix IPv4 and IPv6 relays couldn't work on any released version, and your test was right. In
findFarthestRoute(), the server address was parsed with its IPv6 brackets still on ([2001:…]).net.ParseIPreturns nil for that, so IPv6 servers got no relay whatever relays you listed. @jedisct1 has since fixed it in 14673ae ("Fix IPv6 relay selection for wildcard routes"). The fix came after 2.1.20, so your mixed list should work once it's in a release.One thing about your latest config: it doesn't use two relays.
Routes are stored in a map keyed by
server_name