<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Geodns on Pi Stack</title><link>https://www.pistack.xyz/tags/geodns/</link><description>Recent content in Geodns on Pi Stack</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 19 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.pistack.xyz/tags/geodns/index.xml" rel="self" type="application/rss+xml"/><item><title>PowerDNS vs BIND9 vs CoreDNS: Self-Hosted GeoDNS Routing Guide 2026</title><link>https://www.pistack.xyz/posts/2026-04-19-powerdns-vs-bind9-vs-coredns-self-hosted-geodns-routing-guide-2026/</link><pubDate>Sun, 19 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.pistack.xyz/posts/2026-04-19-powerdns-vs-bind9-vs-coredns-self-hosted-geodns-routing-guide-2026/</guid><description>&lt;p>When you run services across multiple data centers or cloud regions, getting users to the nearest endpoint matters. Every extra hop adds latency, and a user in Tokyo hitting your US East server can easily see 150-200ms of unnecessary round-trip time. Geographic DNS — or GeoDNS — solves this at the DNS layer by returning different IP addresses based on where the query originates.&lt;/p></description></item></channel></rss>