macOS 11 (Big Sur) and later accept encrypted DNS through a configuration
profile, the same .mobileconfig file iOS uses. It applies to every app and
every network interface.
Under Encrypted DNS, fill in Name a device (optional), for
example Work MacBook, so the Mac shows as work-macbook in Logs and
Analytics.
In iOS and macOS configuration profile, choose DNS-over-HTTPS
(recommended) or DNS-over-TLS, and click Download configuration
profile. The file lands in your Downloads folder as
opdns-<profile-id>-<device>-doh.mobileconfig.
The note under the download button on the Setup page says how macOS will
label the profile: Verified when opdns signs it, Unverified while it
is not signed; either is expected. It holds only the DNS setting. Downloading
again with the same device name replaces the installed profile instead of
adding a second one.
Double-click the downloaded file. macOS says the profile was downloaded
and needs review.
Open System Settings, search for Profiles, and open it (under
General → Device Management on macOS 15 and later, Privacy &
Security → Profiles on earlier versions).
Double-click the opdns profile, click Install, and authenticate.
Screenshot to comemacOS System Settings showing the opdns profile under Device Management with its DNS settings payload.macOS 15
The full message is Profile installation failed. The ‘VPN Service’
payload could not be installed. The VPN service could not be created.
macOS handles encrypted DNS settings with the same system component as
VPNs, which is why it says “VPN” although the profile holds only a DNS
setting. It means macOS refused to add the setting. It is not something
you did wrong. Try these in order, and install again after each one:
Download the profile again. Since macOS 26.1, macOS only accepts a
DNS profile that installs for the whole Mac rather than for one user.
Profiles from the dashboard now say so; an older file may not. Download
a fresh one from the Setup page and install that.
Remove any previous DNS profile. In System Settings → General →
Device Management (or Privacy & Security → Profiles), remove any
older opdns profile and any profile from another DNS service. macOS uses
one DNS profile at a time, and an old one, or one left behind by an
earlier failed install, can get in the way.
Pause VPN and DNS apps while you install. Apps that manage DNS can
get in the way: quit them or turn off their DNS feature, install the
profile, then turn them back on (and read
Using opdns with a VPN).
Tailscale: click the Tailscale icon in the menu bar and untick
Use Tailscale DNS settings, or disconnect.
NetBird: in the NetBird app’s settings, turn off Enable DNS, or
disconnect. From Terminal, netbird down then
netbird up --disable-dns does the same.
Others: another DNS app (another filtering DNS service, a
“1.1.1.1”-style app), a VPN app, or a network filter or firewall app:
disconnect or quit it. In System Settings → VPN and System
Settings → Network, look for DNS or filter entries left by apps you
no longer use, and remove them.
Restart the Mac. macOS can hold on to the settings of a removed
profile or app until a restart. Restart, then install the profile
before connecting any VPN.
If it still fails, contact support and include your
macOS version (Apple menu → About This Mac) and the VPN or DNS apps
installed, and we will help you get it working.
While a VPN that sets its own DNS server is connected, macOS sends DNS
questions to that server instead of opdns: filtering, logs and analytics
pause for that Mac and come back when the VPN disconnects. The opdns profile
still shows as installed and on, which is confusing but expected. Apple
documents this behaviour, and VPN apps cannot see or forward to an
encrypted DNS profile.
Tailscale: with Use Tailscale DNS settings on, names go to
Tailscale’s own resolver, which passes names outside your tailnet to your
network’s ordinary DNS, not to opdns. Untick it to keep opdns (you lose
Tailscale’s short device names such as my-server), or ask your Tailscale
admin to add opdns as a nameserver for the whole tailnet (that applies to
every device on it, not just this Mac).
NetBird: if your NetBird network sets a DNS server for all names,
NetBird’s resolver answers instead of opdns. Turning off Enable DNS
keeps opdns but loses NetBird’s own names.
Any VPN:check it works with the VPN connected.
If the check says you are not using opdns, the VPN’s DNS is in use.
If your network has IPv6, you can instead enter the profile’s IPv6
address from the Setup page under System Settings → Network → (your
connection) → Details → DNS. This is not encrypted and carries no device
name.
If you cannot download the file from the dashboard, the template on the
iOS page works on
macOS too: fill it in, save it as opdns.mobileconfig, and install it as
above.