Ping: cannot resolve vanishthevan.com: Unknown host

Website, Application, Performance DNS & Network
1

I have never ran into this issue in the many years I’ve been using Cloudflare and Google Domains.
I have vanishthevan.com registered through Google and setup with Cloudflare:

image
image2054×314 44 KB

The A record is coming back correctly:

AND the nameservers are coming back correctly:

I am using a Digital Ocean droplet. I have destroyed the droplet and created a new one. I have also deleted my domain from Cloudflare and started over.

I cannot resolve this domain and I cannot determine the reason.

Please help me, thank you!

2

Can you post the output of these six commands?

nslookup vanishthevan.com
nslookup www.vanishthevan.com
nslookup vanishthevan.com 1.1.1.1
nslookup www.vanishthevan.com 1.1.1.1
ping vanishthevan.com
ping www.vanishthevan.com

For me the domain resolves, but the server does not respond. Could you be confusing these two?

3

Hi, thanks for the response. I don’t think I am confusing anything. This is how I setup this stuff everytime but this time it is simply not working. Thanks for your help, here are the commands output:

➜  trellis.vanishthevan.build git:(master) nslookup vanishthevan.com
Server:         192.168.0.1
Address:        192.168.0.1#53

Non-authoritative answer:
*** Can't find vanishthevan.com: No answer

➜  trellis.vanishthevan.build git:(master) nslookup www.vanishthevan.com
Server:         192.168.0.1
Address:        192.168.0.1#53

** server can't find www.vanishthevan.com: NXDOMAIN

➜  trellis.vanishthevan.build git:(master) nslookup vanishthevan.com 1.1.1.1
Server:         1.1.1.1
Address:        1.1.1.1#53

Non-authoritative answer:
Name:   vanishthevan.com
Address: 147.182.139.76

➜  trellis.vanishthevan.build git:(master) nslookup www.vanishthevan.com 1.1.1.1
Server:         1.1.1.1
Address:        1.1.1.1#53

Non-authoritative answer:
www.vanishthevan.com    canonical name = vanishthevan.com.
Name:   vanishthevan.com
Address: 147.182.139.76

➜  trellis.vanishthevan.build git:(master) ping vanishthevan.com
ping: cannot resolve vanishthevan.com: Unknown host

➜  trellis.vanishthevan.build git:(master) ping www.vanishthevan.com
ping: cannot resolve www.vanishthevan.com: Unknown host
4

You have an issue with your local DNS resolver. Either reboot your router (if that’s your resolver) or switch to one of the public resolvers.

1 Like
5

Ok, so my brother and myself are on the same network here at our office and he wasn’t able to resolve the domain IP either. We rebooted the router and then he was able to resolve but I am still unable. He’s on a Mac Mini and I’m on an iMac.

I’ve flushed DNS cache and restarted my iMac and I’m still unable to resolve.

How do I switch to a public resolver?

6

You need to change your system settings to point to any of the available public resolvers

But if your router actually now has the correct IP address it might be something cached on your machine. You best reboot that too.

7

Thanks for info. I’ll try to figure out how to change my system settings.

I’ve already rebooted and attempted to flush my dns cache to no avail.

8

If it works on another machine on the same network it won’t be a resolver issue any more, but really something on your machine I am afraid.

9

Thanks so much for your help!
I went in and added Google’s DNS:

image
image1428×1230 148 KB

Now I can resolve.

Will changing this create any issues anywhere else or for any other projects?

10

Not really, unless you used specific nameservers which resolved particular hostnames, but that’s not the standard setup.

I’d probably still try to figure out why your original resolver did not return the right addresses, respectivly why it still did not work, even after you had fixed it with the reboot. But that’s a different issue of course.

11

Ok, thanks!

I am not much of a network guy and I’ve never changed my network settings DNS before, so should be good to go now…

Before the reboot and changing those settings, I was able to resolve other domains but not this specific one.

12

DNS is a hierarchical system and depends on proper data propagation, which sometimes can take time (that’s where the famous 48 hours come from).

In your case your resolver might have cached the non-existent record response from earlier and the reboot fixed that (they usually do) but it’s not clear why afterwards you still couldn’t resolve it.

Anyhow, if you are happy with that fix you should be good to go :slight_smile:.

13

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