Description of problem: Recently I realized that using dnssec-trigger causes resolv.conf not to contain search domains. This makes users using one-label names from search domain not to resolve. Version-Release number of selected component (if applicable): latest How reproducible: always Steps to Reproduce: 1. turn on dnssec-trigger + unbound 2. connect to a network providing you a search domain 3. try to resolve some host without using the search domain ending Actual results: The host name is not resolved. The search domain is not appended and tried out. Expected results: The search domain should be tried out. Additional info:
dnssec-trigger should honour "domain" and "search" entries. But so should NM. This relates to the long discussion we had on always forwarding everything to the dhcp supplied DNS server. There is disagreement on this. My position is that nothing should ever change my domain/search entries. Others believe the dhcp/vpn domain should always be put there.
We have been working on dnssec-trigger-script but resolv.conf is written out by dnssec-trigger which isn't aware of NetworkManager configuration at all. This logic probably belongs to just one place so when we're using dnssec-trigger-script to configure unbound, it should also be used to write out /etc/resolv.conf which I'm already doing for bug #1125267. The only problem I see is hotspot sign on where dnssec-trigger rewrites /etc/resolv.conf on purpose.
(In reply to Paul Wouters from comment #1) > My position is that nothing should ever change my domain/search entries. > Others believe the dhcp/vpn domain should always be put there. In my opinion, this should be configurable on the side of the tool that originates then change which is NetworkManager on a typical Fedora installation.
*** Bug 1132233 has been marked as a duplicate of this bug. ***
Created attachment 982666 [details] patch
Created attachment 983076 [details] patch
The patch implements the search list with a global configuration knob. In future a more fine grained configuration should be part of NetworkManager.
Implemented but not set by default. I know there were some discussions, any comments on setting it by default are welcome.
dnssec-trigger-0.12-19.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/FEDORA-2015-3864/dnssec-trigger-0.12-19.fc22
dnssec-trigger-0.12-19.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/FEDORA-2015-3843/dnssec-trigger-0.12-19.fc21
dnssec-trigger-0.12-19.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
dnssec-trigger-0.12-20.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.