Problem with verifying mailgun MX DNS

Hello Community,

I’ve decided to use Mailgun as my mail service provider, but I’m meeting one problem. The problem is setting mx dns records to use their routes system, so i can forward my inbound mails to my email.

My DNS look like this for now: $ORIGIN $TTL 1800 IN SOA 1462529965 10800 3600 604800 1800 1800 IN NS 1800 IN NS 1800 IN NS 1800 IN A 1800 IN CNAME 1800 IN A 1800 IN A 1800 IN A 1800 IN A 1800 IN CNAME 1800 IN TXT “v=spf1 ~all” 1800 IN TXT “k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC6M7JKhr7xUaj4bUxKFCYNCAcNU3q2GSoveoORB2J4UzQrxWuMTMTY6egRWLwNsCxHGtiMXv0JFa4t5T2cYVeGF2q0AMBOCx+UJ4kMOF8tsuzTEcPatLN8YsYYSCxpX/iPr89Gvwjq57JpMkfJAIs1hbC7/2IQh1pdDEQzyszvvwIDAQAB” 1800 IN MX 10 1800 IN MX 10

But mailgun still can’t see MX values even after 48h.

Somebody can help?

I’d be grateful.

Show comments

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

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.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

This question was answered by @jschwenn:

In this scenario, you would create a second domain zone just for ‘’ and use it for the purpose of setting MX records to this subdomain.

View the original comment