Host Not Found, potential DNS issue

[Stefan Klotz]

​Hi there,
over the last months I sometimes found the following error message during troubleshooting:
Host Not Found: The Server referenced in the URL cannot be reached. This code can be returned if either the host does not exist or the host is simply down.
It's always just a few/short occurence and before starting fingerpointing to other departments I want to be sure, that this is NOT an issue with the gateway. Is there any way to double check that there is no DNS-resolution issue with the gateway? How can this be further analyzed? Or can this somehow be optimized (e.g. DNS TTL)?
Any ideas or hints would be helpful.
Thank you!

Ciao Stefan :)

[Deactivated User]

Mostly I use to get the host not found due to dns error. I use to confirm this by login on the shell and making a host entry in the Linux Shell.
With Regards to TTL here is a KB article
https://knowledge.broadcom.com/external/article/12118/api-gateway-adjusting-the-dns-cache-or-t.html


The response.routingcode we use to get was -1 when the DNS was not reachable or could not be resolved also

------------------------------
Pre-Sales Consultant
CA Southern Africa
------------------------------

[Sachin Ghumbre]

Most likely this should be DNS issue. When you face this issue, run nslookup <<hostname>> command from your system and check the IPs resolved. If you found correct domain IP then DNS configuration is fine. If not, then DNS issue, may be DNS cache issue. In this case connect to your network team.

------------------------------
Technology Lead
Infosys Limited
------------------------------