FS#55045 - [networkmanager] Single word domain name from DHCP not set in resolv.conf

Attached to Project: Arch Linux
Opened by Andy Botting (andybz) - Sunday, 06 August 2017, 02:54 GMT
Last edited by Jan de Groot (JGC) - Saturday, 19 August 2017, 21:40 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Jan de Groot (JGC)
Jan Alexander Steffens (heftig)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


Description: With a single word domain name, Network Manager won't set the 'domain' option in resolv.conf.

For example, using home, lan or foo for example, doesn't work. Setting to something more traditional style like foo.bar, home.lan works perfectly.

I've tested using a couple of other OSs, including LibreELEC (uses Connection Manager) and Mac OS X that work fine.

I rolled back to the latest pre-1.8 package I had (networkmanager-1.6.2-3) and the problem went away.

I've also tried changing the DNS handler within Network Manager to dnsmasq, but no difference.

Additional info:
* package version(s): 1.8.0-1 or later
* config and/or log files etc.

Steps to reproduce:
On local router, set domain name to a single word like home or lan. Restart NetworkManager and wait for a DHCP client to do its thing.
This task depends upon

Closed by  Jan de Groot (JGC)
Saturday, 19 August 2017, 21:40 GMT
Reason for closing:  Fixed
Additional comments about closing:  1.8.3dev+18+gf43222d41
Comment by Andy Botting (andybz) - Sunday, 06 August 2017, 09:48 GMT
Posted this into #nm on FreeNode:

bengal: yeah, this is fixed by commit https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?h=nm-1-8&id=e80163c713cdd911cb79036f3f7b629040297c58 , which will be in 1.8.4