Certbot failed to authenticate some domains (authenticator: nginx)

[humaisawan]

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:
coachmastersports.com
I ran this command:
sudo certbot --nginx -d coachmastersports.com
It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Requesting a certificate for coachmastersports.com

Certbot failed to authenticate some domains (authenticator: nginx). The Certificate Authority reported these problems:
Domain: coachmastersports.com
Type: dns
Detail: DNS problem: NXDOMAIN looking up A for coachmastersports.com - check that a DNS record exists for this domain; DNS problem: NXDOMAIN looking up AAAA for coachmastersports.com - check that a DNS record exists for this domain

Hint: The Certificate Authority failed to verify the temporary nginx configuration changes made by Certbot. Ensure the listed domains point to this nginx server and that it is accessible from the internet.

Some challenges have failed.

My web server is (include version): Ngnix

The operating system my web server runs on is (include version): Ubuntu

My hosting provider, if applicable, is: Domain bought from raidboxes and I am using Amzone Route 53 to create records for it.
NOTE: I added the NS nameservers provided by Aws route 53 in the dns management of my raidboxes dashboard.

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): 2.9.0

Please ask if there is any more information that you need.

[Osiris]

@humaisawan

NOTE: I added the NS nameservers provided by Aws route 53 in the dns management of my raidboxes dashboard.

It looks like the .com. zone DNS servers are not (yet?) aware of this. See e.g.:

https://dnsviz.net/d/coachmastersports.com/dnssec/

In fact, the .com. zone doesn't even "know" your domain name, as it responds with a NSEC3 RR.

Maybe it just takes some time for the .com. zone to get updated, I dunno The domain is fairly new, registered at 2024-04-02T00:24:42Z. That said, we're 24 hours further already..

Anyway, currently not a Let's Encrypt/ACME issue, but a DNS issue. Try again once DNS is fixed

[humaisawan]

This is the image from my raidboxes(where i purchased the domain) dashbaord. It says that the domain is active

[Osiris]

In the whois and rdap info it's active indeed, but still, the .com. DNS servers are not aware of your domain. I don't know how to help you with that. As I said, maybe you just need to wait a little bit longer. Or maybe you need to talk with your DNS registar/provider and ask them about it.