[Dnssec-trigger] [PATCH] dnssec-trigger-script: Don't configure RFC1918 zones if there are no global forwarders
wouter at nlnetlabs.nl
Tue Apr 7 12:57:39 UTC 2015
-----BEGIN PGP SIGNED MESSAGE-----
Applied, that must have been a painful issue for the user.
Best regards, Wouter
On 02/04/15 20:19, Tomas Hozza wrote:
> I'm attaching patch for issue caught by ABRT - Automatic Bug
> Reporting Tool.
> Previously the script tried to install RFC1918 zones even if there
> were no global forwarders from NetworkManager. This lead to
> removing the zones from Unbound which is good, but not from zones
> Store. Also on subsequent calls the script tried to remove the
> zones from Unbound again and crashed with traceback.
> When a machine had configuration of RFC1918 zones enabled by
> default, the script crashed also during boot, if the machine was
> not connected to any network.
> Please also see
> This change makes the script to add RFC1918 zones only if there are
> global forwarders, otherwise it will remove them from Unbound and
> zones Store. If zones are not configured in Unbound or are not
> present in the zones Store, it will do nothing.
> _______________________________________________ dnssec-trigger
> mailing list dnssec-trigger at NLnetLabs.nl
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
-----END PGP SIGNATURE-----
More information about the dnssec-trigger