Mailgun Is Not Detecting My New MX Records
- by Tyler Crompton
When I issue a DiG command to verify my MX records, I get the following output:
$ dig example.com MX
; <<>> DiG 9.9.5-3-Ubuntu <<>> example.com MX
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 47700
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 5, ADDITIONAL: 5
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;example.com. IN MX
;; ANSWER SECTION:
example.com. 85468 IN MX 10 mxa.mailgun.org.
example.com. 85468 IN MX 10 mxb.mailgun.org.
;; REMAINDER OF OUTPUT REMOVED FOR BREVITY
However, when I click "Check DNS Records Now" on Mailgun, it verifies the changes to the TXT and CNAME records but says that my MX records have not been changed.
Type | Priority | Enter This Value | Current Value
-----+----------+------------------+--------------------
MX | 10 | mxa.mailgun.org | 10 mail.example.com
MX | 10 | mxb.mailgun.org | 10 mail.example.com
I updated these records three to fours ago. I know it said to wait up to twenty-four to forty-eight hours. But I feel that if it detected the other DNS changes, then it should detect the MX record changes. Am I being impatient or is this a legitimate concern? What do you suggest I do?
Note: I'd create a Mailgun tag for this; I feel that it'd be appropriate, but I don't have enough reputation to do so.
