Detail: dns :: DNS problem: NXDOMAIN looking up A for

#1

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:

    Domain: www.17068.l.time4vps.cloud
    Type: connection
    Detail: dns :: DNS problem: NXDOMAIN looking up A for
    www.17068.l.time4vps.cloud

    To fix these errors, please make sure that your domain name was
    entered correctly and the DNS A/AAAA record(s) for that domain
    contain(s) the right IP address. Additionally, please check that
    your computer has a publicly routable IP address and that no
    firewalls are preventing the server from communicating with the
    client. If you’re using the webroot plugin, you should also verify
    that you are serving files from the webroot path you provided.

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

#2

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.

#3

image

#4

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.

2 Likes
#5

So

ns1.serveriai.lt.

is their nameserver hostname and not

ns1.time4vps.com

like they have it set as default to?

#6

nsX.serveriai.lt are the nameservers for time4vps.cloud. They could delegate 17068.l.time4vps.cloud to 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 in the next few hours. Maybe it’s just wrong.

2 Likes
#7

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?

1 Like
#8

I’m using the panel from their site btw.

#9

Hi @chill

sometimes these are standard programs (browser, nslookup, dig). Sometimes these are online tools - there is a list (pinned in #help ):

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.

1 Like
closed #10

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