[deleted]

Comments

• Atherel@lemmy.dbzer0.com ⁨1⁩ ⁨week⁩ ago

  Which test are you running exactly?
  Two things I would check:
  Resolvers configured in PiHole
  Check using browser with DNS over HTTPS instead of the system configuration

  source
• Decronym@lemmy.decronym.xyz ⁨1⁩ ⁨week⁩ ago

  Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:

  Fewer Letters	More Letters
  DNS	Domain Name Service/System
  HTTP	Hypertext Transfer Protocol, the Web
  HTTPS	HTTP over SSL
  PiHole	Network-wide ad-blocker (DNS sinkhole)
  SSL	Secure Sockets Layer, for transparent encryption
  VPS	Virtual Private Server (opposed to shared hosting)

  ---

  [Thread #1012 for this comm, first seen 21st Jan 2026, 02:55] [FAQ] [Full list] [Contact] [Source code]

  source
• stratself@lemdro.id ⁨1⁩ ⁨week⁩ ago

  In your Tailscale DNS panel, disable “Use with exit node” option for your nameservers.

  When turned on, that option actually allows you to talk directly to nameservers without tunneling DNS queries through the exit node. Since Quad9 in fact has a worldwide CDN, this would leak your (general) DNS query location.

  I believe Tailscale send the queries in parallel and fetch the faster response, which is Quad9 in this case. Ideally for your use case, all your queries should be able to reach and show up in Pi-hole’s logs. Use tailscale dns commands for further debugging

  source
• just_another_person@lemmy.world ⁨1⁩ ⁨week⁩ ago

  Need more details about how you’re running this test.

  source