{"section":"known-issues","requestedLocale":"en","requestedSlug":"custom-domain-moved-between-faststore-projects-keeps-routing-to-the-previous-account","locale":"en","slug":"custom-domain-moved-between-faststore-projects-keeps-routing-to-the-previous-account","path":"docs/en/known-issues/FastStore/custom-domain-moved-between-faststore-projects-keeps-routing-to-the-previous-account.md","branch":"main","content":"## Summary\n\nWhen a custom domain is added to a FastStore project in WebOps and deployed to production, a domain-to-account mapping is created in the hosting infrastructure. Removing the domain from that project in WebOps does not delete this mapping. If the same domain is then added to a FastStore project from a different account and deployed, the existing mapping is kept instead of reassigned.\nAs a result, the domain keeps serving the storefront of the first project, although the WebOps settings, License Manager hosts, DNS, and `discovery.config.js` of the new project are all correctly configured. Redeploying either project and purging the CDN cache do not solve the issue.\n\n## Simulation\n\n1. Have two FastStore projects in WebOps, each linked to a different VTEX account (Account A and Account B).\n2. In the project of Account A, go to **WebOps > Settings > Domains**, add a custom domain (for example, `store.example.com`), and deploy to production.\n3. Remove `store.example.com` from the project of Account A.\n4. Make sure `store.example.com` is registered as a host only in Account B's License Manager, then add it to the project of Account B in **WebOps > Settings > Domains**.\n5. Deploy both projects to production.\n6. Go to `https://store.example.com`.\n\n\n**Expected behavior:** the domain serves the storefront of Account B.\n**Actual behavior:** the domain keeps serving the storefront of Account A.\n\n## Workaround\n\nThere is no workaround available on the customer side. Contact VTEX Support to have the domain mapping reassigned to the correct account."}