Struct ClientHasValidReverseDns 

pub struct ClientHasValidReverseDns { /* private fields */ }

Requires the client’s address to have a PTR record, optionally forward-confirmed and optionally matching a hostname pattern.

Implementations

impl ClientHasValidReverseDns

pub fn from_settings( name: &str, settings: &Settings, dns: &DnsConfig, ) -> Result<Self>

Compiles the hostname patterns and builds the resolver — dns.resolver if set, else the system configuration, the same choice challenge::from_config makes for dns-01, sharing the dns table rather than each subsystem picking its own resolver.

The resolver is shared with the rest of the crate, so it reports failures without knowing who asked; naming the setting is this caller’s job.

pub fn with_resolver( name: &str, settings: &Settings, resolver: Arc<dyn Resolver>, ) -> Result<Self>

Same, against a caller-supplied resolver. Used by tests.

Trait Implementations

impl Check for ClientHasValidReverseDns

fn stages(&self) -> StageSet

Connection-only by default; stages = ["identifiers"] moves it, which is why the identifier hook below is implemented rather than left to the trait’s default.

fn kind(&self) -> &'static str

The check type (allowed_ip, ipam, …), not the instance name — the instance name is the policy’s key for it.

fn check_connection<'life0, 'life1, 'life2, 'async_trait>( &'life0 self, context: &'life1 ConnectionContext<'life2>, ) -> Pin<Box<dyn Future<Output = Verdict> + Send + 'async_trait>>

where Self: 'async_trait, 'life0: 'async_trait, 'life1: 'async_trait, 'life2: 'async_trait,

fn check_identifiers<'life0, 'life1, 'life2, 'async_trait>( &'life0 self, context: &'life1 IdentifierContext<'life2>, ) -> Pin<Box<dyn Future<Output = Verdict> + Send + 'async_trait>>

where Self: 'async_trait, 'life0: 'async_trait, 'life1: 'async_trait, 'life2: 'async_trait,

impl Debug for ClientHasValidReverseDns

fn fmt(&self, formatter: &mut Formatter<'_>) -> Result

dyn Resolver is not Debug; the policy is the interesting part.