> Right now, the MX record for the-bob.org is cricket.the-bob.org, with
> a value of 10. I just deleted it to see what happens when there's no
> MX record, but I thought you needed to have one for a domain that was
> going to receive mail.

This is a common misconception.

You DO NOT need a MX if the machine that the-bob.org points to also
handles mail.

MX records are only used if you wish to have one machine handle, say,
web, for the-bob.org, but not mail.

Let's say that you've got two machines - banana.example.net, with an IP
of 192.168.1.10 and orange.example.net, with an IP of 192.168.1.20.
(Pretend that those aren't private address blocks.)

If you have an A record for banana.example.net, pointing to
192.168.1.10, an A record for orange.example.net pointing to
192.168.1.20, and an A record for example.net pointing to 192.168.1.20,
you don't need a MX record - as long as you want orange.example.net to
handle the mail for example.net

However, if all of the above remains the same, but you want banana and
not orange to handle mail for the domain, then you need a MX pointing to
banana.example.net.

For a better explanantion, read
http://support.dyndns.org/whitepapers/mail.php. It's for users of
DynDNS services, but the principles are applicable to everyone.

-Sunny Raspet

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]