We are looking for the property that will search domains when you lookup up a hostname.
On one of your working ones, even grep -i -E ‘dns|domain’ for it.
Try disabling that ^^^ in NM and see if it helps…
1 Like
Well, no, but I’m grasping at straws, as is apparently everyone else 
This did not help 
nmcli -p conn show "Wired connection 1" | grep -i -E 'dns|domain'
connection.mdns: -1 (default)
connection.dns-over-tls: -1 (default)
ipv4.dns: --
ipv4.dns-search: --
ipv4.dns-options: --
ipv4.dns-priority: 0
ipv4.ignore-auto-dns: no
ipv6.dns: --
ipv6.dns-search: --
ipv6.dns-options: --
ipv6.dns-priority: 0
ipv6.ignore-auto-dns: no
IP4.DNS[1]: 192.168.1.1
DHCP4.OPTION[5]: domain_name_servers = 192.168.1.1
DHCP4.OPTION[11]: requested_domain_name = 1
DHCP4.OPTION[12]: requested_domain_name_servers = 1
DHCP4.OPTION[13]: requested_domain_search = 1
DHCP4.OPTION[17]: requested_nis_domain = 1
It’s the same as the non-working one.
At least you can see all the DHCP options the DHCP server has passed you there. There is DHCP option for the domain it is on, and another option for a search list of domains.
https://en.wikipedia.org/wiki/Dynamic_Host_Configuration_Protocol#Options
Your router DHCP server probably only uses only a dozen or so, but the TLDR of the hundreds built in the protocol is: Option 15 for domain, and option 119 for domain search list. I know both work, as I’ve used them both via DHCP server.
I was just guessing at grep terms to filter through, as it included the ones I had. But I assume none of those options has your domain? (In the DHCP.OPTION[*] portion.)
I have DHCP4.OPTION[4]: domain_name = hosenet.local
Note: The OPTION[#] does not translate to the option numbers for DHCP, that is part of the protocol you can look up. These numbers, I assume, are just NetworkManager’s ordering, or in the order it got them.
If NM got either of those DHCP options, it should configure the search domain(s).