Red Hat Bugzilla – Bug 1286930
No 'resolv.conf' while using default DNSSEC resolver
Last modified: 2017-08-08 08:28:58 EDT
In one of the lists Matthew mentioned about this issue he faced while using the proposed default DNSSEC resolver(unbound + dnssec-trigger) solution[*].
+-- On Mon, 30 Nov 2015, Matthew Miller wrote --+
| If it helps, I'm pretty sure it can be replicated very easily if you're
| traveling through the Detroit airport. :) There weren't any error messages
| -- there just wasn't any DNS. In some situations, I've ended up without an
| /etc/resolv.conf at all, and in others, it's been there pointing to the
| local resolver but that's mysteriously not returning results.
I experienced the same issue before. From what I can tell, it is happening from the times dnssec-trigger script was modified to use symlinks and other things around resolv.conf management. Also SELinux was previously forbidding dnssec-trigger script to write in /etc. However is should work now.
Anyway the best thing to do is to add 'debug=yes' to /etc/dnssec.conf and set the verbosity to '5' or so in /etc/dnssec-trigger/dnssec-trigger.conf and then attach the logs from journal when it happens.
I actually regularly hit this too. I'll enable the debug and see if i can reproduce it. It seems related to trying to switch the applet to manually reprobe.
Thanks Tomas. I'll set the debug config, and give more information when I have it.
Is this issue the reason why I am getting
avahi-daemon: Successfully called chroot().
avahi-daemon: Successfully dropped remaining capabilities.
avahi-daemon: chroot.c: open() failed: No such file or directory
avahi-daemon: Failed to open /etc/resolv.conf: Invalid argument
avahi-daemon: No service file found in /etc/avahi/services.
avahi-daemon: Network interface enumeration completed.
on every boot with a machine that has both avahi and dnssec-trigger installed and active?
(In reply to Christian Stadelmann from comment #4)
> Is this issue the reason why I am getting
> avahi-daemon: Successfully called chroot().
> avahi-daemon: Successfully dropped remaining capabilities.
> avahi-daemon: chroot.c: open() failed: No such file or directory
> avahi-daemon: Failed to open /etc/resolv.conf: Invalid argument
> avahi-daemon: No service file found in /etc/avahi/services.
> avahi-daemon: Network interface enumeration completed.
> on every boot with a machine that has both avahi and dnssec-trigger
> installed and active?
Please attach the information described in comment #1. Thank you in advance.
Hm, the line "Failed to open /etc/resolv.conf: Invalid argument" is now gone. There was a SELinux issue related to that I think.
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle.
Changing version to '24'.
More information and reason for this action is here:
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Cannot reproduce this on Fedora 26 any more.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.