The point would largely boil down to being a good citizen and reducing abuse, like making your domain less useful for spammers to impersonate and to make it immediately clear to others that mail is not deliverable there. If the claim is accurate that the domain is not used for either sending or receiving email … Read more
To make things nice and clear, as some of the GoDaddy help articles are dead wrong: You just need to paste the two records from the server settings into your Route 53 control panel as a new record. The possible deception here is the the GD email panel will tell you you’re wrong, but not … Read more
While you can set up more than one MX server for a given domain, this is purely a backup function to specify another server to receive mail when one server goes down. It’s not possible to let two totally different services both handle your mail for the same domain, and IMHO it doesn’t make any … Read more
Unfortunately, what you’re running into is a limitation of the DNS specification. Having an MX record for the same hostname as is defined as a CNAME record will fail in most DNS server implementations. Some older DNS servers will allow this, but they have been mostly phased out in favor of newer, more secure implementations. … Read more
They are mostly wrong. It is not a bad practice to have more than one MX, and it’s equally not a bad practice to have one or more of them with a hostname in another domain. In fact, it used to be quite common that people would set up their own mailserver in their own … Read more
As long as the system pointed at by the MX record has an A record itself, then yes. For example: example.com can have a MX record pointing at mail.otherdomain.com. As long as the name mail.otherdomain.com itself is resolvable to an IP address, this is a valid configuration for example.com. Strictly speaking, mail.otherdomain.com should be an … Read more
I can vouch for #2 (reverse PTR) being important, but not #4 (mail server domain matching “from”). We set up mail servers all the time, and most mail hosts don’t really even care about #2. The main thorn is always AOL, and they list standards you can check off.
http://whoisrequest.org/history/ This one is really cool . No registration needed .
This is a common error. You cannot use a CNAME RR for your root domain (e.g. company.com) and define additional resource records for the same zone. See Why can’t I create a CNAME record for the root record? and RFC1034 section 3.6.2 for details: If a CNAME RR is present at a node, no other … Read more
The whole idea behind the MX record is to specify a host or hosts which can accept mail for a domain. As specified in RFC 1035, the MX record contains a domain name. It must therefore point to a host which itself can be resolved in the DNS. An IP address could not be used … Read more