Site feedback

Luisms-5511 avatar image
0 Votes"
Luisms-5511 suggested TracyMyles commented

DNS and custom domains issue - Web App Services

Steps to reproduce:

  1. Create an a Web App Service (tested on Linux with Containers) with name

  2. Add a custom domain pointing to this new WebApp. For example

  3. Check that the redirection is working.

  4. Create a second Web App Service (same configuration) with name

  5. Stop the first webapp and remove the custom domain from it.

  6. Without changing any configuration in your DNS, add the custom domain to your second WebApp. So add in but keep in mind that your DNS will still point to (first WebApp). Here is the first issue, the second WebApp will accept the custom domain eventhough the DNS provider is not point to it.

  7. Check that points to by going to your browser and typing the URL.

  8. Here is the second issue: Now delete the first WebApp. You will see that you loose access to the second WebApp.

  9. To restore access to your second WebApp (dnsissue2), create again the first WebApp (dnsissue).

Expected results:
WebApp should not allow to add a custom domain if the DNS is not pointing to it.

Why WebApp allows you to add a custom domain if the DNS is not pointing to it? The CNAME was still pointing to and old WebApp.
Deleting the first WebApp kills access to the second WebApp. It make sense since the CNAME was pointing to it. So how does the routing works? Is this a totally unexpected behaviour or I just did things in the wrong order?



· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@Luisms-5511 , thank you for the feedback. This area is specifically for Microsoft Q&A feedback only, due to this, we are closing this item.

0 Votes 0 ·

No Solutions

Your Opinion Counts

Share your feedback, or help out by voting for other people's feedback.