<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Raspberrypi on Linux Café</title>
    <link>https://mrtomlinux.org/tags/raspberrypi/</link>
    <description>Recent content in Raspberrypi on Linux Café</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Wed, 28 Oct 2026 11:13:18 +0200</lastBuildDate>
    <atom:link href="https://mrtomlinux.org/tags/raspberrypi/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Fixing the 2‑second DNS lookup lag on my Pi by tweaking resolvectl and systemd‑resolved cache</title>
      <link>https://mrtomlinux.org/post/2026-10-28-fixing-the-2second-dns-lookup-lag-on-my-pi-by/</link>
      <pubDate>Wed, 28 Oct 2026 11:13:18 +0200</pubDate>
      <guid>https://mrtomlinux.org/post/2026-10-28-fixing-the-2second-dns-lookup-lag-on-my-pi-by/</guid>
      <description>&lt;h2 id=&#34;the-2second-dns-lookup-lag-on-a-pi--a-handson-fix&#34;&gt;The 2‑second DNS lookup lag on a Pi – a hands‑on fix&lt;/h2&gt;&#xA;&lt;p&gt;I was running a Pi‑4‑based home‑lab that hosts a few services: a personal Git server, a small reverse‑proxy stack, and a few IoT sensors that ping the Pi every few seconds. Every time I pinged a domain that wasn’t in the local cache, I noticed a ~2 s pause before the first packet left the network interface. On a desktop that latency was negligible, but on the Pi it was a noticeable hiccup that made the sensor logs look a little jittery.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
