Web App (Linux): Inability to Access SCM Console Due to DNS Resolution Issue

Question

Web App (Linux): Inability to Access SCM Console Due to DNS Resolution Issue

AngeloMallory-9652 0

Problem description

I am unable to access the SCM console for my Web App (Linux). When I try to open the console, my browser returns a DNS_PROBE_FINISHED_NXDOMAIN error. The hostname I am attempting to reach does not seem to match my current App Service resource, suggesting I might be using an outdated or incorrect SCM URL.

Environment

Web App (Linux), Azure App Service, located in the East US region.

What I've already tried

I have reviewed the available case details and diagnostic information provided. I also attempted to verify the hostname resolution and checked for any internal proxy or firewall restrictions. Additionally, I used nslookup to confirm whether the SCM hostname resolves correctly.

Current status

I am seeking guidance on how to correctly determine and use the appropriate SCM hostname for my App Service, and how to resolve the DNS resolution issue to access the SCM console successfully.

Golla Venkata Pavani 7,535 Reputation points Microsoft External Staff Moderator

2026-09-24T15:40:03.29+00:00
Hi @AngeloMallory-9652

Thank you for reaching us regarding the issue.

The DNS_PROBE_FINISHED_NXDOMAIN error occurs because the SCM (Kudu) hostname you are using does not exist. Newer Azure App Service resources use secure unique default hostnames, so the classic pattern no longer resolves.

How to obtain the correct SCM hostname:

Microsoft documentation recommends accessing Kudu through the Azure portal so the correct URL is used automatically:

Open your Web App in the Azure portal.

In the left menu, select Development Tools > Advanced Tools.

Click Go.

This opens the Kudu/SCM site with the exact hostname that belongs to your app (classic or unique format).

You can also inspect the Default domain value on the Web App Overview blade and construct the SCM URL by inserting .scm in the appropriate place.

Additional notes:

The unique default hostname format (with hash + region) is now the default for new Web Apps, Function Apps, and Logic Apps (Standard) created in the portal. It cannot be applied retroactively to existing apps.

Private Endpoint / VNet scenarios require private DNS resolution; the public SCM hostname will not resolve correctly from outside the network.

Authentication uses Microsoft Entra ID (SSO) when opened from the portal, or deployment credentials (basic auth) when accessing the URL directly.

Using Advanced Tools > Go is the most reliable way to open the correct SCM console and avoid the NXDOMAIN error.

Reference:
https://learn.microsoft.com/en-us/Azure/app-service/resources-kudu
https://learn.microsoft.com/en-us/azure/app-service/reference-dangling-subdomain-prevention?tabs=cli

Kindly let us know if the above comment helps or you need further assistance on this issue.

Please "upvote" if the information helped you. This will help us and others in the community as well.
Golla Venkata Pavani 7,535 Reputation points Microsoft External Staff Moderator

2026-09-27T10:14:31.01+00:00

Hi @AngeloMallory-9652

I'm just reaching out to see if your issue has been resolved or if you've had a chance to review my previous comment?

Your answer

Golla Venkata Pavani 7,535 Reputation points Microsoft External Staff Moderator

2026-09-24T15:40:03.29+00:00

Hi @AngeloMallory-9652

Thank you for reaching us regarding the issue.

The DNS_PROBE_FINISHED_NXDOMAIN error occurs because the SCM (Kudu) hostname you are using does not exist. Newer Azure App Service resources use secure unique default hostnames, so the classic pattern no longer resolves.

How to obtain the correct SCM hostname:

Microsoft documentation recommends accessing Kudu through the Azure portal so the correct URL is used automatically:

Open your Web App in the Azure portal.

In the left menu, select Development Tools > Advanced Tools.

Click Go.

This opens the Kudu/SCM site with the exact hostname that belongs to your app (classic or unique format).

You can also inspect the Default domain value on the Web App Overview blade and construct the SCM URL by inserting .scm in the appropriate place.

Additional notes:

The unique default hostname format (with hash + region) is now the default for new Web Apps, Function Apps, and Logic Apps (Standard) created in the portal. It cannot be applied retroactively to existing apps.

Private Endpoint / VNet scenarios require private DNS resolution; the public SCM hostname will not resolve correctly from outside the network.

Authentication uses Microsoft Entra ID (SSO) when opened from the portal, or deployment credentials (basic auth) when accessing the URL directly.

Using Advanced Tools > Go is the most reliable way to open the correct SCM console and avoid the NXDOMAIN error.

Reference:
https://learn.microsoft.com/en-us/Azure/app-service/resources-kudu
https://learn.microsoft.com/en-us/azure/app-service/reference-dangling-subdomain-prevention?tabs=cli

Kindly let us know if the above comment helps or you need further assistance on this issue.

Please "upvote" if the information helped you. This will help us and others in the community as well.
Golla Venkata Pavani 7,535 Reputation points Microsoft External Staff Moderator

2026-09-27T10:14:31.01+00:00

Hi @AngeloMallory-9652

I'm just reaching out to see if your issue has been resolved or if you've had a chance to review my previous comment?