<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Pihole on Shawn Sorichetti</title>
    <link>/tags/pihole/</link>
    <description>Recent content in Pihole on Shawn Sorichetti</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <managingEditor>me@ssoriche.com (Shawn Sorichetti)</managingEditor>
    <webMaster>me@ssoriche.com (Shawn Sorichetti)</webMaster>
    <copyright>© 2026 Shawn Sorichetti</copyright>
    <lastBuildDate>Wed, 15 Apr 2026 08:46:17 -0400</lastBuildDate><atom:link href="/tags/pihole/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>GL.iNet&#39;s AdGuard Home Hides Upstream DNS Settings in a Non-Obvious Place</title>
      <link>/til/glinet-adguard-upstream-dns/</link>
      <pubDate>Tue, 03 Mar 2026 00:00:00 +0000</pubDate>
      <author>me@ssoriche.com (Shawn Sorichetti)</author>
      <guid>/til/glinet-adguard-upstream-dns/</guid>
      <description>&lt;p&gt;On a recent trip I kept getting connection failures that needed retrying — pages half-loading, API calls timing out, the usual DNS-smells-wrong experience. It was intermittent enough to be annoying but consistent enough that I knew something was actually broken.&lt;/p&gt;&#xA;&lt;p&gt;I narrowed it down to DNS pretty quickly. My &lt;a href=&#34;https://www.gl-inet.com/products/gl-mt3000/&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34;&gt;GL.iNet MT-3000&lt;/a&gt; travel router was dropping queries or returning nothing for some domains.&lt;/p&gt;&#xA;&lt;p&gt;The culprit turned out to be obvious in retrospect: before leaving I had shut down my &lt;a href=&#34;https://pi-hole.net&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34;&gt;Pi-hole&lt;/a&gt; servers at home. Those Pi-holes live on my &lt;a href=&#34;https://tailscale.com&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34;&gt;Tailscale&lt;/a&gt; network, and my travel router connects back to that network. Somewhere, something was still trying to use them for DNS.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
