<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Custom-Domain on PeteMahon.net</title><link>https://petemahon.net/tags/custom-domain/</link><description>Recent content in Custom-Domain 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 17:00:00 +0400</lastBuildDate><atom:link href="https://petemahon.net/tags/custom-domain/index.xml" rel="self" type="application/rss+xml"/><item><title>Proton Mail on a Custom Domain: Aliases, Catch-all, and Migrating Your Inbox</title><link>https://petemahon.net/posts/proton-mail-custom-domain/</link><pubDate>Tue, 21 Apr 2026 17:00:00 +0400</pubDate><guid>https://petemahon.net/posts/proton-mail-custom-domain/</guid><description>&lt;p&gt;This is part 3 of a series on moving a personal domain from Microsoft 365 to Proton. &lt;a href="https://petemahon.net/posts/why-i-left-microsoft-365-for-proton/"&gt;Post 1&lt;/a&gt; covered the why, and &lt;a href="https://petemahon.net/posts/migrating-dns-to-cloudflare/"&gt;post 2&lt;/a&gt; moved DNS to Cloudflare. This post is the heart of the migration — getting Proton Mail working on a custom domain, understanding how Proton&amp;rsquo;s address model differs from what you&amp;rsquo;re used to, and getting your DNS records right so mail delivery is trusted.&lt;/p&gt;
&lt;p&gt;If you&amp;rsquo;ve landed here straight from a search engine, the earlier posts aren&amp;rsquo;t prerequisites — you can follow this one standalone, provided you already control your DNS somewhere that lets you add TXT and MX records.&lt;/p&gt;</description></item></channel></rss>