#####   ######  #####    ###    #   #  ###  #   #  ######
##  ##  ##      ##  ##  ## ##   #   #   #   #   #  ##
#####   ####    #####   #   #   #   #   #   #   #  ####
##  #   ##      ##      ## ##    # #    #    # #   ##
##   #  ######  ##       ###      #    ###    #    ######

$ curl repovive.com/roadmaps/network-design/dhcp-and-dns/dns-mx-records

░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░███████████████████████████████████████████████████████████████████████

#####   ######  #####    ###    #   #  ###  #   #  ######
##  ##  ##      ##  ##  ## ##   #   #   #   #   #  ##
#####   ####    #####   #   #   #   #   #   #   #  ####
##  #   ##      ##      ## ##    # #    #    # #   ##
##   #  ######  ##       ###      #    ###    #    ######

$ curl repovive.com/roadmaps/network-design/dhcp-and-dns/dns-mx-records

Repovive

DNS MX Records - DHCP and DNS | Network Design | Repovive

Repovive.

Network Design26 sections · 911 units44h total

Open in Course

DNS MX Records

Mail routing

MX records (Mail Exchanger) tell email servers where to deliver mail for a domain.

example.com.  3600  IN  MX  10  mail1.example.com.
example.com.  3600  IN  MX  20  mail2.example.com.

The numbers ( $10$ and $20$ ) are priorities. Lower is preferred. Sending servers try mail1 first. If it's unavailable, they try mail2.

MX records point to hostnames, not IPs. Those hostnames need their own A records.