Arch Linux

baggar11

Member

Registered: 2014-03-12

Posts: 19

NetworkManager v1.7.91+ Not Adding Search Domain

For some reason, any version of NetworkManager above 1.6.2-3 will not properly add the search domain to the resolv.conf file. I've been holding out for a while hoping someone else would come across this too, but haven't seen any posts about it. I only seem to be experiencing this phenomenon on my home workstations. My Arch workstation at work is fine.

If I use a version above 1.6.2-3, I can manually add the search domain and local resolution begins to work again. I can also see the relevant lines in journalctl where it sees my home search domain, it just doesn't add it to resolv.conf. Else, downgrading to 1.6.2-3 and a reboot picks up the search domain properly.

You guys have any ideas on where to look on fixing this? Thanks!

Slithery

Administrator

From: Norfolk, UK

Registered: 2013-12-01

Posts: 5,776

Re: NetworkManager v1.7.91+ Not Adding Search Domain

No solution yet but it's the same issue as this recent thread...

https://bbs.archlinux.org/viewtopic.php?id=225667

---

No, it didn't "fix" anything. It just shifted the brokeness one space to the right. - jasonwryan
Closing -- for deletion; Banning -- for muppetry. - jasonwryan

aur - dotfiles

baggar11

Member

Registered: 2014-03-12

Posts: 19

Re: NetworkManager v1.7.91+ Not Adding Search Domain

Just added a bug report for this.

https://bugs.archlinux.org/task/54455

whiterabbit

Member

Registered: 2011-01-30

Posts: 11

Re: NetworkManager v1.7.91+ Not Adding Search Domain

Hi baggar11, thanks for the bug report.

I had the same problem (custom DNS resolver on my home network, and dns-search set to lan) :
https://bbs.archlinux.org/viewtopic.php?id=226794

From what Jan de Groot said on that bug report, with the new behaviour of NetworkManager you can no longer use dummy TLD for your domain search, you have to use a valid TLD, one that is on the Public Suffix List (PSL) :
https://hg.mozilla.org/mozilla-central/ … _names.dat

libpsl is a C library used to check the validity of a domain name, it doesn't matter which IP class you use : if your dns-search value is based on a dummy TLD, it will be ignored by NetworkManager.

baggar11

Member

Registered: 2014-03-12

Posts: 19

Re: NetworkManager v1.7.91+ Not Adding Search Domain

So our only option is to use a valid public domain and hope we never have to visit that domain legitimately since our own local network will be advertising it? That doesn't sound like a very good solution.

rsmarples

Member

Registered: 2009-05-12

Posts: 287

Re: NetworkManager v1.7.91+ Not Adding Search Domain

So our only option is to use a valid public domain and hope we never have to visit that domain legitimately since our own local network will be advertising it? That doesn't sound like a very good solution.

.local is valid and guaranteed not to be on the public internet. Use that.

https://en.wikipedia.org/wiki/.local

whiterabbit

Member

Registered: 2011-01-30

Posts: 11

Re: NetworkManager v1.7.91+ Not Adding Search Domain

Correct, .local is not ignored by NetworkManager, as long as you don't use it directly, you have to use a subdomain, i.e. foobar.local

Edit :

Using .local may not be a good solution if you have devices using Bonjour / Avahi zeroconf on your network.
.local is reserved for MulticastDNS (mDNS) and that can conflict with hosts using it.

See the  RFC 6762, appendix G : https://tools.ietf.org/html/rfc6762#appendix-G

Using ".local" as a private top-level domain conflicts with Multicast DNS and may cause problems for users [...] this results in additional network traffic and additional delays in name resolution

Second edit :

Actually, lan is not ignored either if you use a subdomain, I tried to set dns-search to home.lan and it worked.
It seems that the dns-search validation only checks if you have a well formed FQDN with at least two labels.

Last edited by whiterabbit (2017-06-17 18:36:27)

baggar11

Member

Registered: 2014-03-12

Posts: 19

Re: NetworkManager v1.7.91+ Not Adding Search Domain

Just to circle back to this. It's been a couple weeks since I solved this and localdomain and home still seem to work. As long as you have it in a format such as "example.home" or "example.localdomain." Apparently the new version of NetworkManager just ignores ".localdomain" and ".home" if they are by themselves. Unsure why, as Windows and other Linux's like Debian/Ubuntu/CentOS don't seem to ignore the search domain when presented with such. Arch is apparently cutting edge in this regard.