MX lookup doesn't work on FQDN

Posted February 5, 2015 4.4k views

Hi all,

I’m setting up a mail server on an Ubuntu droplet. I had to change the droplet name to the fqdn per some other threads on this forum.

droplet name:

dig MX returns the mx:

dig MX +short @
dig MX +short @

Does not return anything.

In Ubuntu,

hostname returns mail
hostname -d returns
hostname –fqdn returns

In the DigitalOcean web gui, under I can see the records.

MX 0

When I use on mx, I get back “No mx Records exist”
If I query mx I get back:
Pref Hostname IP Address TTL

0 {No A Record} 30 min

So it’s like the mx record doesn’t work with the fqdn, but only the domain.tld

Any ideas on how to fix?

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Submit an Answer
5 answers

There’s nothing to fix. That query shouldn’t return anything.

EDIT: There’s a message which seems to indicate you may be missing a record, but since you censored your domain name there’s nothing we can do to verify if that’s true or not.


Thanks for the reply back too. It just seemed like I should get a record back when asking for the mx for the fqdn.

edit 2: My zone file (visible in the DO gui) lists an A record in it: 1800 IN A

So not sure why mxtoolbox says there is no A record.

  • Okay, so with the domain at hand we can see that there is no A record for your MX entry, which is vps is correct - you should add that record.

You need an A record for “”.
In DO control panel add an A record Should end up looking like your A record 1800 IN A

I added the A record and mxtools completes the lookup for the domain.tld

Thank you for the follow ups!

Overall, it was my error on thinking the mx lookup should also work against the fqdn. Thanks again!