SSH/HTTP: Temporary failure in name resolution/ERR Name Not Resolved when accessing droplet

February 8, 2016 5.6k views
DNS Apache Debian
rvk
By:
rvk

When accessing my droplet (via SSH or HTTP by domain name) I receive errors regarding failures in name resolution. I have to retry multiple times for my requests to go through.

SSH: ssh: Could not resolve hostname apiify.io: Temporary failure in name resolution
HTTP: Err Name Not Resolved (apache2 web server)

I don't see anything wrong with my domain or DNS settings. I use namecheap name servers.

A Record    @ 159.203.9.131
A Record    api 159.203.9.131
A Record    doc 159.203.9.131
A Record    www 159.203.9.131

Any help is appreciated.

1 comment
  • gndo February 8, 2016

    May be nothing, but mxtoolbox.com reports the following warnings with dns checks:

    Name Servers are on the Same Subnet
216.87.155
216.87.152
----------------------------------------------------------------------
SOA Expire Value out of recommended range
dns1.registrar-servers.com reported Expire 604800 : Expire is recommended to be between 1209600 and 2419200.
Log In to Comment
1 Answer
gparent February 8, 2016

This will be something to bring up with NameCheap, as your domain works just fine.

Reply
Have another answer? Share your knowledge.

Related Questions