{"id":20,"date":"2020-06-30T15:21:00","date_gmt":"2020-06-30T15:21:00","guid":{"rendered":""},"modified":"2021-10-02T12:05:10","modified_gmt":"2021-10-02T10:05:10","slug":"how-to-ping-in-azure-console","status":"publish","type":"post","link":"http:\/\/panahy.nl\/index.php\/2020\/06\/30\/how-to-ping-in-azure-console\/","title":{"rendered":"How to Ping in Azure Console"},"content":{"rendered":"

Source: https:\/\/docs.microsoft.com\/en-us\/azure\/app-service\/web-sites-integrate-with-vnet<\/a><\/p>\n

Tools<\/h3>\n
The tools\u00a0<\/span>ping<\/strong>,\u00a0<\/span>nslookup<\/strong>, and\u00a0<\/span>tracert<\/strong>\u00a0won’t work through the console because of security constraints. To fill the void, two separate tools are added. To test DNS functionality, we added a tool named\u00a0<\/span>nameresolver.exe<\/strong>. The syntax is:<\/span><\/div>\n
\u00a0<\/span><\/div>\n
nameresolver.exe hostname [optional: DNS Server]<\/span><\/div>\n
<\/div>\n
\n

You can use nameresolver to check the hostnames that your app depends on. This way you can test if you have anything misconfigured with your DNS or perhaps don’t have access to your DNS server. You can see the DNS server that your app uses in the console by looking at the environmental variables WEBSITE_DNS_SERVER and WEBSITE_DNS_ALT_SERVER.<\/p>\n

You can use the next tool to test for TCP connectivity to a host and port combination. This tool is called\u00a0tcpping<\/strong>\u00a0and the syntax is:<\/p>\n

tcpping.exe hostname [optional: port]<\/span><\/p>\n

The\u00a0tcpping<\/strong>\u00a0utility tells you if you can reach a specific host and port. It can show success only if there’s an application listening at the host and port combination, and there’s network access from your app to the specified host and port.<\/p>\n

Additional debug steps include:<\/p>\n