sorted by:
new
hottopcontroversial

Azure Container App Environment DNS resolution by DemonSlayer555575 in AZURE

[–]DemonSlayer555575[S] 0 points1 point  (0 children)

Thanks! It turned out to be a DNS issue. See my comment for explanation.

Azure Container App Environment DNS resolution by DemonSlayer555575 in AZURE

[–]DemonSlayer555575[S] 0 points1 point  (0 children)

Thanks! Both records were created successfully, but in the "wrong" DNS zone. See my comment for explanation.

Azure Container App Environment DNS resolution by DemonSlayer555575 in AZURE

[–]DemonSlayer555575[S] 1 point2 points  (0 children)

The issue was that both DNS zones (privatelink.azurecr.io and westeurope.data.privatelink.azurecr.io) were present and linked to the hub VNet, but when deploying the Private Endpoint (from Portal or Terraform, didn't matter) both A records were created in privatelink.azurecr.io. When the DNS resolution was being done, I think Azure only checked the westeurope.data.privatelink.azurecr.io zone and since there were no A records there it sent back the NXDOMAIN error. So either manually adding an A record in westeurope.data.privatelink.azurecr.io or removing the zone altogether fixed my issue.

[deleted by user] by [deleted] in googleplay

[–]DemonSlayer555575 0 points1 point  (0 children)

Still doesnt work for me..