<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>DNS on lamjan</title>
    <link>https://lamjan.com/tags/dns/</link>
    <description>Recent content in DNS on lamjan</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 22 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://lamjan.com/tags/dns/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The Ultimate Guide to M365 Custom Domains: Automatic, Manual, and NS Paths</title>
      <link>https://lamjan.com/posts/custom-domain-m365/</link>
      <pubDate>Fri, 22 May 2026 00:00:00 +0000</pubDate>
      <guid>https://lamjan.com/posts/custom-domain-m365/</guid>
      <description>&lt;p&gt;Nobody wants to use that long company.onmicrosoft.com address for official business emails. It looks temporary and unprofessional. Mapping your actual custom domain to Microsoft 365 is the very first thing you should do, but if your DNS is not correct, your emails will just be bouncing.&lt;/p&gt;
&lt;p&gt;Depending on where your domain is hosted, Microsoft offers three different setup paths. Let us break them down directly so you can deploy cleanly without any issues.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
