Payload Cloud: No DNS Record generated for Custom Domain

[iron barn]

After adding my domain name, Payload Cloud does not appear to generate a DNS record. I get an empty table.

I have tried deleting and adding multiple times, but it still doesn't work. Kindly help.

Project Id: 664e26139dd26c2ec53747eb

[icy isle]

New Community-Help Thread Created!

Help is on the way! To mark it as solved, use the /solve command. In the meantime, here are some existing threads that may help you:

Documentation:

• Cloud Projects - Custom Domains
• Cloud Projects - Email
• GraphQL Schema - Custom Field Schemas - Adding an NPM script
• Project Configuration - Select your plan
• Project Configuration - Payment

[snow veldt]

Hey @iron barn I will look into this.

[iron barn]

Any Update? @snow veldt

[snow veldt]

Should be all set

The values should now show in your interface

[proper osprey]

@snow veldt Hi, hope you are well. I tried adding custom domain to my project but the dns records are empty, project id is:6740520d018da8a6a1c6d978

[snow veldt]

Sure, I'll be able to take a look soon

[snow veldt]

You should be all set. We're looking into our DNS provisioning to prevent issues like this in the future.

[full niche]

hey @snow veldt I'm also having the same issue (empty DNS for custom domain) and would appreciate help!
project id: 673e5e6b322082258e963eae

[snow veldt]

Okay, let me take a look 👀

[full niche]

Do you happen to know how long it should take for Cloudflare ERR_SSL_VERSION_OR_CIPHER_MISMATCH error to resolve after switching the DNS settings?

[snow veldt]

You're talking about one of your custom domains, correct?

[snow veldt]

You should be all set. The custom domains now load properly.

We're working on a fix to prevent this sort of scenario in the future.

[full niche]

Yes, we tried to swap it yesterday, and it was showing an error for 10+ minutes, so I reverted

Thank you for the quick resolution!

Here was the page for reference

[proper osprey]

@snow veldt sorry to disturb you again, but how can we resolve this issue from our end(if possible) because i am planning to use payloadcms as base for most of my website projects and this issue again came for the 2nd project as well

[snow veldt]

Project ID?

As of now, this can only be resolved on our end

[proper osprey]

67474627d6ef513d753fd093

[proper osprey]

oh okay

[snow veldt]

Both records appear to be resolving properly, despite the records not showing correctly in your dashboard

I'll get this over to someone to get that resolved.

[proper osprey]

sure, thanks

[clever sandal]

@snow veldt Hello, we're having an issue that seems similar to this. We were seeing a cipher mismatch error, so we tried removing our custom domain and re-adding it. Now we're unable to get the DNS records to appear after adding a custom domain. The project ID is: 65ea17b351652515b4566fee

[snow veldt]

Redeploying, then you should be all set

[clever sandal]

thanks @snow veldt -- I was able to get the DNS records to show up and add them to my DNS, however, I'm seeing an error within chrome

ERR_SSL_VERSION_OR_CIPHER_MISMATCH

Is this an issue with the SSL cert being generated by Payload?

when I added a brand new domain (the one ending in .app), it works perfectly. But my old domain .com is showing the error.

would you be able to reissue our cert for the .com domain attached to that project?

[snow veldt]

Let me DM you

[mental flower]

Hey, I am having the same issue, project id: 6750765897483ea9ca9744f1

[snow veldt]

I'm able to see your application URL without issue. Are you still experiencing this?

[noble moon]

Hi there, same issue; 678d042c0c526f0165f707e0

[frozen belfry]

Having the same issue

[dusty stump]

@snow veldt

[smoky perch]

I am also seeing the same error, I've followed the steps outlined in the custom domain docs - set the serverURL setting to my custom domain on https - set the apex A record in route53 for the domain to the IP address provided by the payload UI. Im getting ERR_SSL_VERSION_OR_CIPHER_MISMATCH

project id : 679cb0f5dca2f3178d3bc2b9

[smoky perch]

Ok I've fixed the issue by changing the NEXT_PUBLIC_SERVER_URL env var as well to the custom domain, but now all of our images urls have the old domain xxxx.payloadcms.app and the new domain as well before the /api/media.... part