<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Can the same custom domain be configured on two FusionAuth Cloud deployments simultaneously?]]></title><description><![CDATA[<p dir="auto">I need to migrate a custom domain from one FusionAuth Cloud deployment to another. Currently, the custom domain is configured on a production deployment, and I want to transition it to a development deployment.</p>
<p dir="auto">My intended migration approach is:</p>
<ol>
<li>Configure and validate the custom domain and certificate on the dev deployment</li>
<li>Update DNS to point the domain to the dev deployment</li>
<li>Test and validate everything works correctly</li>
<li>Remove the custom domain from the production deployment</li>
</ol>
<p dir="auto">My questions:</p>
<ul>
<li>Can I configure the same custom domain on both FusionAuth Cloud deployments simultaneously?</li>
<li>Are there any conflicts with certificate validation or provisioning when the same domain is on two deployments at once?</li>
<li>Is this migration approach supported, or is there a recommended sequence to avoid certificate validation issues?</li>
</ul>
]]></description><link>https://fusionauth.io/community/forum/topic/3176/can-the-same-custom-domain-be-configured-on-two-fusionauth-cloud-deployments-simultaneously</link><generator>RSS for Node</generator><lastBuildDate>Thu, 01 Oct 2026 07:44:30 GMT</lastBuildDate><atom:link href="https://fusionauth.io/community/forum/topic/3176.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 30 Sep 2026 19:45:02 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Can the same custom domain be configured on two FusionAuth Cloud deployments simultaneously? on Wed, 30 Sep 2026 19:45:13 GMT]]></title><description><![CDATA[<p dir="auto"><strong>No, you cannot configure the same custom domain on two different FusionAuth Cloud deployments at the same time.</strong></p>
<p dir="auto">The recommended migration sequence is:</p>
<ol>
<li><strong>Remove</strong> the custom domain from the production deployment</li>
<li><strong>Configure</strong> the custom domain on the dev deployment</li>
<li><strong>Configure a CNAME record</strong> pointing your custom domain directly to the dev deployment's durable hostname</li>
<li><strong>Validate the certificate</strong> for the domain on the dev deployment</li>
</ol>
<h2>Important Considerations</h2>
<p dir="auto"><strong>DNS Propagation Time</strong></p>
<ul>
<li>DNS changes take time to propagate</li>
<li>Expect up to 30 minutes for DNS servers to recognize the changes</li>
<li>Propagation may take longer depending on your DNS TTL settings</li>
<li>Plan for this downtime window during your migration</li>
</ul>
<p dir="auto"><strong>Certificate Validation</strong></p>
<ul>
<li>Certificate validation uses DNS-based methods</li>
<li>You must complete the DNS configuration before certificate validation can succeed</li>
</ul>
<p dir="auto">To minimize downtime, prepare all configurations on the dev deployment beforehand, then execute the domain removal, DNS update, and certificate validation in quick succession.</p>
]]></description><link>https://fusionauth.io/community/forum/post/8689</link><guid isPermaLink="true">https://fusionauth.io/community/forum/post/8689</guid><dc:creator><![CDATA[FASupportBot]]></dc:creator><pubDate>Wed, 30 Sep 2026 19:45:13 GMT</pubDate></item></channel></rss>