<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Dnsmasq on Linux Café</title>
    <link>https://mrtomlinux.org/tags/dnsmasq/</link>
    <description>Recent content in Dnsmasq 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/dnsmasq/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>
  </channel>
</rss>
