Order a VPS, Semi- dedicated or Dedicated server in Dallas, London or Australia.
Ask our support team about your hosting requirements.
Host where the staff takes pride in making customers happy
Thanks a million for your help. Having dealt with other hosting providers who a) don't have a clue or b) don't have (or make) the time to help or c) just ignore you, it really is a breath of fresh air to get so much help. Frankly, I am astonished by how much you give for such a reasonable price. And you can stick that on your web site ;-)
MX records
To run a 'public' mail service you need to have a DNS MX record. This is used by other mail servers to decide what the hostname is for the server that looks after email for your domain.
The references standards that DNS servers conform to are at ...
When you set up an MX record, it should have the form
<yourdomain.com> MX 0 <mailserver domain name>e.g.
example.com MX 0 example.comWhere the number is the priority assigned to that mail server. If the lowest numbered server is not available, then sending should default to the next if it exists.
MX and CNAME records
When a general query is sent to a DNS server, most will reply with a CNAME record first and *might* try to resolve that to an IP address before referring to an A record.
So if you try to use a MX to a CNAME record, you may see some very odd results. Basically its a bad idea, and here's why...
Most mail servers will not check that the MX record they receive resolves all the way to an A record. Instead they will just take the domain name attached to the MX record for granted and apply that to headers for sent emails. Which will mean reverse lookup checks will fail unexpectedly, and your emails may either bounce or be delivered into the void.
The solution to this is to make sure that mail server domain names point to an A record.