# systemd-resolved

10 Hacker News commenters recommended systemd-resolved and 11 criticized it, November 2025 to November 2026. It was recommended in 6 of 13 months.

**Verdict:** Recommended for being integrated with systemd, well documented and useful; critics say it invents DNS records and breaks standard behavior.

## Why people recommend it

- Works well with systemd-networkd (3 comments): "I'm glad systemd-networkd (advertising) and systemd-resolved (finding) just integrate these concerns for me" ([source](https://news.ycombinator.com/item?id=49769769)) "I'm quite happy with systemd-resolved and systemd-networkd" ([source](https://news.ycombinator.com/item?id=48104508)) "they generally work together pretty cohesively" ([source](https://news.ycombinator.com/item?id=46367205))
- Handles DNS tasks automatically (2 comments): "I'm glad systemd-networkd (advertising) and systemd-resolved (finding) just integrate these concerns for me" ([source](https://news.ycombinator.com/item?id=49769769)) "does DNS-over-TLS stub resolution for me" ([source](https://news.ycombinator.com/item?id=48105024))
- Reliable in daily use (2 comments): "In my experience, that works every time." ([source](https://news.ycombinator.com/item?id=48108794)) "systemd-resolved working as intended" ([source](https://news.ycombinator.com/item?id=46689830))

## What people warn about

- Alters DNS answers, breaks protocol (3 comments): "Systemd-resolved invents DNS records (not really something you would like to see, makes debugging DNS issues a nightmare)" ([source](https://news.ycombinator.com/item?id=46058958)) "Did you know that it will convert the answer to a relative query that has generated an NXDOMAIN into a REFUSED?" ([source](https://news.ycombinator.com/item?id=48381195)) "it is a clearly defined protocol, which systemd-resolved breaks" ([source](https://news.ycombinator.com/item?id=46118349))
- Poor DNSSEC key and signature handling (2 comments): "systemd-resolved on older, but still supported Ubuntu versions 24.04 LTS and 22.04 LTS does not know about the new KSK" ([source](https://news.ycombinator.com/item?id=50077820)) "Turned out that systemd did reject their signed subdomains." ([source](https://news.ycombinator.com/item?id=49572454))
- Seen as poor networking design (4 comments): "Redefining recursive DNS resolution as general 'name resolution' is indeed exactly the kind of horror I expect from the systemd project." ([source](https://news.ycombinator.com/item?id=46076702)) "systemd has no f*cking clue what they're doing on networking" ([source](https://news.ycombinator.com/item?id=48104385)) "That's introductory course to systemd's shenanigans." ([source](https://news.ycombinator.com/item?id=48375420))
- Complex, often removed from installs (2 comments): "driven me to a policy of ripping out systemd-resolved entirely on any new installation" ([source](https://news.ycombinator.com/item?id=46786232)) "they very quickly run off into the weeds with their crazy features and configuration" ([source](https://news.ycombinator.com/item?id=46310939))

## Alternatives hackers recommend

- [Cloudflare DNS](https://hackerapproved.com/p/cloudflare-dns.md): 52 recommend
- [Unbound DNS resolver](https://hackerapproved.com/p/unbound.md): 45 recommend
- [Google Public DNS](https://hackerapproved.com/p/google-public-dns.md): 18 recommend
- [Numa DNS resolver](https://hackerapproved.com/p/numa-dns-resolver.md): 10 recommend
- [DNS4EU](https://hackerapproved.com/p/dns4eu.md): 5 recommend

## Cite as

Hacker Approved, "systemd-resolved", https://hackerapproved.com/p/systemd-resolved/ (counts from 1,795,640 Hacker News comments, November 2025 to November 2026).