Enable configurable DNS propagation time for Azure DNS plugin #562
Conversation
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
Thanks for opening this pull request! Be sure to follow the pull request template!
|
I am a bot, here is the pushed image/manifest for this PR:
|
|
I am a bot, here is the pushed image/manifest for this PR:
|
|
I see an issue terricain/certbot-dns-azure#1 which is closed but shows log output with the propagation flag to be unsupported. Later someone reported terricain/certbot-dns-azure#36 which shows log output that looks like the propagation flag is supported, so I think it's safe to assume this should be fine. |
|
I'd like #564 to merge first and then this would need a changelog entry in the |
|
I am a bot, here is the pushed image/manifest for this PR:
|
|
I am a bot, here is the pushed image/manifest for this PR:
|
|
I am a bot, here is the pushed image/manifest for this PR:
|
Description:
Add support for the PROPAGATION environment variable to the Azure DNS plugin, allowing configurable wait times for DNS record propagation.
Benefits of this PR and context:
Prior to this change, the Azure DNS plugin ignored propagation delays and could fail DNS-01 challenges when records hadn’t yet propagated. By honoring the PROPAGATION setting, the plugin now behaves consistently with Certbot’s propagation mechanism and aligns with other DNS providers.
How Has This Been Tested?
After confirming that the Azure DNS plugin supports configurable propagation time with Certbot, I removed it from the list of DNS plugins that lack propagation-time support. Then I cleared the letsencrypt folder, requested a new certificate, and reviewed the logs to verify that the propagation delay was applied correctly.
Source / References: