[Dnssec-trigger] current status?

Paul Wouters paul at nohats.ca
Thu Mar 12 14:08:26 UTC 2015

On Thu, 12 Mar 2015, Chuck Anderson wrote:

>> There is a long standing bug that triggers in certain situations with
>> hotspots where somehow dnssec-triggerd rewrites resolv.conf but actually
>> has no (DHCP obtained) DNS server to put in, it then writes a file
>> without any nameserver entry and expects the user to successfully browse
>> through the captive portal. I haven't managed to reproduce it at will
>> though. But I do wish that dnssec-triggerd would first check if it has
>> any DNS server before it overwrites resolv.conf.
> This particular "disappearing /etc/resolv.conf" APPEARS to be
> SELinux-related.  When I "setenforce 0" and restart dnssec-triggerd,
> resolv.conf gets generated properly.  It may be a new SELinux thing
> since I just took a new version of selinux-policy-targeted.

Not for me. I (sadly) do not run with selinux enabled on my laptop.


More information about the dnssec-trigger mailing list