<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Anycast on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/anycast/</link>
    <description>Recent content in Anycast on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 22 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/anycast/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>BIRD vs FRRouting vs Keepalived: Self-Hosted DNS Anycast Routing Guide 2026</title>
      <link>https://www.pistack.xyz/posts/2026-04-22-bird-vs-frrouting-vs-keepalived-self-hosted-dns-anycast-guide-2026/</link>
      <pubDate>Wed, 22 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-04-22-bird-vs-frrouting-vs-keepalived-self-hosted-dns-anycast-guide-2026/</guid>
      <description>&lt;p&gt;DNS anycast is one of the most powerful yet underutilized techniques for building resilient, low-latency infrastructure. By advertising the same IP address from multiple locations, anycast ensures that DNS queries are automatically routed to the nearest healthy server — no load balancer, no geo-DNS provider, no SaaS dependency required.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
