Sections DNS configuration seems to mix up dns entries. By following this section you will endup in a entry like <AppName>.<ASE name>.scm.appserviceenvironment.net but should be <AppName>.scm.<ASE name>.appserviceenvironment.net like mentioned in section "Publish with an ILB ASE".
Therefore the actions to configure dns would be more like:
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
@cult-x Thanks for the feedback! We are currently investigating and will update you shortly.
Thanks for updating the documentation. I did create the 2 zones and A records as stated above. I am using Internal ASE. I created a jumpbox in the same VNET. I am unable to access Kudu console. When I try to access kudu console it get redirected to an invalid URL which results in Server IP address could not be found error.
I will also open a support case to get to the bottom of this issue.
@cult-x Thanks again for the feedback! I have assigned the issue to the content author to review further and update the document as appropriate. @rajcheval Thanks for asking question! Request you to open new issue so that we can track the progress on it. Thanks for your understanding.
Any update on Kudu/SCM access and the dns wildcard entry working as described? We are looking to cut down on DNS overhead and are hopeful that dns wildcard entry "*" will allow for dns resolution for hosted apps on the ILB-ASE.
@hammer5280 I used fiddler to figure out what was going on. The documentation is indeed missing a required step. It turns for that for kudu console to work I had to create a host entry on my host file for ASE URL. In addition to what is already mentioned in the documentation I had to point ILB IP to the ASE URL. Once I did this Kudu console started working.
I succeeded to access kudu on ILB ASE with 3 A records "", ".scm", "@" in ilbasename.appserviceenvironment.net zone, all points ILP private ip address.
Third configuration for @ seems to be missing in this doc.
Sorry, wildcard(asterisk) was removed...
I want to write 3 A records named "
Most helpful comment
Thanks for updating the documentation. I did create the 2 zones and A records as stated above. I am using Internal ASE. I created a jumpbox in the same VNET. I am unable to access Kudu console. When I try to access kudu console it get redirected to an invalid URL which results in Server IP address could not be found error.
I will also open a support case to get to the bottom of this issue.