Enum trust_dns_proto::rr::domain::usage::OpUsage [−][src]
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
NormalDNS 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.
LoopbackDNS server operators SHOULD be aware that the effective RDATA for localhost names is defined by protocol specification and cannot be modified by local configuration.
NxDomainDNS 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[src]
impl Clone for OpUsagefn clone(&self) -> OpUsage[src]
fn clone(&self) -> OpUsageReturns a copy of the value. Read more
fn clone_from(&mut self, source: &Self)1.0.0[src]
fn clone_from(&mut self, source: &Self)Performs copy-assignment from source. Read more
impl Copy for OpUsage[src]
impl Copy for OpUsageimpl PartialEq for OpUsage[src]
impl PartialEq for OpUsagefn eq(&self, other: &OpUsage) -> bool[src]
fn eq(&self, other: &OpUsage) -> boolThis method tests for self and other values to be equal, and is used by ==. Read more
fn ne(&self, other: &Rhs) -> bool1.0.0[src]
fn ne(&self, other: &Rhs) -> boolThis method tests for !=.
impl Eq for OpUsage[src]
impl Eq for OpUsage