Article proposal: systemd-resolved: rationale and configuration

Why resolved: single lookup mechanism, cache, dynamic interface and server lists, split dns, dbus api.
How to configure resolved: search domains, routing domains.
State introspection: resolvectl dns, resolvectl domain, etc.
Integration of NetworkManager and resolved.
Examples:

  • VPN trusted more than local network
  • company VPN that should only handle company traffic

My primary goal is to explain how domain routing works, i.e. how resolved decides which servers to query for a given name.

I don’t want to talk LLMNR, mDNS, DNSSEC, or DoT in the first article. Maybe that’d be a good subject for a second article.
DoT was described in https://fedoramagazine.org/use-dns-over-tls/.

This article was requested in https://meetbot.fedoraproject.org/teams/fesco/fesco.2020-09-30-14.00.html.

1 Like

+1 from me. This would be great, especially since this is an F33 Change.

Sounds good to me too, +1. Zbyszek, you probably want to log in to our Taiga board so we can put in a card for you and assign it to you to track article progress.

Thank you. I have already logged into Taiga.