Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Ok, this should be straight forward and I'm ashamed I haven't been able to figure this one out for myself, but...

I've recently discovered Amazon Route 53 DNS services and I'm now using this for the domains which I manage. In order to sanity check my MX records, I use to show the MX records and run a quick SMTP check on each MX server.

Here's an example of one of the domains in Route 53:

Route 53

However when I try to run the query on, I am [what seems to be] redirected to the query results for and the MX records are not returned:

Example query Example result

So I check from command line:

$ dig MX +short

Which confirms that the MX records are present.

If I query MX servers for, behaves correctly:

So it appears that it's only my domains that are not returning valid MX records to MXToolBox, at least.

Does anyone have any ideas why? Does the above work correctly for anyone else using Route 53 for their DNS?

share|improve this question
To confirm, the URL I am using to check from is:… – MasterRoot24 Dec 1 '13 at 21:09
up vote 2 down vote accepted

Looks like a bug with mxtoolbox. This happens on all, ... domains. I guess it doesn't like TLDs with two fields. You can check with,,, you always get an A record.

share|improve this answer
Great! Why didn't I think of that? :) I've opened up a thread on the forums so hopefully they can fix this.… – MasterRoot24 Dec 1 '13 at 21:48

Did you recently change your records? You may need to wait for the TTL to expire on the previous records. They are reporting correctly for me. mail is handled by 10 mail is handled by 15
share|improve this answer
The domain has been running on Route 52 for approx. 1 week, so MX records have been present on there for some time, hence MXToolBox should return some MX records. Furthermore, MXToolBox queries the name servers for the domain directly, so any changes to MX records in Route 53 should show up pretty much straight away from queries performed my – MasterRoot24 Dec 1 '13 at 21:15
Also, I'm aware that the host command is returning MX records for the domain, as you have pointed out, hence I included the output of dig in my original question. Thanks for confirming this from another location, though. – MasterRoot24 Dec 1 '13 at 21:17
This seems to be some bug at mxtoolbox, because it seems to be happening on ALL domains. Try for yourself with, or whatever... – etagenklo Dec 1 '13 at 21:29
Same problem with domains... – etagenklo Dec 1 '13 at 21:31

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.