Cache Load Balance estimation across restart?

[Klaaktu]

One of the inconvenience to dnscrypt-proxy is that whenever the service is restarted, or the machine is rebooted, dnscrypt-proxy makes a flood of connections on start (that can potentially trip firewalls) and takes some time get ready.

How about preserving the internal sorted list across sessions?

[jedisct1]

It's pretty quick. A single working resolver is enough to start answering DNS responses.

Also a computer can be restarted with a completely different network, so redoing the checks is not a bad thing.

[Klaaktu]

I guess it's a bit of an exception, but...
In China (at least where my home server is), save for the dozen closest servers, the rest are slow and lossy. They appear to be usable initially, but once you start using them for a bit, they / I am quickly blocked. It also feels like there is a client block on the ISP side, where I'm blocked / heavily interfered from connecting to outside if I do it too much. So I guess that's why it feels kinda slow to start.
(I don't look at my server frequently and I'm currently not in China, so the above has some conjecture.)

Is there another way to avoid the startup scan / delay? (Use server_names instead of the resolver list?)