Community Q&A:
Pingdom.com shows this result during domain test What it means?
ns1.webhostinghub.com.
Name server ns1.webhostinghub.com (205.134.224.133) is recursive.
The name server answers recursive queries for 3rd parties (such as DNSCheck). By making a recursive query to a name server that provides recursion, an attacker can cause a name server to look up and cache information contained in zones under their control. Thus the victim name server is made to query the attackers malicious name servers, resulting in the victim caching and serving bogus data.
ns2.webhostinghub.com.
Name server ns2.webhostinghub.com (173.205.127.4) is recursive.
The name server answers recursive queries for 3rd parties (such as DNSCheck). By making a recursive query to a name server that provides recursion, an attacker can cause a name server to look up and cache information contained in zones under their control. Thus the victim name server is made to query the attackers malicious name servers, resulting in the victim caching and serving bogus data.
Name server ns1.webhostinghub.com (205.134.224.133) is recursive.
The name server answers recursive queries for 3rd parties (such as DNSCheck). By making a recursive query to a name server that provides recursion, an attacker can cause a name server to look up and cache information contained in zones under their control. Thus the victim name server is made to query the attackers malicious name servers, resulting in the victim caching and serving bogus data.
ns2.webhostinghub.com.
Name server ns2.webhostinghub.com (173.205.127.4) is recursive.
The name server answers recursive queries for 3rd parties (such as DNSCheck). By making a recursive query to a name server that provides recursion, an attacker can cause a name server to look up and cache information contained in zones under their control. Thus the victim name server is made to query the attackers malicious name servers, resulting in the victim caching and serving bogus data.
ANSWERS
|
0
|
Hello Fawad, We have apparently seen this a few times now (you are not the only one to see it), and after further investigation with our senior tech shows that the responses you are seeing are being generated from false positives. In our testing, we did both dig and host testing (dig and host are dns tools). The tests were ran against 2 domains. The host command returns the results for our domain (which it should), however it does not return anything for the second test (which is a well known domain - yahoo.com), and instead returns the SERVFAIL error. The yahoo.com query failing shows us that our nameservers are not giving results for domain names that are not under our control. And thus, cannot be made to serve "bogus data" as the warnings are indicating. I hope this helps to re-assure you that this is not a problem. If you have any further questions, please post comment at the bottom of the page. Regards, Arnel C. |
Want to share this Question?
Tweet
Help Center Login
Related Articles
It looks like there are no related articles.
Would you like to ask a question about this page? If so, click the button below!
