Get past airport/hotel captive portals blocked by forced DNS and DNS-over-TLS
Cause verified against bin/omarchy-dns: it does write DNS=...#cloudflare-dns.com plus DNSOverTLS=opportunistic to /etc/systemd/resolved.conf and a [global-dns-domain-*] servers= block to /etc/NetworkManager/conf.d/20-omarchy-dns.conf, and omarchy dns DHCP is a real, correctly-spelled invocation that writes exactly the [Resolve]\nDNSOverTLS=no shown. The manual fallback is incomplete in a way that leaves the user still broken: omarchy-dns also runs set_connection_dns, which stamps ipv4.ignore-auto-dns yes + ipv4.dns 1.1.1.1 1.0.0.1 (and the IPv6 equivalents) onto EVERY wifi/ethernet profile. Deleting the two global files does not undo that, so the portal still cannot hijack DNS.
Symptom
Repeated failures on airport, hotel and university Wi-Fi: you associate fine, the portal sometimes appears, but after clicking through nothing loads. http://captive.apple.com and http://example.com cannot be reached. Public IPs ping fine, so it is purely DNS. Setting nameserver 1.1.1.3 in /etc/resolv.conf by hand does not help either.
Cause
Omarchy's DNS helper writes a hard DNS= list plus DNSOverTLS=opportunistic into /etc/systemd/resolved.conf and a global-DNS override into /etc/NetworkManager/conf.d/20-omarchy-dns.conf. Captive portals work by hijacking plain DNS on port 53 and only whitelisting the portal host. A pinned upstream resolver reached over TLS on port 853 is simply blocked before you authenticate, so the portal redirect never happens and no name ever resolves.
Fix
Preferred: the helper clears all three layers:
omarchy dns DHCP # Omarchy 4.x (Quattro)
Manual equivalent, if the helper is unavailable. Note the third step, which the global files alone do not cover:
# 1. global NetworkManager override
sudo rm -f /etc/NetworkManager/conf.d/20-omarchy-dns.conf
# 2. resolved's pinned upstream + DoT
sudo tee /etc/systemd/resolved.conf >/dev/null <<'EOF'
[Resolve]
DNSOverTLS=no
EOF
# 3. per-profile DNS that omarchy-dns also wrote onto every wifi/ethernet profile
while IFS=: read -r uuid type; do
case "$type" in 802-11-wireless|802-3-ethernet)
sudo nmcli connection modify "$uuid" \
ipv4.ignore-auto-dns no ipv4.dns "" \
ipv6.ignore-auto-dns no ipv6.dns "" ;;
esac
done < <(nmcli -t -f UUID,TYPE connection show)
sudo systemctl restart systemd-resolved NetworkManager
Then force the portal open:
resolvectl status | grep -A3 'Link.*wlan0' # DNS Servers must now be the AP's address
xdg-open http://neverssl.com
Switch back afterwards with omarchy dns Cloudflare.
Verify
resolvectl status shows the link's DNS server as the local gateway and DNSOverTLS=no. curl -sI http://neverssl.com returns a 302 to the portal.