OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
network high occasional DISPUTE

Use an encrypted-only resolver such as Mullvad with omarchy dns Custom

omarchysystemd-resolvednetworkmanagerdns
CORRECTED An auditor found the fix wrong or incomplete and rewrote it. · checked against Omarchy omarchy 4.0.4-1 on 2026-10-05
AUDIT NOTE

Read /usr/share/omarchy/bin/omarchy-dns on 4.0.4-1, which is byte-identical to the quattro tip. The Custom branch writes a bare DNS= line and the FallbackDNS line with no DNSOverTLS=. It also writes the NetworkManager global-dns file and sets every Wi-Fi and Ethernet profile to ignore-auto-dns, as the cause says. Issue #8921 and its triage comment support the cause, the FallbackDNS behaviour and the workaround, which is the fix here. PR #6513 is still OPEN. The verify step is wrong in two places. First, resolvectl status on this workstation (Cloudflare preset, DNSOverTLS=opportunistic) prints DNSOverTLS=opportunistic in the Global Protocols line, not +DNSOverTLS, which resolvectl prints only for yes. Second, the verify said a remaining timeout means NetworkManager's per-link servers lack a TLS name. On this machine, with the same NetworkManager global-dns file the Custom branch writes, every link shows Current Scopes: none and no per-link DNS servers, so the resolved.conf global servers are the only ones queried. That claim, and the previous audit note's worry about per-link copies, did not hold here, so the verify now points at the likely real cause, a blocked port 853. The danger is extended because with a DoT-only resolver opportunistic fails the same way as yes when 853 is blocked. The cause and fix are kept. Only the Cloudflare preset was observed live. Custom was not run.

The cause above was rewritten on 2026-10-04 to match this note; the fix was corrected by the audit itself.
RISK

With a resolver that answers only DNS-over-TLS, such as Mullvad, DNS fails on any network that blocks port 853. This happens with DNSOverTLS=opportunistic as well as yes, because opportunistic falls back to plain DNS, which that resolver does not answer. DNSOverTLS=yes also breaks DNS on captive-portal networks until you switch back (see captive-portal-never-loads-forced-dns). omarchy dns DHCP undoes everything without needing working DNS.

Symptom

After omarchy dns Custom with a privacy resolver such as Mullvad (194.242.2.4 2a07:e340::4), the internet seems to be down. No site loads, but Wi-Fi is connected and ping 1.1.1.1 works. resolvectl query archlinux.org times out. The Quad9 fallback in /etc/systemd/resolved.conf never takes over.

Cause

The Custom branch of omarchy-dns writes a bare DNS= line into /etc/systemd/resolved.conf, with no #hostname and no DNSOverTLS=. resolved's default is DNSOverTLS=no, so queries go out as plain DNS on port 53, which the issue reports Mullvad does not answer. The Cloudflare and Google presets write IP#hostname with DNSOverTLS=opportunistic, but Custom does not. Custom also writes the same addresses into /etc/NetworkManager/conf.d/20-omarchy-dns.conf under [global-dns-domain-*], and into every saved Wi-Fi and Ethernet profile with ignore-auto-dns yes, so DHCP or a VPN cannot override them. FallbackDNS= is used only when no DNS server is configured at all, so an unresponsive configured server never falls back. Confirmed on 4.0.4-1 in /usr/share/omarchy/bin/omarchy-dns. Open PR #6513 adds the missing DNSOverTLS=opportunistic line.

Fix

Run omarchy dns Custom with the addresses as usual, then add the TLS server name and turn on DNS-over-TLS in /etc/systemd/resolved.conf:


sudo tee /etc/systemd/resolved.conf >/dev/null <<'EOF'
[Resolve]
DNS=194.242.2.4#base.dns.mullvad.net 2a07:e340::4#base.dns.mullvad.net
FallbackDNS=9.9.9.9#dns.quad9.net 149.112.112.112#dns.quad9.net 2620:fe::fe#dns.quad9.net 2620:fe::9#dns.quad9.net
DNSOverTLS=opportunistic
EOF
sudo systemctl reload systemd-resolved.service

Use DNSOverTLS=yes instead to refuse plain DNS entirely, which also validates the server name.

Running omarchy dns again (any provider) rewrites /etc/systemd/resolved.conf and removes this edit. To undo everything, run omarchy dns DHCP.

A resolver that answers plain DNS (your router, a Pi-hole) needs none of this.

Verify


resolvectl status | grep -E 'DNSOverTLS|DNS Servers|Current DNS|Current Scopes'
resolvectl query archlinux.org

The Global section should show DNSOverTLS=opportunistic (or +DNSOverTLS if you chose DNSOverTLS=yes) and the #base.dns.mullvad.net servers, and the query should return an address. With the NetworkManager global-dns file that omarchy dns writes, the links show Current Scopes: none and no per-link servers, so the global servers in /etc/systemd/resolved.conf are the only ones in use. If the query still times out, the network is probably blocking port 853. Run omarchy dns DHCP to recover.

Sources

omarchy-dns-custom-dot-only-resolver-breaks-dns