Certbot renew suddenly failing DNS looking for AAAA

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:

host146.technologists.com
host146.vidconf.net

mail.technologists.com
mail.vidconf.net

ns.technologists.com
ns.vidconf.net

I ran this command: certbot -v renew

It produced this output:
[root@mail ~]# certbot -v renew
Saving debug log to /var/log/letsencrypt/letsencrypt.log


Processing /etc/letsencrypt/renewal/host146.kaybuena.com.conf


Certificate is due for renewal, auto-renewing...
Plugins selected: Authenticator apache, Installer apache
Renewing an existing certificate for host146.kaybuena.com and 8 more domains
Performing the following challenges:
http-01 challenge for host146.vidconf.net
http-01 challenge for mail.vidconf.net
http-01 challenge for ns.vidconf.net
Waiting for verification...
Challenge failed for domain host146.vidconf.net
Challenge failed for domain ns.vidconf.net
Challenge failed for domain mail.vidconf.net
http-01 challenge for host146.vidconf.net
http-01 challenge for ns.vidconf.net
http-01 challenge for mail.vidconf.net

Certbot failed to authenticate some domains (authenticator: apache). The Certificate Authority reported these problems:
Domain: host146.vidconf.net
Type: dns
Detail: DNS problem: looking up A for host146.vidconf.net: DNSSEC: Bogus; DNS problem: looking up AAAA for host146.vidconf.net: DNSSEC: Bogus

Domain: ns.vidconf.net
Type: dns
Detail: DNS problem: looking up A for ns.vidconf.net: DNSSEC: Bogus; DNS problem: looking up AAAA for ns.vidconf.net: DNSSEC: Bogus

Domain: mail.vidconf.net
Type: dns
Detail: DNS problem: looking up A for mail.vidconf.net: DNSSEC: Bogus; DNS problem: looking up AAAA for mail.vidconf.net: DNSSEC: Bogus

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

Cleaning up challenges
Failed to renew certificate host146.kaybuena.com with error: Some challenges have failed.


All renewals failed. The following certificates could not be renewed:
/etc/letsencrypt/live/host146.kaybuena.com/fullchain.pem (failure)


1 renew failure(s), 0 parse failure(s)
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.
[root@mail ~]#

My web server is (include version):
Server version: Apache/2.4.58 (Fedora Linux)
Server built: Oct 20 2023 00:00:00

The operating system my web server runs on is (include version): 6.7.10-200.fc39.x86_64

My hosting provider, if applicable, is: self, static IPV4 from Spectrum, no IPV6

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

You will need to fix the DNSSEC on every domain that includes that status.

You may find DNSviz useful.

https://dnsviz.net/

3 Likes

thanks. I'm very puzzled about how this got broken, it hadn't changed in over a year, so I will have to remember how everything worked and figure out how it should work

1 Like

not true. I had tried to switch to Cloudflare and forgot. Reverted.

1 Like

You need to disable DNSSEC prior to moving DNS to Cloudflare. Once the zone is active on Cloudflare you can re-enable DNSSEC by updating your registrar with your DNSSEC components.

4 Likes