<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Dns on Linux Café</title>
    <link>https://mrtomlinux.org/tags/dns/</link>
    <description>Recent content in Dns on Linux Café</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Tue, 07 Jul 2026 09:00:33 +0200</lastBuildDate>
    <atom:link href="https://mrtomlinux.org/tags/dns/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Resolving DNS Troubles at Home: A systemd-resolved and dnsmasq Setup Gone Wrong</title>
      <link>https://mrtomlinux.org/post/2026-07-07-resolving-dns-troubles-at-home-a-systemd-reso/</link>
      <pubDate>Tue, 07 Jul 2026 09:00:33 +0200</pubDate>
      <guid>https://mrtomlinux.org/post/2026-07-07-resolving-dns-troubles-at-home-a-systemd-reso/</guid>
      <description>&lt;h2 id=&#34;introduction-to-dns-troubles&#34;&gt;Introduction to DNS Troubles&lt;/h2&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve been running my homelab for years, and one thing that still gets me is DNS troubles. Last year, I decided to set up &lt;code&gt;systemd-resolved&lt;/code&gt; and &lt;code&gt;dnsmasq&lt;/code&gt; to manage my home network&amp;rsquo;s DNS. The idea was to use &lt;code&gt;systemd-resolved&lt;/code&gt; as the primary resolver and &lt;code&gt;dnsmasq&lt;/code&gt; as a caching layer to improve performance. Sounds simple, but it didn&amp;rsquo;t quite work out that way.&lt;/p&gt;&#xA;&lt;h2 id=&#34;setting-up-systemd-resolved&#34;&gt;Setting Up systemd-resolved&lt;/h2&gt;&#xA;&lt;p&gt;To start, I enabled &lt;code&gt;systemd-resolved&lt;/code&gt; on my Ubuntu-based server. This involved editing the &lt;code&gt;/etc/systemd/resolved.conf&lt;/code&gt; file to set the DNS servers and domains. I opted for Cloudflare&amp;rsquo;s DNS servers - they&amp;rsquo;re known for being fast and secure.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Taming systemd-resolved: My Journey to Reliable DNS Resolution at Home</title>
      <link>https://mrtomlinux.org/post/2026-06-10-taming-systemd-resolved-my-journey-to-reliabl/</link>
      <pubDate>Wed, 10 Jun 2026 08:31:17 +0200</pubDate>
      <guid>https://mrtomlinux.org/post/2026-06-10-taming-systemd-resolved-my-journey-to-reliabl/</guid>
      <description>&lt;h2 id=&#34;introduction-to-systemd-resolved&#34;&gt;Introduction to systemd-resolved&lt;/h2&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve been using Linux for years, and I&amp;rsquo;ve had my fair share of struggles with DNS resolution. Recently, I decided to take a closer look at &lt;code&gt;systemd-resolved&lt;/code&gt;, the DNS resolver component of systemd. I was looking for a reliable way to resolve DNS at home, and I&amp;rsquo;m happy to share what I&amp;rsquo;ve learned.&lt;/p&gt;&#xA;&lt;h2 id=&#34;what-is-systemd-resolved&#34;&gt;What is systemd-resolved?&lt;/h2&gt;&#xA;&lt;p&gt;&lt;code&gt;systemd-resolved&lt;/code&gt; is a system service that provides DNS resolution for Linux systems. It&amp;rsquo;s designed to replace traditional DNS resolvers like &lt;code&gt;bind&lt;/code&gt; and &lt;code&gt;dnsmasq&lt;/code&gt;. One of the key benefits of &lt;code&gt;systemd-resolved&lt;/code&gt; is its integration with the rest of the systemd ecosystem, making it easy to manage and configure. Don&amp;rsquo;t bother with &lt;code&gt;bind&lt;/code&gt; and &lt;code&gt;dnsmasq&lt;/code&gt; unless you have a specific reason to - &lt;code&gt;systemd-resolved&lt;/code&gt; is a solid choice for most users.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Troubleshooting DNS Resolution Issues in My Homelab with Unbound and systemd-resolved</title>
      <link>https://mrtomlinux.org/post/2026-06-06-troubleshooting-dns-resolution-issues-in-my-h/</link>
      <pubDate>Sat, 06 Jun 2026 09:40:24 +0200</pubDate>
      <guid>https://mrtomlinux.org/post/2026-06-06-troubleshooting-dns-resolution-issues-in-my-h/</guid>
      <description>&lt;h2 id=&#34;introduction-to-dns-resolution-issues&#34;&gt;Introduction to DNS Resolution Issues&lt;/h2&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve been running my own homelab for years, and like many of you, I&amp;rsquo;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&amp;rsquo;t all smooth sailing.&lt;/p&gt;</description>
    </item>
    <item>
      <title>DNS and DNS Servers for Linux</title>
      <link>https://mrtomlinux.org/post/dns/</link>
      <pubDate>Sun, 26 Jan 2025 00:00:00 +0000</pubDate>
      <guid>https://mrtomlinux.org/post/dns/</guid>
      <description>&lt;p&gt;The Domain Name System (DNS) is a fundamental component of the internet. It translates human-readable domain names like &lt;code&gt;example.com&lt;/code&gt; into IP addresses such as &lt;code&gt;93.184.216.34&lt;/code&gt;, 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.&lt;/p&gt;&#xA;&lt;h2 id=&#34;what-is-dns&#34;&gt;What is DNS?&lt;/h2&gt;&#xA;&lt;p&gt;DNS functions as the internet&amp;rsquo;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:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
