Enum trust_dns_proto::rr::domain::usage::OpUsage

pub enum OpUsage {
    Normal,
    Loopback,
    NxDomain,
}

DNS Server Operators:

Does this reserved Special-Use Domain Name have any potential impact on DNS server operators? If they try to configure their authoritative DNS server as authoritative for this reserved name, will compliant name server software reject it as invalid? Do DNS server operators need to know about that and understand why? Even if the name server software doesn’t prevent them from using this reserved name, are there other ways that it may not work as expected, of which the DNS server operator should be aware?

Variants

Normal

DNS server operators SHOULD, if they are using private addresses, configure their authoritative DNS servers to act as authoritative for these names.

DNS server operators SHOULD, if they are using test names, configure their authoritative DNS servers to act as authoritative for test names.

Loopback

DNS server operators SHOULD be aware that the effective RDATA for localhost names is defined by protocol specification and cannot be modified by local configuration.

NxDomain

DNS server operators SHOULD be aware that the effective RDATA for “invalid” names is defined by protocol specification to be nonexistent and cannot be modified by local configuration.

Trait Implementations

impl Clone for OpUsage

fn clone(&self) -> OpUsage

Returns a copy of the value.

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

Performs copy-assignment from source.

impl PartialEq for OpUsage

fn eq(&self, other: &OpUsage) -> 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 OpUsage

impl Eq for OpUsage

impl StructuralEq for OpUsage

impl StructuralPartialEq for OpUsage