Struct DnsProviderAdapter 

pub struct DnsProviderAdapter<D> {
    dns: Arc<D>,
}

Adapts any [didbot_dns::DnsProvider] into an AcmeDnsChallenge.

See the module docs for why this is safe to be this thin: the provider’s own [DnsProvider::publish_txt]/[DnsProvider::withdraw_txt] are already additive and idempotent per value, so publishing a set is just diffing that set against [DnsProvider::txt_values] and issuing one call per value that needs to change. Both directions of that diff run to completion (including waiting for propagation, on a backend that does that — see Route53Dns) before Self::publish_challenge or Self::clear_challenge return, so a caller sequencing several names — as crate::acme::issue does — never proceeds to the next step with a change still in flight underneath it.

Fields

dns: Arc<D>

Implementations

impl<D: DnsProvider> DnsProviderAdapter<D>

pub fn new(dns: Arc<D>) -> Self

Wraps dns so it can answer ACME’s DNS-01 step.

Trait Implementations

impl<D: DnsProvider> AcmeDnsChallenge for DnsProviderAdapter<D>

fn publish_challenge( &self, name: &str, values: &[String], ) -> Result<(), AcmeDnsError>

Publishes exactly values as TXT records at name, replacing whatever this backend had published there before.

fn authorize_issuer( &self, zone: &str, policy: &IssuancePolicy, ) -> Result<(), AcmeDnsError>

Publishes policy as the CAA record set at zone, replacing whatever was there.

fn clear_challenge(&self, name: &str) -> Result<(), AcmeDnsError>

Removes every value published at name.