Azure-docs: Vague DNS Explanation

[EonHale]

Is there any way you can elaborate on how to setup DNS properly? I followed this document step by step and the only way to get a VM (on the same vNet) to communicate to my ILB is to manually set a hosts file. It says above for "simple testing" but where do I do this for "non-simple testing"? I've created the wildcard A records as instructed.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 2b1afa49-a5b4-92db-68e8-3feeeff52eb3
• Version Independent ID: c9191775-e49c-1462-e525-a5ce549ae743
• Content: Create internal load balancer with App Service Environment - Azure
• Content Source: articles/app-service/environment/create-ilb-ase.md
• Service: app-service
• GitHub Login: @ccompy
• Microsoft Alias: ccompy

[SnehaAgrawal-MSFT]

@EonHale Thanks for the question! We are investigating and will update you shortly.

[SnehaAgrawal-MSFT]

@EonHale Thanks for the question! When you use an External VIP, the DNS is managed by Azure. Any app created in your ASE is automatically added to Azure DNS, which is a public DNS.
You may refer this link https://docs.microsoft.com/en-us/azure/dns/dns-zones-records
If issue persists it will be helpful if you elaborate your error.

[EonHale]

Thanks, I read that document. I can tell you this isn't working for
ILB-ASE. I manually added the records as instructed in this article but
none of my VMs can communicate with my App unless I manually set a hosts
file. Thanks.

On Tue, Apr 2, 2019 at 11:45 AM SnehaAgrawal-MSFT [e-mail]
wrote:

@EonHale https://github.com/EonHale Thanks for the question! When you
use an External VIP, the DNS is managed by Azure. Any app created in your
ASE is automatically added to Azure DNS, which is a public DNS.
You may refer this link
https://docs.microsoft.com/en-us/azure/dns/dns-zones-records
If issue persists it will be helpful if you elaborate your error.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/28508#issuecomment-479060017,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGoDrCMeLZfYMA-0Sn4kdd0CCKPITk7_ks5vc3shgaJpZM4cWwRM
.

[aromanrod]

I have the same issue.

[SnehaAgrawal-MSFT]

@EonHale and @aromanrod Thanks for bringing this to our attention. Your's feedback has been shared with the content owner for further review.

[elevated-permissions]

Is there any status on this request? I also find the instructions very vague in the configuration of DNS, particularly in its interaction with the DNS settings on the vNet in which the ASE subnet is created.

[allanmoller]

same issue here!!

[holgerjay]

I'd also be interested in a little more detail on the DNS setup for ILB ASE's.
I have set this up based on this guide, deployed a web app and I can connect to it fine. But Kudu or basically anything around the scm url fails. Let's assume I'm using this URL... https://mynewaseapp730.scm.newase557.appserviceenvironment.net/
...it always redirects to...
https://newase557.appserviceenvironment.net/
..which obviously fails as there is just a zone behind this but no A record or the like.

[allanmoller]

I managed to reach SCM by just adding another A record for this. I dont like creating another ZONE as guide suggest! so instead for now i have 2 A records one for site.domain.com and another for site.scm.domain.com. Currently testing how a local install of Azure Devops connects to this, as iam uncertain how service connections through Azure will work!

[grik001]

I have the same issue, @allanmoller. I tried adding another A record both how the docs suggest and how you suggested but still unable to access SCM. Did you also configure the host file(I did)? trying to figure out what you may have done differently.

[jcbrooks92]

@SnehaAgrawal-MSFT could we get someone to follow up on this to make sure the doc references the need for the dns entry for ilbasename.appserviceenvironment.net?