DNS lookup time out

[HELOISE]

In testing various error messages such as "DNS request timed out. Timeout was 2 seconds." (the other FMs, I'm just not ready). All other FQDNs I've jokingly tried (google, etc.), but are resolved to 100%. So I think the DNS servers are working correctly. My domain is a virtual, as is usual for web hosting.

It seems to me there is a relationship between accessibility of the site and the DNS name resolution. Can it be? Should not the DNS will never break, regardless of whether the site is down? what the actual error ?

[TACY]

Can you provide us Some more information that would be helpful for us to recognize the problem.

[HELOISE]

The problem is that my site (XYZ.in) is not shown, which is at a web host:

http://DOMAIN.in
-> Home (DSL): "Web server is not reachable."
-> In the office (via proxy): "[code = DNS_TIMEOUT] A DNS lookup error occurred because the request timed out during the lookup."

So I do a nslookup to see me the answer of the DNS server. nslookup DOMAIN.IN
-> "DNS request timed out. Timeout was 2 seconds."

[Galvin]

According to google means "DNS Request Timed Out":
Symptoms: When running nslookup, you may receive this message: Can not find server name for : No response from server
Cause: The DNS server's reverse lookup zones do not contain a PTR record for the DNS server's IP address.

[TACY]

It does indeed look as if missing the dns entry. It would be easier if one has the correct link and not domain.in
The SSH server tries a reverse DNS lookup to the IP that is created from which the SSH connection. When configured on the target system is not working DNS (eg in / etc / resolv.conf an incorrect IP for the DNS server is registered), it takes 10 seconds until the timeout for the reverse DNS lookup is achieved. Only then comes the password prompt.