dl5ark1 Posted September 2, 2019 Share Posted September 2, 2019 (edited) Server ns2.heliohost.org doesn't resolve the name dl5ark.heliohost.org: nslookup ################################### > server ns1.heliohost.org Standardserver: ns1.heliohost.org Address: 65.19.143.3 > dl5ark.heliohost.org Server: ns1.heliohost.org Address: 65.19.143.3 Name: dl5ark.heliohost.org Address: 64.62.211.134 > ftp.dl5ark.heliohost.org Server: ns1.heliohost.org Address: 65.19.143.3 Name: ftp.dl5ark.heliohost.org Address: 64.62.211.134 ################################### > server ns2.heliohost.org Standardserver: ns2.heliohost.org Address: 64.62.211.133 > dl5ark.heliohost.org Server: ns2.heliohost.org Address: 64.62.211.133 *** dl5ark.heliohost.org was not found from ns2.heliohost.org: Non-existent domain. > ftp.dl5ark.heliohost.org Server: ns2.heliohost.org Address: 64.62.211.133 *** ftp.dl5ark.heliohost.org was not found from ns2.heliohost.org: Non-existent domain. ################################### What´s wrong? Edited September 2, 2019 by dl5ark1 Quote Link to comment Share on other sites More sharing options...
Sn1F3rt Posted September 2, 2019 Share Posted September 2, 2019 Just checked... ns2 for your domain only resolves SOA. Test if the records are missing. Probably they need to be manually synced. Anyways that hardly matters took ns1 is up and functional. Quote Link to comment Share on other sites More sharing options...
wolstech Posted September 2, 2019 Share Posted September 2, 2019 Well that one's new. NS1 is the one that's been giving us issues. The domain dl5ark.heliohost.org has been synced onto NS2. > dl5ark.heliohost.org Server: ns2.heliohost.org Address: 64.62.211.133 Name: dl5ark.heliohost.org Address: 64.62.211.134 Quote Link to comment Share on other sites More sharing options...
Piotr GRD Posted September 2, 2019 Share Posted September 2, 2019 (...) Anyways that hardly matters took ns1 is up and functional. @sohamb03 For future reference... In such situations it DOES matter. If one of the nameservers is not working at all (but the other is working properly) - there is no problem.If both nameservers are online, but one have no records (or wrong records) for the domain name - there is problem: randomly in ~50% of cases we won't have access to the domain name (website, incomming mails etc.). 1 Quote Link to comment Share on other sites More sharing options...
Sn1F3rt Posted September 2, 2019 Share Posted September 2, 2019 Yup.. That was just an assurance I have to him, what you say depends on through which nameserver the website is indexed. Quote Link to comment Share on other sites More sharing options...
wolstech Posted September 2, 2019 Share Posted September 2, 2019 Piotr GRD described exactly the issue we've been seeing for the past week until a few days ago. It's better for busted NSes to be down entirely, because if it times out, the requesting device just asks the next one in the list. If it gets an answer, it just assumes that the information received is correct. NS1 was alive after Tommy came up, but until recently, had not been informed of most of the domains we have. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.