<?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 Daniel &#39;f0o&#39; Preussker</title>
    <link>https://f0o.dev/tags/anycast/</link>
    <description>Recent content in Anycast on Daniel &#39;f0o&#39; Preussker</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 27 Jul 2025 12:00:00 +0000</lastBuildDate><atom:link href="https://f0o.dev/tags/anycast/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Building an anycast authoritative DNS infrastructure for funsies</title>
      <link>https://f0o.dev/posts/2025/07/building-an-anycast-authoritative-dns-infrastructure-for-funsies/</link>
      <pubDate>Sun, 27 Jul 2025 12:00:00 +0000</pubDate>
      
      <guid>https://f0o.dev/posts/2025/07/building-an-anycast-authoritative-dns-infrastructure-for-funsies/</guid>
      <description>&lt;p&gt;It&amp;rsquo;s been some time since I wrote something, and frankly, I blame DNS.&lt;/p&gt;
&lt;p&gt;Always blame DNS, right? It&amp;rsquo;s the silent killer of Friday afternoons and the invisible glue holding this fragile house of cards we call the internet together.&lt;/p&gt;
&lt;p&gt;But what if you didn&amp;rsquo;t just consume DNS? What if you actually &lt;em&gt;owned&lt;/em&gt; your entire DNS infrastructure?&lt;/p&gt;
&lt;h3 id=&#34;why-do-this-to-yourself&#34;&gt;Why do this to yourself?&lt;/h3&gt;
&lt;p&gt;Historically, running your own authoritative DNS was a nightmare reserved for masochists.&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
