# Certbot : "DNS problem: looking up A for my\_domain: DNSSEC: RRSIGs Missing; no valid AAAA records found for my\_domain

**URL:** <https://community.letsencrypt.org/t/certbot-dns-problem-looking-up-a-for-my-domain-dnssec-rrsigs-missing-no-valid-aaaa-records-found-for-my-domain/220673>\
**Category:** Help\
**Created:** [June 25, 2024, 11:09am UTC](https://community.letsencrypt.org/t/certbot-dns-problem-looking-up-a-for-my-domain-dnssec-rrsigs-missing-no-valid-aaaa-records-found-for-my-domain/220673 "2024-06-25T11:09:53Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![evol](https://avatars.discourse-cdn.com/v4/letter/e/73ab20/32.png) [@evol](https://community.letsencrypt.org/u/evol)\
**Post date:** [June 25, 2024, 11:09am UTC](https://community.letsencrypt.org/t/certbot-dns-problem-looking-up-a-for-my-domain-dnssec-rrsigs-missing-no-valid-aaaa-records-found-for-my-domain/220673/1 "2024-06-25T11:09:53Z")

</div>

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](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: [joseldsm.com](http://joseldsm.com)

I ran this command: sudo certbot --nginx [joseldsm.com](http://joseldsm.com) -d [www.joseldsm.com](http://www.joseldsm.com)

It produced this output: "DNS problem: looking up A for [joseldsm.com](http://joseldsm.com): DNSSEC: RRSIGs Missing; no valid AAAA records found for [joseldsm.com](http://joseldsm.com)  
(same for [www.joseldsm.com](http://www.joseldsm.com))

My web server is (include version): nginx 1.18.0

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

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 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 don't know

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

I'm trying to get the https certification. My domain works perfectly for the basic http : [joseldsm.com](http://joseldsm.com) and [www.joseldsm.com](http://www.joseldsm.com).

Thanks ! 🙂

---

<div class="post-metadata">

**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\
**Post date:** [June 25, 2024, 1:53pm UTC](https://community.letsencrypt.org/t/certbot-dns-problem-looking-up-a-for-my-domain-dnssec-rrsigs-missing-no-valid-aaaa-records-found-for-my-domain/220673/2 "2024-06-25T13:53:23Z")

</div>

Welcome @evol

Your DNS has a couple problems.

One is that the IP address in your A record is for a private IP address. That needs to be a public IP so the Let's Encrypt server can send your server an HTTP request to validate your cert request.

You say your site works on HTTP but it must work on the public internet. Not just your local network.

> **[Test result for joseldsm.com: Fatal](https://letsdebug.net/joseldsm.com/2059556)**
>
> 1 unique issue(s) detected (ReservedAddress)

The other problem is the DNSSEC seems wrong on your DNS in general. I recommend disabling that first. Once you get a cert try to re-enable again. Sometimes that clears these up. Use the above Let's Debug test site to check after you re-enable it  
[https://dnsviz.net/d/joseldsm.com/dnssec/](https://dnsviz.net/d/joseldsm.com/dnssec/)

---

<div class="post-metadata">

**Author:** ![evol](https://avatars.discourse-cdn.com/v4/letter/e/73ab20/32.png) [@evol](https://community.letsencrypt.org/u/evol)\
**Post date:** [June 25, 2024, 2:11pm UTC](https://community.letsencrypt.org/t/certbot-dns-problem-looking-up-a-for-my-domain-dnssec-rrsigs-missing-no-valid-aaaa-records-found-for-my-domain/220673/3 "2024-06-25T14:11:19Z")

</div>

Hello @MikeMcQ,

Thank you very much for your help. I just disabled DNSSEC for now. I didn't realize the IP adress was private. I really thought it worked on public internet.

I'll try to get a public adress instead then.

Thanks again !

---

<div class="post-metadata">

**Author:** ![evol](https://avatars.discourse-cdn.com/v4/letter/e/73ab20/32.png) [@evol](https://community.letsencrypt.org/u/evol)\
**Post date:** [June 26, 2024, 1:25pm UTC](https://community.letsencrypt.org/t/certbot-dns-problem-looking-up-a-for-my-domain-dnssec-rrsigs-missing-no-valid-aaaa-records-found-for-my-domain/220673/4 "2024-06-26T13:25:22Z")

</div>

I got a public IP and now it works ! Thanks a lot @MikeMcQ !

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [July 26, 2024, 1:25pm UTC](https://community.letsencrypt.org/t/certbot-dns-problem-looking-up-a-for-my-domain-dnssec-rrsigs-missing-no-valid-aaaa-records-found-for-my-domain/220673/5 "2024-07-26T13:25:25Z")

</div>

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