Sources urls should respect `ipv6_servers = false` option.

[vbauerster]

Would it be possible for the sources section to respect ipv6_servers = false option? I mean not to use ipv6 urls if ipv6_servers = false.

dnscrypt-proxy/dnscrypt-proxy/example-dnscrypt-proxy.toml

Lines 670 to 688 in c467e20

	[sources]
	### An example of a remote source from https://github.com/DNSCrypt/dnscrypt-resolvers
	[sources.public-resolvers]
	urls = ['https://raw.githubusercontent.com/DNSCrypt/dnscrypt-resolvers/master/v3/public-resolvers.md', 'https://download.dnscrypt.info/resolvers-list/v3/public-resolvers.md', 'https://ipv6.download.dnscrypt.info/resolvers-list/v3/public-resolvers.md']
	cache_file = 'public-resolvers.md'
	minisign_key = 'RWQf6LRCGA9i53mlYecO4IzT51TGPpvWucNSCh1CBM0QTaLn73Y7GFO3'
	refresh_delay = 72
	prefix = ''
	### Anonymized DNS relays
	[sources.relays]
	urls = ['https://raw.githubusercontent.com/DNSCrypt/dnscrypt-resolvers/master/v3/relays.md', 'https://download.dnscrypt.info/resolvers-list/v3/relays.md', 'https://ipv6.download.dnscrypt.info/resolvers-list/v3/relays.md']
	cache_file = 'relays.md'
	minisign_key = 'RWQf6LRCGA9i53mlYecO4IzT51TGPpvWucNSCh1CBM0QTaLn73Y7GFO3'
	refresh_delay = 72
	prefix = ''

dnscrypt-proxy/dnscrypt-proxy/example-dnscrypt-proxy.toml

Line 64 in c467e20

ipv6_servers = false

[vbauerster]

I actually had a service crash most likely because of this (dnscrypt-proxy is self compiled from HEAD):

[jedisct1]

If a source URL is unreachable, no matter why, the proxy is expected to try another URL in the list.

What exact error do you get when starting the proxy from the command line?

[vbauerster]

The problem was that service sometimes crashed. Now I figured out why. It's running on raspberry pi, where there is no hw clock. So if it is started before actual time is set, it always crashed with error saying something like cert expired or invalid at source url download step. I've fixed that by making sure dnscrypt-proxy is starting after actual time is set.

So if bad url is skipped, this issue is likely not so important anyway, feel free to close.

[jedisct1]

Unless the cache is stored in a location such as /tmp that doesn't persist after a reboot, the old cache should be used if up-to-date information cannot be fetched.

If nothing is accessible, it doesn't crash. The service stops, because it doesn't have any valid servers list.

In servers list, https:// can be replaced with http:// so that there's no TLS, no need for a correctly set clock. But the best thing to do is exactly what you did; make sure the time is set. Certificates, whether they are DNSCrypt or DoH, have a limited life time, so even if the configuration is usable, DNS servers won't be usable if the clock is off.

Waiting for the system clock not be in 1970's is something we could add to the netprobe step. though.