<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Unbound on Linux Café</title>
    <link>https://mrtomlinux.org/tags/unbound/</link>
    <description>Recent content in Unbound on Linux Café</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sat, 06 Jun 2026 09:40:24 +0200</lastBuildDate>
    <atom:link href="https://mrtomlinux.org/tags/unbound/index.xml" rel="self" type="application/rss+xml" />
    <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>
  </channel>
</rss>
