Dns

Introduction to systemd-resolved

I’ve been using Linux for years, and I’ve had my fair share of struggles with DNS resolution. Recently, I decided to take a closer look at systemd-resolved, the DNS resolver component of systemd. I was looking for a reliable way to resolve DNS at home, and I’m happy to share what I’ve learned.

What is systemd-resolved?

systemd-resolved is a system service that provides DNS resolution for Linux systems. It’s designed to replace traditional DNS resolvers like bind and dnsmasq. One of the key benefits of systemd-resolved is its integration with the rest of the systemd ecosystem, making it easy to manage and configure. Don’t bother with bind and dnsmasq unless you have a specific reason to - systemd-resolved is a solid choice for most users.

Introduction to DNS Resolution Issues

I’ve been running my own homelab for years, and like many of you, I’ve had my fair share of DNS resolution issues. Last year, I decided to ditch my router as a DNS server and set up Unbound and systemd-resolved on my Linux machines instead. The goal was to improve DNS resolution speed and security, but as you can probably guess, it wasn’t all smooth sailing.

The Domain Name System (DNS) is a fundamental component of the internet. It translates human-readable domain names like example.com into IP addresses such as 93.184.216.34, allowing users to connect to websites and services without memorizing numerical addresses. For Linux users, understanding DNS and managing DNS servers is essential for troubleshooting, configuring networks, and ensuring smooth internet connectivity.

What is DNS?

DNS functions as the internet’s phonebook. When you type a domain name into a browser, DNS resolves it into the corresponding IP address so your computer can establish a connection. This resolution process involves several DNS components: