# DNS problem: NXDOMAIN looking up A for mynginx.adams.org **URL:** \ **Category:** Help\ **Created:** [March 5, 2023, 1:21pm UTC](https://community.letsencrypt.org/t/dns-problem-nxdomain-looking-up-a-for-mynginx-adams-org/193918 "2023-03-05T13:21:45Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![24adithya](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/24adithya/32/68315_2.png) [@24adithya](https://community.letsencrypt.org/u/24adithya)\ **Post date:** [March 5, 2023, 1:21pm UTC](https://community.letsencrypt.org/t/dns-problem-nxdomain-looking-up-a-for-mynginx-adams-org/193918/1 "2023-03-05T13:21:46Z")
# My domain is: [mynginx.adams.org](http://mynginx.adams.org) # I ran this command: sudo certbot --nginx It produced this output: Saving debug log to /var/log/letsencrypt/letsencrypt.log Which names would you like to activate HTTPS for? We recommend selecting either all domains, or all domains in a VirtualHost/server block. * * * 1: [mynginx.adams.org](http://mynginx.adams.org) * * * Select the appropriate numbers separated by commas and/or spaces, or leave input blank to select all options shown (Enter 'c' to cancel): 1 Requesting a certificate for [mynginx.adams.org](http://mynginx.adams.org) Certbot failed to authenticate some domains (authenticator: nginx). The Certificate Authority reported these problems: Domain: [mynginx.adams.org](http://mynginx.adams.org) Type: dns # Detail: DNS problem: NXDOMAIN looking up A for [mynginx.adams.org](http://mynginx.adams.org) - check that a DNS record exists for this domain; DNS problem: NXDOMAIN looking up AAAA for [mynginx.adams.org](http://mynginx.adams.org) - check that a DNS record exists for this domain Hint: The Certificate Authority failed to verify the temporary nginx configuration changes made by Certbot. Ensure the listed domains point to this nginx server and that it is accessible from the internet. Some challenges have failed. Ask for help or search for solutions at [https://community.letsencrypt.org](https://community.letsencrypt.org). See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details. # My web server is (include version): nginx/1.23.3 The operating system my web server runs on is (include version): Ubuntu 22.04 My hosting provider, if applicable, is: N/A 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): Ubuntu Gnome Terminal # The version of my client is (e.g. output of `certbot --version` or `certbot-auto --version` if you're using Certbot): certbot 2.3.0 My /etc/hosts looks as follows: # 127.0.0.1 localhost [mynginx.adams.org](http://mynginx.adams.org) 127.0.1.1 24adithya The following lines are desirable for IPv6 capable hosts ::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters Can someone tell me what else needs to be configured? ---
**Author:** ![orangepizza](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/orangepizza/32/19597_2.png) [@orangepizza](https://community.letsencrypt.org/u/orangepizza)\ **Post date:** [March 5, 2023, 1:30pm UTC](https://community.letsencrypt.org/t/dns-problem-nxdomain-looking-up-a-for-mynginx-adams-org/193918/2 "2023-03-05T13:30:02Z")
Disclaimer: I throw the question into chatGPT and this is the result. The error message indicates that the Let's Encrypt certificate authority was unable to verify that your domain, `mynginx.adams.org`, exists and is pointing to the correct IP address. This could be due to various reasons, such as a DNS misconfiguration, firewall issues, or server connectivity problems. To troubleshoot this issue, you should try the following steps: 1. Verify that the domain `mynginx.adams.org` is registered and points to the correct IP address. You can use a DNS lookup tool like `dig` or `nslookup` to check the DNS records. For example: ```plaintext $ dig mynginx.adams.org ;; ANSWER SECTION: mynginx.adams.org. 3600 IN A ``` If the DNS records are not found or incorrect, you should fix the DNS configuration. - Ensure that your server is accessible from the internet and that there are no firewall rules blocking incoming traffic on port 80 and 443. You can test the connectivity using the `telnet` command. For example: ```plaintext $ telnet mynginx.adams.org 80 $ telnet mynginx.adams.org 443 ``` If you cannot connect to the server, you should check your firewall rules and network configuration. - Verify that your nginx configuration is correct and matches the Let's Encrypt requirements. You can use the `nginx -t` command to check the syntax of your nginx configuration files. For example: ```plaintext $ nginx -t ``` If there are any syntax errors or configuration issues, you should fix them before retrying the Let's Encrypt certificate request. - Ensure that your server clock is correct and synchronized with the internet time servers. You can use the `timedatectl` command to check the system time. If the time is not correct, you should fix it using the appropriate time synchronization tools for your operating system. Once you have resolved any issues, you can try running the `sudo certbot --nginx` command again to request the Let's Encrypt certificate for your domain. ---
**Author:** ![orangepizza](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/orangepizza/32/19597_2.png) [@orangepizza](https://community.letsencrypt.org/u/orangepizza)\ **Post date:** [March 5, 2023, 1:33pm UTC](https://community.letsencrypt.org/t/dns-problem-nxdomain-looking-up-a-for-mynginx-adams-org/193918/3 "2023-03-05T13:33:44Z")
a human replying: do you own [adams.org](http://adams.org)? as you bought the domain? you can't just make up a domain and expect LE to verity that, public CA only accepts public name. ---
**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:** [March 5, 2023, 2:04pm UTC](https://community.letsencrypt.org/t/dns-problem-nxdomain-looking-up-a-for-mynginx-adams-org/193918/4 "2023-03-05T14:04:15Z")
Perhaps: mynginx.adams. ~~org~~ some other TLD Like: ```plaintext Name: mynginx.adams.cc Address: 91.195.240.103 Name: mynginx.adams.com Addresses: 165.160.13.20 165.160.15.20 Name: mynginx.adams.com.br Addresses: 165.160.15.20 165.160.13.20 Name: mynginx.adams.in Address: 91.195.241.232 Name: mynginx.adams.rest Address: 88.198.150.39 ``` ---
**Author:** ![24adithya](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/24adithya/32/68315_2.png) [@24adithya](https://community.letsencrypt.org/u/24adithya)\ **Post date:** [March 5, 2023, 4:56pm UTC](https://community.letsencrypt.org/t/dns-problem-nxdomain-looking-up-a-for-mynginx-adams-org/193918/5 "2023-03-05T16:56:44Z")
Ok - got it. It's just a name I have given to my server. Thanks for sharing this info. I was under the impression that I will be able to generated authentic and approved certificates for enabling SSL for local servers as well 🙂 ---
**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\ **Post date:** [March 5, 2023, 5:16pm UTC](https://community.letsencrypt.org/t/dns-problem-nxdomain-looking-up-a-for-mynginx-adams-org/193918/6 "2023-03-05T17:16:23Z")
> [@24adithya](#): > > I was under the impression that I will be able to generated authentic and approved certificates for enabling SSL for local servers as well 🙂 Please read [How It Works - Let's Encrypt](https://letsencrypt.org/how-it-works/) ---
**Author:** ![24adithya](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/24adithya/32/68315_2.png) [@24adithya](https://community.letsencrypt.org/u/24adithya)\ **Post date:** [March 5, 2023, 5:28pm UTC](https://community.letsencrypt.org/t/dns-problem-nxdomain-looking-up-a-for-mynginx-adams-org/193918/7 "2023-03-05T17:28:11Z")
Thanks! ---
**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\ **Post date:** [April 4, 2023, 5:28pm UTC](https://community.letsencrypt.org/t/dns-problem-nxdomain-looking-up-a-for-mynginx-adams-org/193918/8 "2023-04-04T17:28:30Z")
Closed on April 4, 2023, 5:28pm UTC This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.