On 15.09.2017 16:05, Gerben Meijer wrote:
> Unfortunately it seems that setting set_search_domains=yes in dnssec.conf is
> not enough.
>
> The code in dnssec-trigger-script does not look at the contents of "search:"
> in /etc/dnssec-trigger/dnssec-trigger.conf even with that set. Instead, it
>
Unfortunately it seems that setting set_search_domains=yes in
dnssec.conf is not enough.
The code in dnssec-trigger-script does not look at the contents of
"search:" in /etc/dnssec-trigger/dnssec-trigger.conf even with that set.
Instead, it seems to query NetworkManager for search domains but
This seems to be caused by a new option, set_search_domains, in
/etc/dnssec.conf. It defaults to 'no', but if you set it to 'yes',
search domains are properly added to /etc/resolv.conf, again.
(Note: Make sure to look at /etc/dnssec.conf, not
/etc/dnssec-trigger/dnssec.conf, which may be present a
Package: dnssec-trigger
Version: 0.13-6
Severity: important
Since a recent upgrade of dnssec-trigger the "search" option to set
custom search domains is ignored. Looking at the dnssec-trigger-script
which writes resolv.conf it does not even look at this option.
While this does not make the packag
4 matches
Mail list logo
