tomp
01-07-2006, 12:57 AM
This mainly pertains to our VDS folks but would apply to basically any customer who is routing email to a non Myriad Network based server. A good example of this would be a customer who hosts a website with us, but has email delivered to a mail server at there business location.
When you modify the routing for email you typically do so by adjusting the mail exchange or "MX" record.
Per RFC 974
"Each MX matches a domain name with two pieces of data, a preference value (an unsigned 16-bit integer), and the name of a host."
The important part of this is the "....and the name of a host."
The following is an example of an illegal DNS entry per RFC 974 for the domain 'example.com':
example.com. IN MX 10 192.168.1.1
The above is illegal because '192.168.1.1' is not the name of a host, but rather an IP address.
In order to send your email to a host (mail server) located at IP address 192.168.1.1 you would do the following:
example.com. IN MX 10 mail.example.com.
mail IN A 192.168.1.1
When you modify the routing for email you typically do so by adjusting the mail exchange or "MX" record.
Per RFC 974
"Each MX matches a domain name with two pieces of data, a preference value (an unsigned 16-bit integer), and the name of a host."
The important part of this is the "....and the name of a host."
The following is an example of an illegal DNS entry per RFC 974 for the domain 'example.com':
example.com. IN MX 10 192.168.1.1
The above is illegal because '192.168.1.1' is not the name of a host, but rather an IP address.
In order to send your email to a host (mail server) located at IP address 192.168.1.1 you would do the following:
example.com. IN MX 10 mail.example.com.
mail IN A 192.168.1.1