# Detail: dns :: DNS problem: NXDOMAIN looking up A for **URL:** \ **Category:** Help\ **Created:** [March 26, 2019, 4:29am UTC](https://community.letsencrypt.org/t/detail-dns-dns-problem-nxdomain-looking-up-a-for/89598 "2019-03-26T04:29:18Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![chill](https://avatars.discourse-cdn.com/v4/letter/c/e95f7d/32.png) [@chill](https://community.letsencrypt.org/u/chill)\ **Post date:** [March 26, 2019, 4:29am UTC](https://community.letsencrypt.org/t/detail-dns-dns-problem-nxdomain-looking-up-a-for/89598/1 "2019-03-26T04:29:18Z")
My domain is: 17068.l.time4vps.cloud I ran this command: sudo certbot --nginx -d 17068.l.time4vps.cloud -d www.17068.l.time4vps.cloud It produced this output: Saving debug log to /var/log/letsencrypt/letsencrypt.log Plugins selected: Authenticator nginx, Installer nginx Obtaining a new certificate Performing the following challenges: http-01 challenge for www.17068.l.time4vps.cloud Waiting for verification… Cleaning up challenges Failed authorization procedure. www.17068.l.time4vps.cloud (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: dns :: DNS problem: NXDOMAIN looking up A for www.17068.l.time4vps.cloud IMPORTANT NOTES: - The following errors were reported by the server: My web server is: NGINX 1.14.0 The operating system my web server runs on is: Ubuntu 18.04 My hosting provider, if applicable, is: Time4vps I can login to a root shell on my machine: 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: certbot 0.31.0 ---
**Author:** ![chill](https://avatars.discourse-cdn.com/v4/letter/c/e95f7d/32.png) [@chill](https://community.letsencrypt.org/u/chill)\ **Post date:** [March 26, 2019, 4:32am UTC](https://community.letsencrypt.org/t/detail-dns-dns-problem-nxdomain-looking-up-a-for/89598/2 "2019-03-26T04:32:46Z")
I’ve looked at some other peoples solutions and have come up blank. here is a screenshot of my Nginx config and A name records. Any help very appreciated. ![image](https://global.discourse-cdn.com/letsencrypt/original/3X/d/b/dbb52ef149ecfb3c432e0958ac9e6e366af913b8.png) ---
**Author:** ![chill](https://avatars.discourse-cdn.com/v4/letter/c/e95f7d/32.png) [@chill](https://community.letsencrypt.org/u/chill)\ **Post date:** [March 26, 2019, 4:37am UTC](https://community.letsencrypt.org/t/detail-dns-dns-problem-nxdomain-looking-up-a-for/89598/3 "2019-03-26T04:37:45Z")
![image](https://global.discourse-cdn.com/letsencrypt/original/3X/2/f/2f0951c6b9f3983db17a6325081c1b2ff86b951c.png) ---
**Author:** ![mnordhoff](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mnordhoff/32/22583_2.png) [@mnordhoff](https://community.letsencrypt.org/u/mnordhoff)\ **Post date:** [March 26, 2019, 5:01am UTC](https://community.letsencrypt.org/t/detail-dns-dns-problem-nxdomain-looking-up-a-for/89598/4 "2019-03-26T05:01:02Z")
It looks like that isn’t the active DNS setup. `time4vps.cloud` uses these nameservers: ``` time4vps.cloud. 86286 NS ns1.serveriai.lt. time4vps.cloud. 86286 NS ns2.serveriai.lt. time4vps.cloud. 86286 NS ns3.serveriai.lt. time4vps.cloud. 86286 NS ns4.serveriai.lt. ``` `17068.l.time4vps.cloud` isn’t a separate zone and isn’t delegated to `ns1.time4vps.com` and `ns2.time4vps.com`. Either you aren’t accessing the right DNS control panel, or the delegation hasn’t been set up yet. ---
**Author:** ![chill](https://avatars.discourse-cdn.com/v4/letter/c/e95f7d/32.png) [@chill](https://community.letsencrypt.org/u/chill)\ **Post date:** [March 26, 2019, 5:14am UTC](https://community.letsencrypt.org/t/detail-dns-dns-problem-nxdomain-looking-up-a-for/89598/5 "2019-03-26T05:14:35Z")
So > ns1.serveriai.lt. is their nameserver hostname and not > [ns1.time4vps.com](http://ns1.time4vps.com) like they have it set as default to? ---
**Author:** ![mnordhoff](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mnordhoff/32/22583_2.png) [@mnordhoff](https://community.letsencrypt.org/u/mnordhoff)\ **Post date:** [March 26, 2019, 5:21am UTC](https://community.letsencrypt.org/t/detail-dns-dns-problem-nxdomain-looking-up-a-for/89598/6 "2019-03-26T05:21:38Z")
nsX.serveriai.lt are the nameservers for `time4vps.cloud`. They _could_ delegate `17068.l.time4vps.cloud` to [nsX.time4vps.com](http://nsX.time4vps.com), but they haven’t. I don’t know what control panel you’re using, or why it has the records it does. Maybe they’re going to delegate `17068.l.time4vps.cloud` to [nsX.time4vps.com](http://nsX.time4vps.com) in the next few hours. Maybe it’s just wrong. ---
**Author:** ![chill](https://avatars.discourse-cdn.com/v4/letter/c/e95f7d/32.png) [@chill](https://community.letsencrypt.org/u/chill)\ **Post date:** [March 26, 2019, 5:50am UTC](https://community.letsencrypt.org/t/detail-dns-dns-problem-nxdomain-looking-up-a-for/89598/7 "2019-03-26T05:50:11Z")
Ok guess I need to take it up with my provider then. Thanks a ton for the help you guys are great and responsive. What kind of tools do you guys use for finding this info and troubleshooting? ---
**Author:** ![chill](https://avatars.discourse-cdn.com/v4/letter/c/e95f7d/32.png) [@chill](https://community.letsencrypt.org/u/chill)\ **Post date:** [March 26, 2019, 5:50am UTC](https://community.letsencrypt.org/t/detail-dns-dns-problem-nxdomain-looking-up-a-for/89598/8 "2019-03-26T05:50:53Z")
I’m using the panel from their site btw. ---
**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\ **Post date:** [March 26, 2019, 7:07am UTC](https://community.letsencrypt.org/t/detail-dns-dns-problem-nxdomain-looking-up-a-for/89598/9 "2019-03-26T07:07:04Z")
Hi @chill > [@chill](#): > > What kind of tools do you guys use for finding this info and troubleshooting? sometimes these are standard programs (browser, nslookup, dig). Sometimes these are online tools - there is a list (pinned in #Help ): > [@Third-party-Tools to check your configuration](https://community.letsencrypt.org/t/third-party-tools-to-check-your-configuration/76272): > > I… One thing is curious: You have a Letsencrypt certificate, 2 days old: | CRT-Id | Issuer | not before | not after | Domain names | LE-Duplicate | next LE | | --- | --- | --- | --- | --- | --- | --- | | 1314345199 | CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US | 2019-03-24 23:44:53 | 2019-06-22 22:44:53 | 17068.l.time4vps.cloud | duplicate nr. 1 | | And now your server has the same ip address: | Host | T | IP-Address | is auth. | ∑ Queries | ∑ Timeout | | --- | --- | --- | --- | --- | --- | | 17068.l.time4vps.cloud | A | 194.135.88.19 | yes | 1 | 0 | | | AAAA | | yes | | | | www.17068.l.time4vps.cloud | | Name Error | yes | 1 | 0 | So NXDOMAIN shouldn't be a problem. ---
**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\ **Post date:** [April 25, 2019, 7:07am UTC](https://community.letsencrypt.org/t/detail-dns-dns-problem-nxdomain-looking-up-a-for/89598/10 "2019-04-25T07:07:12Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.