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
impl Copy for AuthUsage
impl Eq for AuthUsage
impl StructuralEq for AuthUsage
impl StructuralPartialEq for AuthUsage
Auto Trait Implementations
impl RefUnwindSafe for AuthUsage
impl Send for AuthUsage
impl Sync for AuthUsage
impl Unpin for AuthUsage
impl UnwindSafe for AuthUsage
Blanket Implementations
sourceimpl<T> BorrowMut<T> for T where
T: ?Sized,
impl<T> BorrowMut<T> for T where
T: ?Sized,
const: unstable · sourcefn borrow_mut(&mut self) -> &mut T
fn borrow_mut(&mut self) -> &mut T
Mutably borrows from an owned value. Read more
sourceimpl<T> ToOwned for T where
T: Clone,
impl<T> ToOwned for T where
T: Clone,
type Owned = T
type Owned = T
The resulting type after obtaining ownership.
sourcefn clone_into(&self, target: &mut T)
fn clone_into(&self, target: &mut T)
toowned_clone_into
)Uses borrowed data to replace owned data, usually by cloning. Read more