Authorization failed (error 400)

[digitalosaurus]

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. https://crt.sh/?q=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:
stinner-it.com
I ran this command:

It produced this output:
nvalid response from https://acme-v02.api.letsencrypt.org/acme/authz-v3/1811075927.

Details:

Type: urn:ietf:params:acme:error:dns

Status: 400

Detail: DNS problem: NXDOMAIN looking up TXT for _acme-challenge.stinner-it.com

My web server is (include version):
apache (dont know the version)
The operating system my web server runs on is (include version):
Plesk and CentOS 7.6.1810 (Core)
My hosting provider, if applicable, is:
A1
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):
Plesk
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot): dont apply

[JuergenAuer]

Hi @digitalosaurus

@digitalosaurus

My domain is:
stinner-it.com

checking your domain you have created the wrong entries - https://check-your-website.server-daten.de/?q=stinner-it.com#txt

You have created

_acme-challenge.stinner-it.com.stinner-it.com

so the menu you use adds stinner-it.com.

Create only two entries with

_acme-challenge
_acme-challenge.www

Compare it with

Your wrong marked entries should be empty.

[digitalosaurus]

Hi,
thank you for the quick response, but I tried again and got;

Invalid response from https://acme-v02.api.letsencrypt.org/acme/authz-v3/1811600342.

Details:

Type: urn:ietf:params:acme:error:dns

Status: 400

Detail: DNS problem: NXDOMAIN looking up TXT for _acme-challenge.stinner-it.com

I mean, I am worried because I could reissue an certificate some months ago, I wonder why it doesnt work this time?
BR

[JuergenAuer]

@digitalosaurus

Detail: DNS problem: NXDOMAIN looking up TXT for _acme-challenge.stinner-it.com

There is a newer check of your domain - https://check-your-website.server-daten.de/?q=stinner-it.com#txt

Now you have removed the wrong entries. So the three tested wrong entries are green.

But the correct domain names are empty -> nothing found.

ns15.domaincontrol.com is your name server you have to change, that's from GoDaddy.

Did you create the required entries manual? Is your Plesk able to talk with your GoDaddy name server?

How did you remove these wrong entries?