<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Posts on dúndns</title>
    <link>https://blog.dundns.eu/posts/</link>
    <description>Recent content in Posts on dúndns</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 28 Jul 2026 09:30:00 +0000</lastBuildDate>
    <atom:link href="https://blog.dundns.eu/posts/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How a device finds encrypted DNS by itself</title>
      <link>https://blog.dundns.eu/posts/ddr-encrypted-dns-discovery/</link>
      <pubDate>Tue, 28 Jul 2026 09:30:00 +0000</pubDate>
      <guid>https://blog.dundns.eu/posts/ddr-encrypted-dns-discovery/</guid>
      <description>&lt;p&gt;A device is normally configured with a single IP address for its DNS resolver. That address reaches the resolver over plain, unencrypted DNS, which is all a bare IP address can describe. Encrypted DNS requires more: a hostname to check the certificate against, a port, and a protocol. None of that fits in the settings box, and none of it can be worked out from the address already sitting there.&lt;/p&gt;</description>
    </item>
    <item>
      <title>DoH, DoT, DoQ, DoH3, and ODoH: which one should you use?</title>
      <link>https://blog.dundns.eu/posts/doh-dot-doq-odoh-explained/</link>
      <pubDate>Sun, 26 Jul 2026 09:30:00 +0000</pubDate>
      <guid>https://blog.dundns.eu/posts/doh-dot-doq-odoh-explained/</guid>
      <description>&lt;p&gt;Every time you open a website, your device first asks a DNS resolver where to find it. Without encryption that question travels in the clear, readable by your internet provider, by the café Wi-Fi, and by everyone else handling the traffic along the way. Taken together, those questions are a running list of every site you visit.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
