Enum trust_dns_proto::rr::domain::usage::AuthUsage

pub enum AuthUsage {
    Local,
    NxDomain,
    Loopback,
    Normal,
}

Authoritative DNS Servers:

Are developers of authoritative domain name servers expected to make their implementations recognize these names as special and treat them differently? If so, how?

Variants

Local

Authoritative DNS servers SHOULD recognize these names as special and SHOULD, by default, generate immediate negative responses for all such queries, unless explicitly configured by the administrator to give positive answers for private-address reverse-mapping names.

NxDomain

Authoritative DNS servers SHOULD recognize these names as special and SHOULD, by default, generate immediate negative responses for all such queries, unless explicitly configured by the administrator to give positive answers for private-address reverse-mapping names.

Loopback

Authoritative DNS servers SHOULD recognize localhost names as special and handle them as described above for caching DNS servers.

Normal

Authoritative DNS servers SHOULD NOT recognize example names as special.

Trait Implementations

impl Clone for AuthUsage

fn clone(&self) -> AuthUsage

Returns a copy of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl PartialEq for AuthUsage

fn eq(&self, other: &AuthUsage) -> bool

This method tests for self and other values to be equal, and is used by ==.

fn ne(&self, other: &Rhs) -> bool

This method tests for !=. The default implementation is almost always sufficient, and should not be overridden without very good reason.

impl Copy for AuthUsage

impl Eq for AuthUsage

impl StructuralPartialEq for AuthUsage