<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Systemd-Resolved on Il blog di Damien Dye</title>
    <link>https://blogs.damiendye.uk/it/tags/systemd-resolved/</link>
    <description>Recent content in Systemd-Resolved on Il blog di Damien Dye</description>
    <generator>Hugo</generator>
    <language>it-IT</language>
    <lastBuildDate>Sun, 27 Sep 2026 09:00:00 +0100</lastBuildDate>
    <atom:link href="https://blogs.damiendye.uk/it/tags/systemd-resolved/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Resolved: il resolver che stai già usando</title>
      <link>https://blogs.damiendye.uk/it/dns/resolved-the-resolver-you-are-already-running/</link>
      <pubDate>Sun, 27 Sep 2026 09:00:00 +0100</pubDate>
      <guid>https://blogs.damiendye.uk/it/dns/resolved-the-resolver-you-are-already-running/</guid>
      <description>systemd-resolved gira sulla maggior parte dei desktop Linux: mette in cache ogni ricerca e non ne convalida nessuna. Cosa fa lo stub su 127.0.0.53, la cache misurata, come attivare DNSSEC, perché DNS over TLS funziona e DNS over HTTPS non esiste, cosa installano Fedora, Ubuntu, Debian e RHEL, e perché una build su misura non serve.</description>
    </item>
  </channel>
</rss>
