Related

Tool Instant DNS Lookup Tool Tool
Howto setup apache2 request through 1 DMZ Question Question
Server won't boot Question Question

Question

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

Posted February 8, 2016 11.1k views
ApacheDebianDNS

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.

Add a comment
rvk
By:
rvk

Related

Tool Instant DNS Lookup Tool Tool
Howto setup apache2 request through 1 DMZ Question Question
Server won't boot Question Question
Add a comment
1 comment
  • gndo February 8, 2016
    Reply Report

    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.

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
Submit an Answer
1 answer
gparent February 8, 2016

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

Reply Report

Related

Looking for something else?

Ask a new question Search for more help