Title: Hi, I just saw this tweet[^1] by @QuinnyPig that mentions accessing your Pi-hole while traveling thanks to TailScale and wondered how to deploy Pi-hole at the edge, instead of a home lab, for improved latency.<p>My simple solution involves running it on Fly.io to make it easy to relocate anywhere, and embedding tailscale into the same firecracker VM (né docker container) to keep the infra dead simple and cheap.<p>Naively deploying a publicly accessible DNS resolver is not ideal[^2] so the main constraint was to secure the VM by 1) keeping all public ports closed and 2) having Pi-hole listen only on the private network interface created by TailScale.<p>It&#x27;s all very straightforward but it&#x27;s noticeably improved my bandwidth usage and page loading times across my laptop and mobile phone, so I figured I&#x27;d share. Suggestions for improvement are also welcome!<p>[^1]: <a href="https:&#x2F;&#x2F;twitter.com&#x2F;QuinnyPig&#x2F;status&#x2F;1558521941538983936" rel="nofollow">https:&#x2F;&#x2F;twitter.com&#x2F;QuinnyPig&#x2F;status&#x2F;1558521941538983936</a><p>[^2]: <a href="https:&#x2F;&#x2F;www.cloudflare.com&#x2F;learning&#x2F;ddos&#x2F;dns-amplification-ddos-attack&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.cloudflare.com&#x2F;learning&#x2F;ddos&#x2F;dns-amplification-d...</a>
Upvote: