Struct MX

pub struct MX { /* private fields */ }

RFC 1035, DOMAIN NAMES - IMPLEMENTATION AND SPECIFICATION, November 1987

3.3.9. MX RDATA format

    +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
    |                  PREFERENCE                   |
    +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
    /                   EXCHANGE                    /
    /                                               /
    +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+

MX records cause type A additional section processing for the host
specified by EXCHANGE.  The use of MX RRs is explained in detail in
[RFC-974].

Implementations

impl MX

pub fn new(preference: u16, exchange: Name) -> Self

Constructs a new MX RData

Arguments

• preference - weight of this MX record as opposed to others, lower values have the higher preference
• exchange - Name labels for the mail server

Returns

A new MX RData for use in a Resource Record

pub fn preference(&self) -> u16

RFC 1035, DOMAIN NAMES - IMPLEMENTATION AND SPECIFICATION, November 1987

PREFERENCE      A 16 bit integer which specifies the preference given to
                this RR among others at the same owner.  Lower values
                are preferred.

pub fn exchange(&self) -> &Name

RFC 1035, DOMAIN NAMES - IMPLEMENTATION AND SPECIFICATION, November 1987

EXCHANGE        A <domain-name> which specifies a host willing to act as
                a mail exchange for the owner name.

Trait Implementations

impl Clone for MX

fn clone(&self) -> MX

Returns a copy of the value.

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

Performs copy-assignment from source.

impl Debug for MX

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Display for MX

RFC 1033, DOMAIN OPERATIONS GUIDE, November 1987

  MX (Mail Exchanger)  (See RFC-974 for more details.)

          <name>   [<ttl>] [<class>]   MX   <preference>   <host>

  MX records specify where mail for a domain name should be delivered.
  There may be multiple MX records for a particular name.  The
  preference value specifies the order a mailer should try multiple MX
  records when delivering mail.  Zero is the highest preference.
  Multiple records for the same name may have the same preference.

  A host BAR.FOO.COM may want its mail to be delivered to the host
  PO.FOO.COM and would then use the MX record:

          BAR.FOO.COM.    MX      10      PO.FOO.COM.

  A host BAZ.FOO.COM may want its mail to be delivered to one of three
  different machines, in the following order:

          BAZ.FOO.COM.    MX      10      PO1.FOO.COM.
                          MX      20      PO2.FOO.COM.
                          MX      30      PO3.FOO.COM.

  An entire domain of hosts not connected to the Internet may want
  their mail to go through a mail gateway that knows how to deliver
  mail to them.  If they would like mail addressed to any host in the
  domain FOO.COM to go through the mail gateway they might use:

          FOO.COM.        MX       10     RELAY.CS.NET.
          *.FOO.COM.      MX       20     RELAY.CS.NET.

  Note that you can specify a wildcard in the MX record to match on
  anything in FOO.COM, but that it won't match a plain FOO.COM.

fn fmt(&self, f: &mut Formatter<'_>) -> Result<(), Error>

Formats the value using the given formatter.

impl Hash for MX

fn hash<__H: Hasher>(&self, state: &mut __H)

Feeds this value into the given Hasher.

fn hash_slice<H>(data: &[Self], state: &mut H)

where H: Hasher, Self: Sized,

Feeds a slice of this type into the given Hasher.

impl PartialEq for MX

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

impl StructuralPartialEq for MX