Certificate creation using certbot and route53 fails

[ALFAGAGA]

Starting yesterday, 03.06.2024 I can no longer issue new certificates using certbot and having my domain hosted on AWS Route53. The domain has DNSSEC configured to "not signing". I am certain this has worked on 31.05.2024

My domain is: i-05b3c67ca68a810b1.sandbox.devl.awhap.hev.cloud

I ran this command:
certbot certonly --dns-route53 -d i-05b3c67ca68a810b1.sandbox.devl.awhap.hev.cloud -d *.i-05b3c67ca68a810b1.sandbox.devl.awhap.hev.cloud -n --agree-tos --email hap@helvetia.ch

It produced this output:

Saving debug log to /var/log/letsencrypt/letsencrypt.log
Found credentials from IAM Role: <redacted, it is the correct IAM Role with correct permissions>
Plugins selected: Authenticator dns-route53, Installer None
Requesting a certificate for i-05b3c67ca68a810b1.sandbox.devl.awhap.hev.cloud and *.i-05b3c67ca68a810b1.sandbox.devl.awhap.hev.cloud
Performing the following challenges:
dns-01 challenge for i-05b3c67ca68a810b1.sandbox.devl.awhap.hev.cloud
dns-01 challenge for i-05b3c67ca68a810b1.sandbox.devl.awhap.hev.cloud
Waiting for verification...
Challenge failed for domain i-05b3c67ca68a810b1.sandbox.devl.awhap.hev.cloud
Challenge failed for domain i-05b3c67ca68a810b1.sandbox.devl.awhap.hev.cloud
dns-01 challenge for i-05b3c67ca68a810b1.sandbox.devl.awhap.hev.cloud
dns-01 challenge for i-05b3c67ca68a810b1.sandbox.devl.awhap.hev.cloud

Certbot failed to authenticate some domains (authenticator: dns-route53). The Certificate Authority reported these problems:
  Domain: i-05b3c67ca68a810b1.sandbox.devl.awhap.hev.cloud
  Type:   dns
  Detail: DNS problem: looking up TXT for _acme-challenge.i-05b3c67ca68a810b1.sandbox.devl.awhap.hev.cloud: DNSSEC: DNSKEY Missing

  Domain: i-05b3c67ca68a810b1.sandbox.devl.awhap.hev.cloud
  Type:   dns
  Detail: DNS problem: looking up TXT for _acme-challenge.i-05b3c67ca68a810b1.sandbox.devl.awhap.hev.cloud: DNSSEC: DNSKEY Missing

Hint: The Certificate Authority failed to verify the DNS TXT records created by --dns-route53. Ensure the above domains have their DNS hosted by AWS Route53.

Cleaning up challenges
Some challenges have failed.

My web server is (include version): traefik

The operating system my web server runs on is (include version): UBI9 (traefik runs inside a docker container, the issue doesn't really reach that point)

My hosting provider, if applicable, is: not applicable

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.10.0

[ALFAGAGA]

For further details, this is the log file that certbot produced when running the command.
certbot_log.txt (204.0 KB)

[petercooperjr]

@ALFAGAGA

The domain has DNSSEC configured to "not signing".

Yes, it's not signing, but the domain is still configured at the registrar to be DNSSEC-signed. In order for your domain to work, you need to either sign it with the same key you have configured at the registrar, or have the registrar turn off DNSSEC as well.

In addition, the NS records set at the registrar need to match the NS records served by the authoritative DNS servers.

See the DNSViz report

This really isn't related to certificates; you just need a working domain name before one can get a certificate for it, or really for anyone to use that domain name at all. Once you've fixed DNS so that your domain name works again, then you should be able to get certificates for it.