<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Bird on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/bird/</link>
    <description>Recent content in Bird on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 16 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/bird/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted DNS Anycast Health Checking: anycast-healthchecker vs BIRD vs Keepalived</title>
      <link>https://www.pistack.xyz/posts/2026-05-16-self-hosted-dns-anycast-health-checking-bird-keepalived-guide/</link>
      <pubDate>Sat, 16 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-16-self-hosted-dns-anycast-health-checking-bird-keepalived-guide/</guid>
      <description>&lt;p&gt;DNS Anycast is the standard approach for running highly available, geographically distributed DNS services. By advertising the same IP address from multiple locations via BGP, clients are automatically routed to the nearest available DNS server. But what happens when one of those servers goes down? Without health checking, BGP continues advertising the anycast IP from a failed node, sending queries into a black hole.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
