I have set up a custom domain. The nameservers were set up and the domain points to an old deployment. dig ns 2runes.gg shows the name servers are correctly configured. geo@Geovanies-MBP ~ % dig ns 2Runes.gg ; <<>> DiG 9.10.6 <<>> ns 2Runes.gg ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<-…

Per support: This seems to be a known issue related to the Customer Environments feature. The solution is to set your domain to “No environment.” As soon as I did the interface picked up the custom domain. After redeploying the domain was correctly assigned and resolves as expected.

The domain troubleshooting guide can help with most custom domain configuration issues. You might be able to use that guide to solve it before a human is available to help you. Then you can come back here and share the answer for bonus points . [image] Troubleshooting domains Learn about…

I’m not sure what I did here to make it work originally. This is still assigning a generated domain to production deployments instead of my custom domain.

No Production Domain

Help

geovanie-ruiz (Geo) December 15, 2024, 2:45am 5

It appears I have the same issue as this person: Why my production URL is not my actual domain?

Topic		Replies	Views
Domain and URL not matching settings during productions deployment Help domains	3	78	February 16, 2025
Assigned domain not updating Help domains	3	91	March 8, 2025
Why my production URL is not my actual domain? Help domains	3	107	December 15, 2024
Need help with custom domain is not working Help domains	3	93	March 16, 2025
Custom domain setup issue Help nextjs , domains	4	154	August 7, 2024

No Production Domain

Related topics