parameter 'startVerifyUpstream = false' checks upstream on start

[0xERR0R]

When following configuration is used:

upstream:
  default:
    - some.wrong.host
startVerifyUpstream: false

Then blocky fails to start with following message: upstream group default: lookup some.wrong.host on 127.0.0.11:53: no such host

I would expect, the configuration "startVerifyUpstream: false" will disable all startup checks. This is useful if server gets restarted and DNS resolution is not ready if blocky is started.

[kwitsch]

Do I get it correct that you like to change the default behavior and setting it to true will switch it back to the current default?

[0xERR0R]

My expectation is:

if startVerifyUpstream = false, which is default, blocky should start even if network is down. No upstream server should be verified. List download will fail. But blocky starts and can answer DNS queries (e.g. custom mapping). All queries to upstream servers will of course fail. If network connection is established again, blocky will operate without issues. Lists will be downloaded on next refresh attempt.

if startVerifyUpstream = true, blocky start should fail.

Current behaviour is, that blocky start fails even if startVerifyUpstream = false

[ThinkChaos]

Assigned to myself and will submit a MR.