Enum trust_dns_proto::rr::domain::usage::AuthUsage[][src]

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

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

Returns a copy of the value. Read more

Performs copy-assignment from source. Read more

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

This method tests for !=.

Auto Trait Implementations

Blanket Implementations

Gets the TypeId of self. Read more

Immutably borrows from an owned value. Read more

Mutably borrows from an owned value. Read more

Performs the conversion.

Performs the conversion.

The resulting type after obtaining ownership.

Creates owned data from borrowed data, usually by cloning. Read more

🔬 This is a nightly-only experimental API. (toowned_clone_into)

Uses borrowed data to replace owned data, usually by cloning. Read more

The type returned in the event of a conversion error.

Performs the conversion.

The type returned in the event of a conversion error.

Performs the conversion.