# Fixed upstream resolvers for this router — see deploy.conf's DNS_RESOLVERS.
# Never the WAN-provided ones: the failover/60-van-wan-dns NM dispatcher
# strips each WAN's DHCP/RA-provided DNS from resolved as soon as it appears
# (NM's own ipv4/ipv6.ignore-auto-dns can't be set as a config-file default —
# it's rejected as an unknown key there, even though it's a real per-
# connection property), so these are the only unicast resolvers in play,
# regardless of whether the WAN is Wapana, Starlink, or cellular.
# Domains=~. makes them the default route for every query (there being no
# competing per-link DNS to prioritize over them in the first place).
#
# This does NOT affect .local (mDNS) resolution — that's handled separately,
# per-link, only on br0 (see 21-van-br0.network's MulticastDNS=yes), so
# ESPHome/other mDNS devices on the van's own LAN still resolve.
#
# ZeroTier's own DNS (zt.wrede.pvt, via zerotier-systemd-manager) is a
# separate, more-specific routing domain on the ztuga7c2kh link and is
# unaffected by this — resolved always prefers a domain-specific route over
# the Domains=~. fallback.
[Resolve]
DNS=@DNS_RESOLVERS@
Domains=~.
# Global default: resolved gates per-link MulticastDNS=yes settings behind
# this — a link can't enable mDNS on its own if the global default is "no"
# (confirmed: "Setting mDNS support level yes for X, but the global support
# level is no"). br0 (21-van-br0.network) opts in; every WAN link is opted
# back out explicitly by failover/60-van-wan-dns so mDNS stays scoped to the
# van's own LAN and never leaks onto Wapana/Starlink/cellular.
MulticastDNS=yes