# No valid A records found **URL:** \ **Category:** Help\ **Created:** [May 17, 2023, 1:59pm UTC](https://community.letsencrypt.org/t/no-valid-a-records-found/198520 "2023-05-17T13:59:16Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![spreatty](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/spreatty/32/70472_2.png) [@spreatty](https://community.letsencrypt.org/u/spreatty)\ **Post date:** [May 17, 2023, 1:59pm UTC](https://community.letsencrypt.org/t/no-valid-a-records-found/198520/1 "2023-05-17T13:59:16Z")
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: spreatty.site I ran this command: `certbot certonly --manual` It produced this output: ```plaintext Saving debug log to C:\Certbot\log\letsencrypt.log Please enter the domain name(s) you would like on your certificate (comma and/or space separated) (Enter 'c' to cancel): spreatty.site Requesting a certificate for spreatty.site - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Create a file containing just this data: cf22NFwh3uBxR4Hr0zAQ1uERcD4oTSNZOaspvI24T7M.yvL99TIYLaYTjWTdPYB8C1tjI2zKDCfvKuYdRIKpJ5E And make it available on your web server at this URL: http://spreatty.site/.well-known/acme-challenge/cf22NFwh3uBxR4Hr0zAQ1uERcD4oTSNZOaspvI24T7M - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Press Enter to Continue Certbot failed to authenticate some domains (authenticator: manual). The Certificate Authority reported these problems: Domain: spreatty.site Type: dns Detail: no valid A records found for spreatty.site; no valid AAAA records found for spreatty.site Hint: The Certificate Authority failed to verify the manually created challenge files. Ensure that you created these in the correct location. Some challenges have failed. Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile C:\Certbot\log\letsencrypt.log or re-run Certbot with -v for more details. ``` My web server is (include version): node v18.12.1 The operating system my web server runs on is (include version): Windows 11 My hosting provider, if applicable, is: Home server 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.6.0 * * * The thing is: there is A record [Dig (DNS lookup)](https://toolbox.googleapps.com/apps/dig/#A/spreatty.site) Home page works too: [http://spreatty.site](http://spreatty.site) ---
**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:** [May 17, 2023, 2:06pm UTC](https://community.letsencrypt.org/t/no-valid-a-records-found/198520/2 "2023-05-17T14:06:50Z")
Yes an IP exists but it is a private IP. Let's encrypt must validate your domain using the public Internet > **[Test result for spreatty.site: Fatal](https://letsdebug.net/spreatty.site/1484297)** > > 1 unique issue(s) detected (ReservedAddress) ---
**Author:** ![Bruce5051](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/bruce5051/32/76576_2.png) [@Bruce5051](https://community.letsencrypt.org/u/Bruce5051)\ **Post date:** [May 17, 2023, 3:23pm UTC](https://community.letsencrypt.org/t/no-valid-a-records-found/198520/3 "2023-05-17T15:23:01Z")
You could use the [DNS-01 challenge](https://letsencrypt.org/docs/challenge-types/#dns-01-challenge) of the [Challenge Types - Let's Encrypt](https://letsencrypt.org/docs/challenge-types/) and not need to have and IP Address. > [@DNS providers who easily integrate with Let's Encrypt DNS validation](https://community.letsencrypt.org/t/dns-providers-who-easily-integrate-with-lets-encrypt-dns-validation/86438): > > Iā€¦ ---
**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:** [May 17, 2023, 4:04pm UTC](https://community.letsencrypt.org/t/no-valid-a-records-found/198520/4 "2023-05-17T16:04:01Z")
> [@Bruce5051](#): > > You could use the [DNS-01 challenge](https://letsencrypt.org/docs/challenge-types/#dns-01-challenge) of the [Challenge Types - Let's Encrypt](https://letsencrypt.org/docs/challenge-types/) Yes, if they plan to keep their site privately accessed. But they will need a public IP in their DNS to access from the public internet. If they are only going to use this privately they could consider using a self-signed cert and make their life easier šŸ™‚ ---
**Author:** ![Bruce5051](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/bruce5051/32/76576_2.png) [@Bruce5051](https://community.letsencrypt.org/u/Bruce5051)\ **Post date:** [May 17, 2023, 4:07pm UTC](https://community.letsencrypt.org/t/no-valid-a-records-found/198520/5 "2023-05-17T16:07:35Z")
I total agree @MikeMcQ, I was just trying to find a way for them to get a Let's Encrypt issued TLS Certificate. ---
**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\ **Post date:** [May 17, 2023, 4:07pm UTC](https://community.letsencrypt.org/t/no-valid-a-records-found/198520/6 "2023-05-17T16:07:42Z")
> [@MikeMcQ](#): > > But they will need a public IP in their DNS to access from the public internet. OR... A VPN could overcome that routeable IP deficiency. [just saying - I know that no VPN has been mentioned] OR... A private DNS could be used to provide the Internet IP. ---
**Author:** ![spreatty](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/spreatty/32/70472_2.png) [@spreatty](https://community.letsencrypt.org/u/spreatty)\ **Post date:** [May 17, 2023, 4:13pm UTC](https://community.letsencrypt.org/t/no-valid-a-records-found/198520/7 "2023-05-17T16:13:29Z")
Actually I'd prefer to use DNS-01 method. However, I don't see how can I run certbot for a non-wildcard domain in DNS-01 mode. Still, Mike has a point here: wrong IP is set on A record. I will need to fix that anyway, and then I'll try HTTP-01 again if port 80 is open ---
**Author:** ![danb35](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/danb35/32/70869_2.png) [@danb35](https://community.letsencrypt.org/u/danb35)\ **Post date:** [May 17, 2023, 4:31pm UTC](https://community.letsencrypt.org/t/no-valid-a-records-found/198520/8 "2023-05-17T16:31:59Z")
> [@spreatty](#): > > I don't see how can I run certbot for a non-wildcard domain in DNS-01 mode. You'd run it in exactly the same way as you'd run it for a wildcard domain--just leave out the wildcard part. So, `-d spreatty.site`. ---
**Author:** ![Bruce5051](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/bruce5051/32/76576_2.png) [@Bruce5051](https://community.letsencrypt.org/u/Bruce5051)\ **Post date:** [May 17, 2023, 4:44pm UTC](https://community.letsencrypt.org/t/no-valid-a-records-found/198520/9 "2023-05-17T16:44:17Z")
Presently I am finding a valid DNS A Record, however the IPv4 Address: 172.16.15.190 is part of the [Private network - Wikipedia](https://en.wikipedia.org/wiki/Private_network) for IPv4 Address space. ```plaintext $ nslookup -q=a spreatty.site ns19.inhostedns.com. Server: ns19.inhostedns.com. Address: 185.104.44.24#53 Name: spreatty.site Address: 172.16.15.190 ``` ```plaintext $ nslookup -q=a spreatty.site ns29.inhostedns.net. Server: ns29.inhostedns.net. Address: 185.104.46.24#53 Name: spreatty.site Address: 172.16.15.190 ``` ```plaintext $ nslookup -q=a spreatty.site ns39.inhostedns.org. Server: ns39.inhostedns.org. Address: 62.210.30.252#53 Name: spreatty.site Address: 172.16.15.190 ``` ![image](https://global.discourse-cdn.com/letsencrypt/original/3X/3/4/3497d6a0ebc48313a841d188b037669f6060e71d.png) ---
**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\ **Post date:** [May 17, 2023, 4:55pm UTC](https://community.letsencrypt.org/t/no-valid-a-records-found/198520/10 "2023-05-17T16:55:22Z")
> [@spreatty](#): > > However, I don't see how can I run certbot for a non-wildcard domain in DNS-01 mode. See the `--preferred-challenges` option in the Certbot documentation. ---
**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\ **Post date:** [June 16, 2023, 4:55pm UTC](https://community.letsencrypt.org/t/no-valid-a-records-found/198520/11 "2023-06-16T16:55:40Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.