Setting to set DNS resolver about keyvault-acmebot HOT 3 CLOSED

ACME Issuers such as Let's Encrypt use their own or public DNS to resolve the necessary DNS records, so they use public DNS such as 8.8.8.8 to increase the success rate of issuance.

We do not believe Acmebot is suitable for deployment within a Private Network due to its features. Are you running a private ACME Issuer?

from keyvault-acmebot.

For us it's more of a forced tunnel. All of our Azure traffic has to pass through central firewalls and public dns resolvers are not allowed for security purposes (all dns queries have to be logged at a centralized server). We are using LetsEncrypt & Cloudflare for the provider.

We have deployed everything using privatelinks to keep traffic internal to the network and route traffic via the firewalls. If I open port 53 to the function app, it works fine. When I close it, we get the previously mentioned error and I can see the traffic attempt from the function app trying to reach 8.8.8.8 on port 53.

from keyvault-acmebot.

Acmebot uses 8.8.4.4 and 8.8.8.8, so the simplest solution is to allow it for those two DNSs. We do not want to have this behavior customized, as we have had previous experience with failed publishing using Azure-provided DNS.

Frankly, it is not an application that was implemented to be used in such a very closed environment.

from keyvault-acmebot.