[Dnssec-trigger] [PATCH] dnssec-trigger-script: Don't configure RFC1918 zones if there are no global forwarders
thozza at redhat.com
Tue Apr 7 15:16:40 UTC 2015
-----BEGIN PGP SIGNED MESSAGE-----
It sure was. I experienced the same issue and in my case it delayed
the boot for 2,5 minutes.
I also found out that the configuration of reverse address zones does
not work, since Unbound configures them as static local zones. I'm working on
the fix and will send it soon.
On 04/07/2015 02:57 PM, W.C.A. Wijngaards wrote:
> Hi Tomas,
> 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
> dnssec-trigger mailing list
> dnssec-trigger at NLnetLabs.nl
Software Engineer - EMEA ENG Developer Experience
Red Hat Inc. http://cz.redhat.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
-----END PGP SIGNATURE-----
More information about the dnssec-trigger