Enum hickory_proto::rr::domain::usage::AppUsage

pub enum AppUsage {
    Normal,
    Loopback,
    LinkLocal,
    NxDomain,
}

Application Software:

Are writers of application software expected to make their software recognize these names as special and treat them differently? In what way? (For example, if a human user enters such a name, should the application software reject it with an error message?)

Variants

Normal

Application software SHOULD NOT recognize these names as special, and SHOULD use these names as they would other reverse-mapping names.

Application software SHOULD NOT recognize test names as special, and SHOULD use test names as they would other domain names.

Application software SHOULD NOT recognize example names as special and SHOULD use example names as they would other domain names.

Loopback

Application software MAY recognize localhost names as special, or MAY pass them to name resolution APIs as they would for other domain names.

LinkLocal

Link local, generally for mDNS

NxDomain

Application software MAY recognize “invalid” names as special or MAY pass them to name resolution APIs as they would for other domain names.

Trait Implementations

impl Clone for AppUsage

fn clone(&self) -> AppUsage

Returns a copy of the value.

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

Performs copy-assignment from source.

impl PartialEq for AppUsage

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

Tests for self and other values to be equal, and is used by ==.

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

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

impl Copy for AppUsage

impl Eq for AppUsage

impl StructuralPartialEq for AppUsage