Cannot DNS record change could not enough timeout for _acme-challange.x.company.com

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 issue is when I add the _acme-challenge.ap.company.com. to my DNS server (this is IPAM tool).. it has always expired timout.. Who can help me
My domain is:

I ran this command:
sudo certbot certonly --manual --preferred-challenges=dns --email so@company.com --server https://acme-v02.api.letsencrypt.org/directory --agree-tos -d app.company.com -d *.ap.company.com -v

It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator manual, Installer None
Requesting a certificate for ap.company.com and *.ap.company.com
Performing the following challenges:
dns-01 challenge for ap.company.com
dns-01 challenge for ap.company.com


Please deploy a DNS TXT record under the name:

_acme-challenge.ap.company.com.

with the following value:

lGQ_cW5hoOTbTrjfkmfsyzZmId2urto8kFFSmInF5i0Ztw


Press Enter to Continue^CCleaning up challenges

My web server is (include version):

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

My hosting provider, if applicable, is:

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

I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
I am configuring Load balance for the company applications..
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): certbot 3.1.0

I don't see any such DNS record.

Is company.com really your domain?

1 Like

Good morning ,
It is not our real company name. is it really necessary ? the issue TTL period. When I change from IPAM , command prompts already expired

From the questionnaire:

Also, what's the exact error from the ACME server? In your post there was a Ctrl-C before anything is when shown.

Or is it Certbot that's timing out?

1 Like

That domain name is valid and belongs to someone else. Please don't use other people's domain names in examples.

Use example.com if you must. But, debugging DNS query problems is very difficult without an actual domain name. And, without seeing the actual error we don't have much to work with. Well, without either we don't have anything to work with :slight_smile:

3 Likes

hello , finally i update domain but I took this error :

Press Enter to Continue
Waiting for verification...
Challenge failed for domain app.example.com
dns-01 challenge for app.example.com

Certbot failed to authenticate some domains (authenticator: manual). The Certificate Authority reported these problems:
Domain: app.example.com
Type: unauthorized
Detail: Incorrect TXT record "AeHoCzBEInK7qSCoVCZh4vLh6ecreDVV-nCHmb3_p3g" found at _acme-challenge.app.example.com

Hint: The Certificate Authority failed to verify the manually created DNS TXT records. Ensure that you created these in the correct location, or try waiting longer for DNS propagation on the next attempt.

Cleaning up challenges
Some challenges have failed.

_acme-challenge.app.example.com
Server: dns.google
Address: 8.8.8.8

_acme-challenge.app.example.com text =

    "AeHoCzBEInK7qSCoVCZh4vLh6ecreDVV-nCHmb3_p3g"

Note the error says "incorrect TXT record". Which you confirm below

It will be difficult to say specific things without your actual domain name.

But, you are using the Manual method so be sure the TXT record value you are shown has sync'd worldwide at your DNS provider. Usually this only takes a minute or so but some may take much longer.

Use a tool like this to check in a similar way to Let's Encrypt: https://unboundtest.com

Sometimes problems in DNS delegation cause this problem. Make sure yours is correct with a tool like: https://dnsviz.net

If you want more detailed help you will need to provide your actual domain name

2 Likes

If you tried and aborted the process, you may have left behind old ACME DNS records. I suggest you clear any such entries off your zone before you attempt to run it with extended delay for the zones to be published and propagated. Also worth noting LE always reaches my secondary and never my primary DNS server - unsure if I'm that lucky or it is by design, so aside of the IPAM record publication, you also need to account for the zone synchronization while setting up your timeout. If using certbot with DNS RFC2136 hook (recommended for ISC BIND based setups), refer to its parameters, of importance the "--dns-rfc-2136-propagation-seconds" to increase it accordingly.

Edit: I see you are using manual DNS, so before you press continue, make sure you can query the _acme-challenge record at all your DNS servers.

For DNS validation when you create/update a TXT record you need to wait long enough for the changes to be copied to all of your domains nameservers before proceeding, normally that's a minute but it can be up to 5 minutes, then resume your certificate order. TTL settings don't matter because Let's Encrypt is looking at your primary nameservers not cached stuff like 8.8.8.8

Manual DNS validation is very error prone (and are not automated) and you should ideally use an automated DNS plugin where possible.