MX stands for Mail eXchange. MX Records tell email delivery agents where they should deliver your email. You can have many MX records for a domain, providing a way to have redundancy and ensure that email will always be delivered.
Google Apps provides a common example of using MX Records for email delivery. When you create a Google Apps account and you want your email to be delivered to your Google Apps mail account, Google provides you with a set of MX records that you need to add to DNSimple. Here are the default MX records that Google suggests you should add:
Google provides you with 7 different servers that can except your email. Each MX record includes a priority value, which is a relative value compared to the other priorities of MX records for your domain. Addresses with lower values will be used first. Therefore, when a mail agent wants to deliver an email to you it would first attempt to deliver to aspmx.l.google.com. If that server cannot handle the delivery it would then move onto alt1.aspmx.l.google.com, and if that server cannot handle the delivery then it would move onto alt2.aspmx.l.google.com, and so on.
Adding Google's MX records for your domain is so common that there is already a standard DNSimple template to make this a one-click operation. Edit your domain and click on the Apply Template link and apply the Google Apps template and you'll get all of the MX records for Google Apps and more.
MX records make it easy to define what servers should handle email delivery and allows you to provide multiple servers for maximum redundancy and ensured delivery.
I break things so Simone continues to have plenty to do. I occasionally have useful ideas, like building a domain and DNS provider that doesn't suck.
Configure DNSimple as your secondary DNS provider to improve your domain's availability and redundancy with AXFR zone transfers.
Get a free limited-edition t-shirt featuring the characters of howdns.works and howhttps.works with any new yearly subscription to DNSimple.