• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1301
  • Last Modified:

NS Lookup does not find MX record

My client created a domain on Whois.com and asked me to set up the email. I created an A record (mail.mydomain.com) pointing to an exchange server on our domain. I then created an MX record for .mydomain.com pointing to the new A record.  We waited 24 hours. The mail did not flow all mails were bounced tjat were addressed to Jane@mydomain.com.

I did an nslookup on the MX record:

Default Server: ServerName.comcast.net
Address: xx.xx.xx.xxx:53

>Set type=MX

Server: ServerName.comcast.net
Address: xx.xx.xx.xxx:53

           primary name server = root
           responsible mail addr = abuse.opticaljungle.com
           serial = xxxxxxxxxxxx
           refresh =28800
           retry = xxxxx
           expire = xxxxxxxxx
           default TTL =1

All other mx records I enter for exchange servers I have set up return:

Server: Comcast server name
address:  IP address:53

Non-authoritative answer:
domain.com MX preference =10, mail exchanger = domain.com

Any ideas why this mx record is not working?
  • 2
  • 2
1 Solution
Technically speaking 24hrs is way too less, you are expecting a global DNS replication to take place within 24hrs. Ideally you should start troubleshooting only after 72 hrs of the time you set up the MX record on the internet, until then you should simply pray that the MX gets hosted and starts working for you.

I have seen cases where MX record starts working after 96hrs even, however industry standards state 72hrs is appropriate.
sarasotabAuthor Commented:
Ok, I guess we can wait and see, but I have set up many MX records and they usually work within 24 hours.  You may be right though.  I subsequently noticed that Whois.com is Singapore based, so there may be a larger delay than using Network Solutions and having the record propagate in the US only which is where all my client's email comes from.  Thanks, I will let you know if waiting works

sarasotabAuthor Commented:
Ok, I got the answer after a lot of hunting around on one of the worst websites for DNS management I have ever seen.  The name servers assigned by default by Whois.com are "Parking" servers and do not propagate changes.  I had to change the name servers on the account to make dns management work.  
@sarotsab: You mean email flows over A record and all those blogs / MS documentation talking about MX record are baseless ????

Featured Post

SMB Security Just Got a Layer Stronger

WatchGuard acquires Percipient Networks to extend protection to the DNS layer, further increasing the value of Total Security Suite.  Learn more about what this means for you and how you can improve your security with WatchGuard today!

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now