Understanding MX Records - Revision history

Pwadmin at 20:08, 4 November 2016

2016-11-04T20:08:26Z

Pwadmin at 16:54, 5 February 2014

2014-02-05T16:54:47Z

Pwadmin at 16:54, 5 February 2014

2014-02-05T16:54:36Z

Pwadmin at 16:54, 5 February 2014

2014-02-05T16:54:06Z

Pwadmin at 16:52, 5 February 2014

2014-02-05T16:52:50Z

Pwadmin at 15:22, 4 February 2014

2014-02-04T15:22:22Z

Pwadmin at 15:11, 4 February 2014

2014-02-04T15:11:55Z

Pwadmin at 15:11, 4 February 2014

2014-02-04T15:11:41Z

Pwadmin at 15:10, 4 February 2014

2014-02-04T15:10:21Z

Pwadmin at 14:33, 10 December 2013

2013-12-10T14:33:46Z

@@ Line 3: / Line 3: @@
-== How MX records work<br/> ==
+= How MX records work<br/> =
 The MX record ensures that emails from a domain are delivered to the correct mail server.
@@ Line 9: / Line 9: @@
-=== Directing emails<br/> ===
+== Directing emails<br/> ==
 An MX record will show that all emails from&nbsp; ''@example.com'' should be routed to the mail server at ''example.com''. An email sent to ''[mailto:user@example.com user@example.com]'' is directly routed to the email server ''216.43.49.148.''
@@ Line 17: / Line 17: @@
-=== Setting the priority<br/> ===
+== Setting the priority<br/> ==
 If the domain ''example.com'' has two MX records, ''mail1.example.com'' might have a priority of 10 and ''mail2.example.com'' might have a priority of 20, emails are delivered first to ''mail1.example.com'' because it has a lower priority number. If ''mail1.example.com'' is down, emails are redirected to ''mail2.example.com''. If two servers have the same priority, one server is chosen randomly.

@@ Line 11: / Line 11: @@
 === Directing emails<br/> ===
-An MX record will show that all emails from''@example.com'' should be routed to the mail server at ''example.com''. An email sent to ''[mailto:user@example.com user@example.com]'' is directly routed to the email server ''216.43.49.148.''
+An MX record will show that all emails from&nbsp; ''@example.com'' should be routed to the mail server at ''example.com''. An email sent to ''[mailto:user@example.com user@example.com]'' is directly routed to the email server ''216.43.49.148.''
 To further ensure that emails always get delivered, you will need to create MX records for multiple servers. When one server is down, emails will be routed to another server instead. You can assign priorities to each server using increments of 10, 20, 30, and so on. The lowest value receives the highest priority and will be tried first.

@@ Line 11: / Line 11: @@
 === Directing emails<br/> ===
-An MX record will show that all emails from''@example.com'' should be routed to the mail server at ''example.com'' should be routed to the mail server at ''example.com''. An email sent to ''[mailto:user@example.com user@example.com]'' is directly routed to the email server ''216.43.49.148.''
+An MX record will show that all emails from''@example.com'' should be routed to the mail server at ''example.com''. An email sent to ''[mailto:user@example.com user@example.com]'' is directly routed to the email server ''216.43.49.148.''
 To further ensure that emails always get delivered, you will need to create MX records for multiple servers. When one server is down, emails will be routed to another server instead. You can assign priorities to each server using increments of 10, 20, 30, and so on. The lowest value receives the highest priority and will be tried first.

@@ Line 11: / Line 11: @@
 === Directing emails<br/> ===
-should be routed to the mail server at ''example.com''. An email sent to ''[mailto:user@example.com user@example.com]'' is directly routed to the email server ''216.43.49.148.''
+An MX record will show that all emails from''@example.com'' should be routed to the mail server at ''example.com'' should be routed to the mail server at ''example.com''. An email sent to ''[mailto:user@example.com user@example.com]'' is directly routed to the email server ''216.43.49.148.''
 To further ensure that emails always get delivered, you will need to create MX records for multiple servers. When one server is down, emails will be routed to another server instead. You can assign priorities to each server using increments of 10, 20, 30, and so on. The lowest value receives the highest priority and will be tried first.

@@ Line 11: / Line 11: @@
 === Directing emails<br/> ===
-An MX record will show that all emails''@example.com'' should be routed to the mail server at ''example.com''. An email sent to ''[mailto:user@example.com user@example.com]'' is directly routed to the email server ''216.43.49.148.''
+should be routed to the mail server at ''example.com''. An email sent to ''[mailto:user@example.com user@example.com]'' is directly routed to the email server ''216.43.49.148.''
 To further ensure that emails always get delivered, you will need to create MX records for multiple servers. When one server is down, emails will be routed to another server instead. You can assign priorities to each server using increments of 10, 20, 30, and so on. The lowest value receives the highest priority and will be tried first.

