See which DNS servers you're using
Show the per-connection resolver settings that systemd-resolved is actually applying.
01Command
$ resolvectl status | grep -A2 'DNS Servers'02What it does
Modern Ubuntu and Fedora don't read /etc/resolv.conf the old way; systemd-resolved manages DNS per link, and resolvectl status reveals it. This answers 'why is my Pi-hole/AdGuard DNS not working?' — you can see instantly whether your custom server is listed under the right interface or whether the router's DNS is still being used. Global DNS appears at the top; per-link servers below each interface.
03Risk
04Undo
✓No undo needed — this command does not change persistent state.
05Sources
- resolvectl(1) — manual pageEvidence: resolvectl status shows the DNS servers and domains configured per link by systemd-resolved.
- systemd-resolved — Arch WikiEvidence: resolvectl status is the way to inspect which DNS servers systemd-resolved is using per interface.
Last verified: 2026-09-18 · Category: Network
06Related solutions
On systemd-based Linux (Ubuntu, Fedora, Debian 12+), the local DNS stub cache is managed by systemd-resolved — and the command to clear it is easy to forget because it changed from systemd-resolve.
Query any DNS record type for a domain, with a compact answer or the full response including headers and TTLs.
One command that prints every interface with its state and IPv4/IPv6 addresses in a short table — the modern, memorable replacement for digging through `ifconfig` or the verbose `ip addr` output.