DNS problem: NXDOMAIN looking up TXT for _acme-challenge.wetesty8.net - check that a DNS record exists for this domain

Hi,
I have a working installation for the domain wetesty.net I can renew the certificate and it works fine.
We created a new domain wetesty8.net and wanted to generate a cert as well.
I copied the contents of the directory /root/letsencrypt/* used when running a renew for wetesty.net to directory /8/ - see below the command I ran - haven't changed anything there - not sure if this is the way to add new domain to certbot don't want to break the working installation.
I was not involved in the initial setup for the wetesty.net domain so not sure what I'm missing.

I read a few threads related to similar errors but I'm not sure how to create this _acme* domain and where or should it be created automatically somehow during some step I missed.
I tried running the command used to renew wetesty.net and added new domain wetesty8.net but the result was the same.

I know the _acme* domain is missing but I also do not see it in our account in aws nor a different one so not sure how to proceed.

Please help :slight_smile:

My domain is:
wetesty8.net

I ran this command:
/snap/bin/certbot certonly -d wetesty8.net -d *.wetesty8.net --dns-route53 --logs-dir /root/letsencrypt/8/log/ --config-dir /root/letsencrypt/8/config/ --work-dir /root/letsencrypt/8/work/ -m asconx@gmail.com --agree-tos --server https://acme-v02.api.letsencrypt.org/directory

It produced this output:
Certbot failed to authenticate some domains (authenticator: dns-route53). The Certificate Authority reported these problems:
Domain: wetesty8.net
Type: dns
Detail: DNS problem: NXDOMAIN looking up TXT for _acme-challenge.wetesty8.net - check that a DNS record exists for this domain

Domain: wetesty8.net
Type: dns
Detail: DNS problem: NXDOMAIN looking up TXT for _acme-challenge.wetesty8.net - check that a DNS record exists for this domain

My web server is (include version):
not relevant

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

My hosting provider, if applicable, is:
colocated server

I can login to a root shell on my machine (yes or no, or I don't know):
yes

I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
no

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

Found the problem|
I created a hosted zone in aws before I registered the domain
when i created the domain new hosted zone with the same name was created.
I removed the one created by me added A, CNAME record to the one created automatically and it worked

2 Likes

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