Description of problem: After upgrading to Fedora 26 I get on my pc (DHCP client) wrong domain list defined in "search" option on my DHCP server. /etc/resolv.conf on pc with hostname "pc1.home": # Generated by NetworkManager search pc1.home nameserver 192.168.0.1 /etc/dhcp/dhcpd.conf on my DHCP server: option domain-name "home"; Version-Release number of selected component (if applicable): NetworkManager.x86_64 1:1.8.0-6.fc26 How reproducible: Use DHCP server with defined "search" option. Actual results: /etc/resolv.conf: search pc1.home Expected results: /etc/resolv.conf: search home
*** This bug has been marked as a duplicate of bug 1404350 ***
Unduplicating, the other bug is for F25.
NetworkManager-1.8.2-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-8949032ca5
NetworkManager-1.8.2-1.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-8949032ca5
*** Bug 1455557 has been marked as a duplicate of this bug. ***
*** Bug 1469786 has been marked as a duplicate of this bug. ***
After the update, the search parameter now does contain search <domain> <hostname>.<domain> Although that effectively solves the problem, I am not sure, why <hostname>.<domain> is still in. What is its purpose?
NetworkManager-1.8.2-1.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.
(In reply to Werner Gold from comment #7) > After the update, the search parameter now does contain > search <domain> <hostname>.<domain> > Although that effectively solves the problem, I am not sure, why > <hostname>.<domain> is still in. What is its purpose? Hi, the purpose is explained here: https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/src/dns/nm-dns-manager.c?h=nm-1-8&id=1.8.2#n1045
*** Bug 1473423 has been marked as a duplicate of this bug. ***