No Production Domain

Help
1

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<<- opcode: QUERY, status: NOERROR, id: 41973
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 5

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;2Runes.gg.			IN	NS

;; ANSWER SECTION:
2Runes.gg.		23351	IN	NS	ns1.vercel-dns.com.
2Runes.gg.		23351	IN	NS	ns2.vercel-dns.com.

;; ADDITIONAL SECTION:
ns1.vercel-dns.com.	53614	IN	A	198.51.44.13
ns2.vercel-dns.com.	53614	IN	A	198.51.45.13
ns1.vercel-dns.com.	53614	IN	AAAA	2620:4d:4000:6259:7:13:0:1
ns2.vercel-dns.com.	53614	IN	AAAA	2a00:edc0:6259:7:13::2

I noticed an issue during production deployments where the custom domain is not listed under domain for production deployments. So for some reason the domain is not being selected.

The project dashboard says No production Domain and gives me the option to add one. When I do so, in the domain list I see:

Project Settings > Domains
Project Settings > Domains1894Ă—1434 216 KB

I’ve tried disabling Auto-assign Custom Production Domains in the production environment configuration, and then manually promoting a deployment, but that didn’t change anything and the domain wasn’t selected.

Edit: Promoting a preview deployment was just assigned the branch. I think the issue has resolved itself. Will try to get production automation to assign the branch as well. If that works then I’ll close the issue.

2

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.

You can also use v0 to narrow down the possibilities.

3

let us know how it goes.

4

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.

5

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

6

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.

1 Like
7

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.