← Older revision		Revision as of 15:22, 4 February 2014
Line 20:		Line 20:

	If the domain ''example.com'' has two MX records, ''mail1.example.com'' might have a priority of 10 and ''mail2.example.com'' might have a priority of 20, emails are delivered first to ''mail1.example.com'' because it has a lower priority number. If ''mail1.example.com'' is down, emails are redirected to ''mail2.example.com''. If two servers have the same priority, one server is chosen randomly.		If the domain ''example.com'' has two MX records, ''mail1.example.com'' might have a priority of 10 and ''mail2.example.com'' might have a priority of 20, emails are delivered first to ''mail1.example.com'' because it has a lower priority number. If ''mail1.example.com'' is down, emails are redirected to ''mail2.example.com''. If two servers have the same priority, one server is chosen randomly.
−
−
−
−	~~== How to set up an MX record with HostPath<br/> ==~~
−
−	~~To create an MX record:~~
−
−	~~#In the '''DNS''' module, select a zone.~~
−	~~#Click '''Records'''.~~
−	~~#Click '''MX'''.~~
−
−	~~::[[File:DNS MX highlight.png\|none\|DNS MX highlight.png]]~~
−	~~<ol start="4">~~
−	~~<li>Fill in the fields as follows:</li>~~
−	~~</ol>~~
−
−	~~::[[File:DNS MX screen.png\|none\|DNS MX screen.png]]~~
−
−	~~{\| style="margin-left: 50px; width: 500px" border="1" cellpadding="1" cellspacing="1"~~
−	\|-
−	~~! scope="col" \| Field<br/>~~
−	~~! scope="col" \| Description<br/>~~
−	\|-
−	~~\| Hostname<br/>~~
−	~~\| Enter the hostname of the device.<br/>~~
−	\|-
−	~~\| Mailserver hostname<br/>~~
−	~~\| Enter the mailserver hostname. (All emails @hostname will be routed to this mailserver hostname).<br/>~~
−	\|-
−	~~\| Priority<br/>~~
−	~~\| Set the priority number for the mailserver. A lower number is higher priority.<br/>~~
−	\|-
−	~~\| TTL<br/>~~
−	~~\| Adjust the TTL value of the zone in seconds.<br/>~~
−	\|-
−	~~\| Active<br/>~~
−	~~\| Select to activate the MX record.<br/>~~
−	\|}
−	~~<ol start="5">~~
−	~~<li>Click '''Save'''.</li>~~
−	~~</ol>~~

← Older revision		Revision as of 15:11, 4 February 2014
Line 23:		Line 23:


−	== How to set up an MX ~~Record~~ with HostPath<br/> ==	+	== How to set up an MX record with HostPath<br/> ==

	To create an MX record:		To create an MX record:

@@ Line 1: / Line 1: @@
-A mail exchange (MX) record is a type of DNS record that specifies how emails are routed to a specific mail server — it directs your domain’s emails to the servers hosting your user’s email accounts. HostPath will manage these settings to make sure emails are always delivered to the correct mail server.
+A '''mail exchange (MX) record''' is a type of DNS record that specifies how emails are routed to a specific mail server. (it directs your domain’s emails to the servers hosting your user’s email accounts.) HostPath will manage these settings to make sure emails are always delivered to the correct mail server.
 == How MX Records Work<br/> ==
 The MX record ensures that emails from a domain are delivered to the correct mail server.
 === Directing Emails<br/> ===
-An MX record will show that all emails @example.com should be routed to the mail server at example.com. An email sent to [mailto:user@example.com user@example.com] is directly routed to the email server 216.43.49.148.
+An MX record will show that all emails''@example.com'' should be routed to the mail server at ''example.com''. An email sent to ''[mailto:user@example.com user@example.com]'' is directly routed to the email server ''216.43.49.148.''
 To further ensure that emails always get delivered, you will need to create MX records for multiple servers. When one server is down, emails will be routed to another server instead. You can assign priorities to each server using increments of 10, 20, 30, and so on. The lowest value receives the highest priority and will be tried first.
 === Setting the Priority<br/> ===
 If the domain ''example.com'' has two MX records, ''mail1.example.com'' might have a priority of 10 and ''mail2.example.com'' might have a priority of 20, emails are delivered first to ''mail1.example.com'' because it has a lower priority number. If ''mail1.example.com'' is down, emails are redirected to ''mail2.example.com''. If two servers have the same priority, one server is chosen randomly.
 == How to Setup an MX Record with HostPath ==