Description of problem: After upgrading to F26, NetworkManager does not add the domain 'lan' provided by DHCPv4 to the list of search domains. Version-Release number of selected component (if applicable): NetworkManager-1.8.0-3.fc26.x86_64 $ cat /etc/resolv.conf # Generated by NetworkManager search miceliux.com nameserver 192.168.1.254 # journalctl -b -u NetworkManager 25 09:12:49 xenon systemd[1]: Starting Network Manager... may 25 09:12:49 xenon NetworkManager[976]: <info> [1495696369.9047] NetworkManager (version 1.8.0-3.fc26) is starting... (for the first time) may 25 09:12:49 xenon NetworkManager[976]: <info> [1495696369.9051] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 20-connectivity-fedora.conf) may 25 09:12:49 xenon NetworkManager[976]: <info> [1495696369.9103] manager[0x562a402460c0]: monitoring kernel firmware directory '/lib/firmware'. may 25 09:12:49 xenon NetworkManager[976]: <info> [1495696369.9112] policy: hostname management mode: default may 25 09:12:49 xenon NetworkManager[976]: <info> [1495696369.9114] dns-mgr[0x562a4024d970]: init: dns=default, rc-manager=symlink may 25 09:12:49 xenon NetworkManager[976]: <info> [1495696369.9120] manager[0x562a402460c0]: WiFi hardware radio set enabled may 25 09:12:49 xenon NetworkManager[976]: <info> [1495696369.9120] manager[0x562a402460c0]: WWAN hardware radio set enabled may 25 09:12:49 xenon systemd[1]: Started Network Manager. may 25 09:12:49 xenon NetworkManager[976]: <info> [1495696369.9487] settings: loaded plugin ifcfg-rh: (c) 2007 - 2015 Red Hat, Inc. To report bugs please use the NetworkManager mailing list. (/usr/lib64/NetworkManager/libnm-settings-plugin-ifcfg-rh.so) may 25 09:12:49 xenon NetworkManager[976]: <info> [1495696369.9505] settings: loaded plugin iBFT: (c) 2014 Red Hat, Inc. To report bugs please use the NetworkManager mailing list. (/usr/lib64/NetworkManager/libnm-settings-plugin-ibft.so) may 25 09:12:49 xenon NetworkManager[976]: <info> [1495696369.9506] settings: loaded plugin keyfile: (c) 2007 - 2016 Red Hat, Inc. To report bugs please use the NetworkManager mailing list. may 25 09:12:49 xenon NetworkManager[976]: <info> [1495696369.9523] ifcfg-rh: new connection /etc/sysconfig/network-scripts/ifcfg-br-lan (d037f754-d567-49ee-9e62-33da2324b8ce,"br-lan") may 25 09:12:49 xenon NetworkManager[976]: <info> [1495696369.9528] ifcfg-rh: new connection /etc/sysconfig/network-scripts/ifcfg-enp5s0 (3f9bb58c-06d5-434d-87eb-4209311196cf,"enp5s0") may 25 09:12:49 xenon NetworkManager[976]: <info> [1495696369.9695] keyfile: new connection /etc/NetworkManager/system-connections/VPN DGA (dbc1a5fb-7a74-4743-87ab-4841e18655fe,"VPN DGA") may 25 09:12:49 xenon NetworkManager[976]: <info> [1495696369.9714] settings: hostname: using hostnamed may 25 09:12:49 xenon NetworkManager[976]: <info> [1495696369.9714] settings: hostname changed from (none) to "xenon" may 25 09:12:49 xenon NetworkManager[976]: <info> [1495696369.9725] dhcp-init: Using DHCP client 'dhclient' may 25 09:12:49 xenon NetworkManager[976]: <info> [1495696369.9726] manager: WiFi enabled by radio killswitch; enabled by state file may 25 09:12:49 xenon NetworkManager[976]: <info> [1495696369.9726] manager: WWAN enabled by radio killswitch; enabled by state file may 25 09:12:49 xenon NetworkManager[976]: <info> [1495696369.9726] manager: Networking is enabled by state file may 25 09:12:49 xenon NetworkManager[976]: <info> [1495696369.9735] Loaded device plugin: NMBondDeviceFactory (internal) may 25 09:12:49 xenon NetworkManager[976]: <info> [1495696369.9735] Loaded device plugin: NMBridgeDeviceFactory (internal) may 25 09:12:49 xenon NetworkManager[976]: <info> [1495696369.9735] Loaded device plugin: NMDummyDeviceFactory (internal) may 25 09:12:49 xenon NetworkManager[976]: <info> [1495696369.9735] Loaded device plugin: NMEthernetDeviceFactory (internal) may 25 09:12:49 xenon NetworkManager[976]: <info> [1495696369.9735] Loaded device plugin: NMInfinibandDeviceFactory (internal) may 25 09:12:49 xenon NetworkManager[976]: <info> [1495696369.9736] Loaded device plugin: NMIPTunnelDeviceFactory (internal) may 25 09:12:49 xenon NetworkManager[976]: <info> [1495696369.9736] Loaded device plugin: NMMacsecDeviceFactory (internal) may 25 09:12:49 xenon NetworkManager[976]: <info> [1495696369.9736] Loaded device plugin: NMMacvlanDeviceFactory (internal) may 25 09:12:49 xenon NetworkManager[976]: <info> [1495696369.9741] Loaded device plugin: NMTunDeviceFactory (internal) may 25 09:12:49 xenon NetworkManager[976]: <info> [1495696369.9741] Loaded device plugin: NMVethDeviceFactory (internal) may 25 09:12:49 xenon NetworkManager[976]: <info> [1495696369.9741] Loaded device plugin: NMVlanDeviceFactory (internal) may 25 09:12:49 xenon NetworkManager[976]: <info> [1495696369.9741] Loaded device plugin: NMVxlanDeviceFactory (internal) may 25 09:12:49 xenon NetworkManager[976]: <info> [1495696369.9818] Loaded device plugin: NMBluezManager (/usr/lib64/NetworkManager/libnm-device-plugin-bluetooth.so) may 25 09:12:49 xenon NetworkManager[976]: <info> [1495696369.9842] Loaded device plugin: NMAtmManager (/usr/lib64/NetworkManager/libnm-device-plugin-adsl.so) may 25 09:12:49 xenon NetworkManager[976]: <info> [1495696369.9857] Loaded device plugin: NMWwanFactory (/usr/lib64/NetworkManager/libnm-device-plugin-wwan.so) may 25 09:12:49 xenon NetworkManager[976]: <info> [1495696369.9885] Loaded device plugin: NMTeamFactory (/usr/lib64/NetworkManager/libnm-device-plugin-team.so) may 25 09:12:49 xenon NetworkManager[976]: <info> [1495696369.9911] Loaded device plugin: NMWifiFactory (/usr/lib64/NetworkManager/libnm-device-plugin-wifi.so) may 25 09:12:49 xenon NetworkManager[976]: <info> [1495696369.9947] device (lo): link connected may 25 09:12:49 xenon NetworkManager[976]: <info> [1495696369.9952] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1) may 25 09:12:49 xenon NetworkManager[976]: <info> [1495696369.9964] manager: (enp5s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2) may 25 09:12:49 xenon NetworkManager[976]: <info> [1495696369.9974] device (enp5s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2] may 25 09:12:50 xenon NetworkManager[976]: <info> [1495696370.1077] manager: (br-lan): new Bridge device (/org/freedesktop/NetworkManager/Devices/3) may 25 09:12:50 xenon NetworkManager[976]: <info> [1495696370.1139] bluez: use BlueZ version 5 may 25 09:12:50 xenon NetworkManager[976]: <info> [1495696370.1190] ModemManager available in the bus may 25 09:12:50 xenon NetworkManager[976]: <info> [1495696370.1195] device (br-lan): state change: unmanaged -> unavailable (reason 'managed') [10 20 2] may 25 09:12:50 xenon NetworkManager[976]: <info> [1495696370.1203] device (br-lan): state change: unavailable -> disconnected (reason 'none') [20 30 0] may 25 09:12:50 xenon NetworkManager[976]: <info> [1495696370.1206] policy: auto-activating connection 'br-lan' may 25 09:12:50 xenon NetworkManager[976]: <info> [1495696370.1215] device (br-lan): Activation: starting connection 'br-lan' (d037f754-d567-49ee-9e62-33da2324b8ce) may 25 09:12:50 xenon NetworkManager[976]: <info> [1495696370.1216] device (br-lan): state change: disconnected -> prepare (reason 'none') [30 40 0] may 25 09:12:50 xenon NetworkManager[976]: <info> [1495696370.1217] manager: NetworkManager state is now CONNECTING may 25 09:12:50 xenon NetworkManager[976]: <info> [1495696370.1226] device (br-lan): state change: prepare -> config (reason 'none') [40 50 0] may 25 09:12:50 xenon NetworkManager[976]: <info> [1495696370.4183] device (br-lan): state change: config -> ip-config (reason 'none') [50 70 0] may 25 09:12:50 xenon NetworkManager[976]: <info> [1495696370.4187] device (br-lan): IPv4 config waiting until carrier is on may 25 09:12:50 xenon NetworkManager[976]: <info> [1495696370.4187] device (br-lan): IPv6 config waiting until carrier is on may 25 09:12:51 xenon NetworkManager[976]: <info> [1495696371.1000] manager: (virbr0): new Bridge device (/org/freedesktop/NetworkManager/Devices/4) may 25 09:12:51 xenon NetworkManager[976]: <info> [1495696371.1101] manager: (virbr0-nic): new Tun device (/org/freedesktop/NetworkManager/Devices/5) may 25 09:12:51 xenon NetworkManager[976]: <info> [1495696371.1132] device (virbr0-nic): state change: unmanaged -> unavailable (reason 'connection-assumed') [10 20 41] may 25 09:12:51 xenon NetworkManager[976]: <info> [1495696371.1138] device (virbr0-nic): state change: unavailable -> disconnected (reason 'none') [20 30 0] may 25 09:12:51 xenon NetworkManager[976]: <info> [1495696371.1622] device (virbr0): state change: unmanaged -> unavailable (reason 'connection-assumed') [10 20 41] may 25 09:12:51 xenon NetworkManager[976]: <info> [1495696371.1634] ifcfg-rh: add connection in-memory (f6f08a8c-a03a-47ee-90b1-f4f3d19df55a,"virbr0") may 25 09:12:51 xenon NetworkManager[976]: <info> [1495696371.1637] device (virbr0): state change: unavailable -> disconnected (reason 'connection-assumed') [20 30 41] may 25 09:12:51 xenon NetworkManager[976]: <info> [1495696371.1642] device (virbr0): Activation: starting connection 'virbr0' (f6f08a8c-a03a-47ee-90b1-f4f3d19df55a) may 25 09:12:51 xenon NetworkManager[976]: <info> [1495696371.1654] device (virbr0): state change: disconnected -> prepare (reason 'none') [30 40 0] may 25 09:12:51 xenon NetworkManager[976]: <info> [1495696371.1657] device (virbr0): state change: prepare -> config (reason 'none') [40 50 0] may 25 09:12:51 xenon NetworkManager[976]: <info> [1495696371.1663] keyfile: add connection in-memory (ca1fed7e-141d-40f5-8dc7-bdae94f0198c,"virbr0-nic") may 25 09:12:51 xenon NetworkManager[976]: <info> [1495696371.1669] device (virbr0-nic): Activation: starting connection 'virbr0-nic' (ca1fed7e-141d-40f5-8dc7-bdae94f0198c) may 25 09:12:51 xenon NetworkManager[976]: <info> [1495696371.1669] device (virbr0): state change: config -> ip-config (reason 'none') [50 70 0] may 25 09:12:51 xenon NetworkManager[976]: <info> [1495696371.1680] device (virbr0-nic): state change: disconnected -> prepare (reason 'none') [30 40 0] may 25 09:12:51 xenon NetworkManager[976]: <info> [1495696371.1700] device (virbr0): state change: ip-config -> ip-check (reason 'none') [70 80 0] may 25 09:12:51 xenon NetworkManager[976]: <info> [1495696371.1708] device (virbr0-nic): state change: prepare -> config (reason 'none') [40 50 0] may 25 09:12:51 xenon NetworkManager[976]: <info> [1495696371.1710] device (virbr0-nic): state change: config -> ip-config (reason 'none') [50 70 0] may 25 09:12:51 xenon NetworkManager[976]: <info> [1495696371.1711] device (virbr0): bridge port virbr0-nic was attached may 25 09:12:51 xenon NetworkManager[976]: <info> [1495696371.1711] device (virbr0-nic): Activation: connection 'virbr0-nic' enslaved, continuing activation may 25 09:12:51 xenon NetworkManager[976]: <info> [1495696371.1713] device (virbr0-nic): state change: ip-config -> secondaries (reason 'none') [70 90 0] may 25 09:12:51 xenon NetworkManager[976]: <info> [1495696371.1714] device (virbr0-nic): state change: secondaries -> activated (reason 'none') [90 100 0] may 25 09:12:51 xenon NetworkManager[976]: <info> [1495696371.1976] device (virbr0-nic): Activation: successful, device activated. may 25 09:12:51 xenon NetworkManager[976]: <info> [1495696371.1992] device (virbr0): state change: ip-check -> secondaries (reason 'none') [80 90 0] may 25 09:12:51 xenon NetworkManager[976]: <info> [1495696371.1994] device (virbr0): state change: secondaries -> activated (reason 'none') [90 100 0] may 25 09:12:51 xenon NetworkManager[976]: <info> [1495696371.2061] device (virbr0): Activation: successful, device activated. may 25 09:12:51 xenon NetworkManager[976]: <info> [1495696371.2070] device (virbr0-nic): state change: activated -> unmanaged (reason 'connection-assumed') [100 10 41] may 25 09:12:51 xenon NetworkManager[976]: <info> [1495696371.2072] device (virbr0): bridge port virbr0-nic was detached may 25 09:12:51 xenon NetworkManager[976]: <info> [1495696371.2072] device (virbr0-nic): released from master device virbr0 may 25 09:12:53 xenon NetworkManager[976]: <info> [1495696373.5299] device (enp5s0): link connected may 25 09:12:53 xenon NetworkManager[976]: <info> [1495696373.5307] device (enp5s0): state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40] may 25 09:12:53 xenon NetworkManager[976]: <info> [1495696373.5312] policy: auto-activating connection 'enp5s0' may 25 09:12:53 xenon NetworkManager[976]: <info> [1495696373.5317] device (enp5s0): Activation: starting connection 'enp5s0' (3f9bb58c-06d5-434d-87eb-4209311196cf) may 25 09:12:53 xenon NetworkManager[976]: <info> [1495696373.5318] device (enp5s0): state change: disconnected -> prepare (reason 'none') [30 40 0] may 25 09:12:53 xenon NetworkManager[976]: <info> [1495696373.5321] device (enp5s0): state change: prepare -> config (reason 'none') [40 50 0] may 25 09:12:53 xenon NetworkManager[976]: <info> [1495696373.5390] device (enp5s0): state change: config -> ip-config (reason 'none') [50 70 0] may 25 09:12:53 xenon NetworkManager[976]: <info> [1495696373.5406] device (br-lan): attached bridge port enp5s0 may 25 09:12:53 xenon NetworkManager[976]: <info> [1495696373.5407] device (enp5s0): Activation: connection 'enp5s0' enslaved, continuing activation may 25 09:12:53 xenon NetworkManager[976]: <info> [1495696373.5407] device (br-lan): IPv4 config waiting until carrier is on may 25 09:12:53 xenon NetworkManager[976]: <info> [1495696373.5407] device (br-lan): IPv6 config waiting until carrier is on may 25 09:12:53 xenon NetworkManager[976]: <info> [1495696373.5410] device (enp5s0): state change: ip-config -> secondaries (reason 'none') [70 90 0] may 25 09:12:53 xenon NetworkManager[976]: <info> [1495696373.5412] device (enp5s0): state change: secondaries -> activated (reason 'none') [90 100 0] may 25 09:12:53 xenon NetworkManager[976]: <info> [1495696373.5643] device (enp5s0): Activation: successful, device activated. may 25 09:13:10 xenon NetworkManager[976]: <info> [1495696390.8740] device (br-lan): link connected may 25 09:13:10 xenon NetworkManager[976]: <info> [1495696390.8747] dhcp4 (br-lan): activation: beginning transaction (timeout in 45 seconds) may 25 09:13:10 xenon NetworkManager[976]: <info> [1495696390.8801] dhcp4 (br-lan): dhclient started with pid 1883 may 25 09:13:10 xenon dhclient[1883]: DHCPREQUEST on br-lan to 255.255.255.255 port 67 (xid=0x3bfd755b) may 25 09:13:10 xenon dhclient[1883]: DHCPACK from 192.168.1.254 (xid=0x3bfd755b) may 25 09:13:10 xenon NetworkManager[976]: <info> [1495696390.9106] dhcp4 (br-lan): address 192.168.1.10 may 25 09:13:10 xenon NetworkManager[976]: <info> [1495696390.9107] dhcp4 (br-lan): plen 24 (255.255.255.0) may 25 09:13:10 xenon NetworkManager[976]: <info> [1495696390.9107] dhcp4 (br-lan): gateway 192.168.1.254 may 25 09:13:10 xenon NetworkManager[976]: <info> [1495696390.9107] dhcp4 (br-lan): lease time 7200 may 25 09:13:10 xenon NetworkManager[976]: <info> [1495696390.9107] dhcp4 (br-lan): hostname 'xenon' may 25 09:13:10 xenon NetworkManager[976]: <info> [1495696390.9107] dhcp4 (br-lan): nameserver '192.168.1.254' may 25 09:13:10 xenon NetworkManager[976]: <info> [1495696390.9107] dhcp4 (br-lan): domain name 'lan' may 25 09:13:10 xenon NetworkManager[976]: <info> [1495696390.9107] dhcp (br-lan): domain search 'lan.' may 25 09:13:10 xenon NetworkManager[976]: <info> [1495696390.9107] dhcp (br-lan): domain search 'miceliux.com.' may 25 09:13:10 xenon NetworkManager[976]: <info> [1495696390.9107] dhcp4 (br-lan): state changed unknown -> bound may 25 09:13:10 xenon NetworkManager[976]: <info> [1495696390.9116] device (br-lan): state change: ip-config -> ip-check (reason 'none') [70 80 0] may 25 09:13:10 xenon dhclient[1883]: bound to 192.168.1.10 -- renewal in 2935 seconds.
I think this is a duplicate of bug 1404350, as now we use libpsl to detect public suffixes and any single-label domain is considered a public suffix [1]. [1] https://github.com/rockdaboot/libpsl/blob/8fddb720331c14b3fac6df1701779d1f943a185e/src/psl.c#L809
*** This bug has been marked as a duplicate of bug 1470966 ***