This does not support Azure Private Dns Zone, I suppose ? #595
Replies: 1 comment
-
Created the discussion in containerapps-acmebot as I was using that repository |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I am assuming [keyvault-acmebot] does not support Azure Private Dns Zone ? The reason being when I try to add the certificate from the dashboard page, the private dns zone does not populate under the drop down list for dnz zones. So, I created a test dns zone in azure DNS instead of Azure private DNS and this time I get the dns zone under the drop down list for dnz zones, but when I try to add the certificate after selecting the container app environment and container app, it throws a pop-up that the AddOrchestratorCertificate process failed- stating that it was expecting the azure nameservers as ns1-38.azure.dns.net and other azure dns servers, but it found null, even though the azure dns zone (not private dns) has got the same NS records. I am assuming, the function app couldn't find a route to the test zone created in Azure DNS, instead of Azure private dns.
Beta Was this translation helpful? Give feedback.
All reactions