<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Infrastructure on PeteMahon.net</title><link>https://petemahon.net/tags/infrastructure/</link><description>Recent content in Infrastructure on PeteMahon.net</description><generator>Hugo</generator><language>en-us</language><copyright>&lt;a href="https://creativecommons.org/licenses/by-nc/4.0/" target="_blank" rel="noopener"&gt;CC BY-NC 4.0&lt;/a&gt;</copyright><lastBuildDate>Tue, 21 Apr 2026 10:00:00 +0400</lastBuildDate><atom:link href="https://petemahon.net/tags/infrastructure/index.xml" rel="self" type="application/rss+xml"/><item><title>Migrating My DNS to Cloudflare</title><link>https://petemahon.net/posts/migrating-dns-to-cloudflare/</link><pubDate>Tue, 21 Apr 2026 10:00:00 +0400</pubDate><guid>https://petemahon.net/posts/migrating-dns-to-cloudflare/</guid><description>&lt;p&gt;In &lt;a href="https://petemahon.net/posts/why-i-left-microsoft-365-for-proton/"&gt;the previous post&lt;/a&gt; I wrote about why I was leaving Microsoft 365. The first practical step was moving DNS off Microsoft&amp;rsquo;s infrastructure.&lt;/p&gt;
&lt;h2 id="why-cloudflare"&gt;Why Cloudflare&lt;/h2&gt;
&lt;p&gt;The specific trigger was licensing: once I stopped paying for M365, there was no guarantee Microsoft would keep hosting my DNS for free. I needed a provider I trusted to keep basic DNS free long-term, and Cloudflare has a strong track record on that front.&lt;/p&gt;
&lt;p&gt;Cloudflare has been my go-to for personal projects, going back years. Their free tier is compelling, and I was able to fashion my own dynamic DNS using their APIs to access my home lab remotely. Whilst I have since shifted my network to Tailscale, I still use Cloudflare for DNS hosting on other domains I own, CI/CD integrations, CDN, and Compute. To safely minimise the number of services I consume, Cloudflare was the natural choice for my DNS migration.&lt;/p&gt;</description></item></channel></rss>