Do not handle Unbound/dnsmasq/PowerDNS by default

MichaIngrequested to merge
(removed):skip-extra-resolver-conf into debian/main

Unbound, dnsmasq and PowerDNS are commonly installed as network services for the LAN, not for their host itself.

Syncing their upstream DNS nameservers with the one(s) used by the host usually breaks their purpose and generally (silently) overriding the admin configured config files for those applications is unexpected and can cause confusion.

With Unbound there are additional issues:

  • It is a validating, recursive DNS resolver which by default queries DNS root servers directly, hence does not use a regular upstream provider. This is the main reason why Unbound is installed.
  • It supports DoT and DoH which is another, though less common use case.
  • Overriding the config to use a regular upstream DNS provider, even without encryption, breaks those two reasons why admins install Unbound.
  • In combination with IPv6, network info can regularly change. The Unbound sync implementation of openresolv updates the Unbound config and restarts the Unbound service on every such change. This can be a significant disturbance of the DNS resolver task for the whole LAN, with regular failing client DNS queries and spammed server logs.

The issue became more apparent after a recent "fix" in Debian's openresolv configuration, which corrected the Unbound config path before which Unbound auto-configuration failed (and hence the mentioned issues did not appear).

The resolvconf.conf addition is hereby removed to align the Debian package's default config with upstream.

For reference: https://github.com/NetworkConfiguration/openresolv/issues/15

Signed-off-by: MichaIng micha@dietpi.com

Edited by MichaIng

Merge request reports