OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
network medium common DISPUTE

Make DHCP-provided search domains work for short local hostnames

omarchyarchendeavouroscachyosdesktoplaptop
AUDITED Audited against its sources and confirmed accurate.

Symptom

Short local names do not resolve. ping thing fails while ping thing.example.net works, on a network whose DHCP server hands out example.net as the search domain. The only thing that helps is hand-editing /etc/resolv.conf to say search example.net and adding the local nameserver, which the next reconnect wipes out.

Cause

A pinned global DNS provider (Omarchy's 20-omarchy-dns.conf plus DNS= in resolved.conf) replaces the DHCP-supplied nameserver, and with the DHCP resolver gone the DHCP search domain is not applied either. resolv.conf ends up with search . and a public resolver that knows nothing about your local zone.

Fix

Return to DHCP-supplied DNS so the search domain comes with it:


omarchy dns DHCP        # Omarchy 4.x; writes only DNSOverTLS=no and clears the NM override
sudo systemctl restart systemd-resolved NetworkManager

If you want to keep a custom resolver but still get the domain, set both explicitly on the profile:


sudo nmcli connection modify "<SSID>" ipv4.ignore-auto-dns no
sudo nmcli connection modify "<SSID>" ipv4.dns-search "example.net"
sudo nmcli connection up "<SSID>"

And to route just that zone at your local resolver while everything else goes upstream:


sudo resolvectl dns wlan0 192.168.1.1
sudo resolvectl domain wlan0 example.net

Verify

resolvectl status wlan0 lists DNS Domain: example.net, and getent hosts thing resolves to the local address.

Sources

dhcp-search-domain-ignored