MX records incorrect on, but are correct everywhere else?

I am using to host websites and DNS records for a number of sites.
Tests are being done at

Every site I have  is configured to use the same FQDN of our single mail server.  
When you perform a "dnsreport" the same FQDN will report 2 DIFFERENT IP addresses.  
All of my sites but 1 report the correct IP address and FQDN of the mail server.  

I contacted GoDaddy as this appeared to be a certain DNS problem on their end.  I ended up getting someone who knew what I was talking about and he advised that they had a "blown zone file" on the DNS server.  He said he was going to reload it, and I should be good in an hour.  Its been 30 hours now...and nothing has changed over at

I then used nslookup to query the nameservers listed at godaddy for the FQDN of the mail server.  They are correct at Godaddy...but aren't updating whatever DNS servers dnsstuff uses for themselves.

Also, some domains are having trouble sending email to the domain in question.

Most DNScheck sites on the web indicate the correct name/ip...but some do not.  

Is 30 hours not long enough to wait for propogation when the zone file is bad and their tech was mistaken when he said about an hour?  Or is there something worse going on here...?

Tips appreciated.
Who is Participating?
mikeshaverAuthor Commented:
I have resolved this by creating a replacement A record (with a different name than the incorrectly resolving one.  And of course pointed it to the correct IP.

Not sure why DNSStuff was reporting the wrong IP...but the above (although not optimum) has resolved the issue.

Thanks for everyone's comments.

30 hours is too long.  I use GoDaddy for some stuff and their TTL is usually only about 15 minutes.  Whatever changes they made should have been reflected pretty quickly.

You can verify the TTL.  Run nslookup and connect to the godaddy servers (like you did when you checked the mail server information).  Set the type to SOA and then query your domain.  If the default TTL is less than 108000 (30 hours in seconds) theres another problem.  if it is too high, you should be able to set the TTL much lower, but unfortunately the setting wont take effect until after the TTL expires.
Also... It could be the "blown" dns file had a malformed TTL.  You could query the SOA record for your domain from various other DNS servers and see what they have on record.
WEBINAR: 10 Easy Ways to Lose a Password

Join us on June 27th at 8 am PDT to learn about the methods that hackers use to lift real, working credentials from even the most security-savvy employees. We'll cover the importance of multi-factor authentication and how these solutions can better protect your business!

mikeshaverAuthor Commented:
Can you give me the commands to do the SOA verification from nslookup?

I've been typing this:
nslookup  (the primary nameserver on the domain in question)

(but then it searches for a domain called

Let's try

Open your command prompt and run nslookup.  It will initially connect to your DNS server.
type 'server' to connect to
then type 'set type=soa' to change to the soa query.
now type your domain name.  a few rows should result but look for either Default TTL or Minimum.  That's the length of time a DNS server will cache an entry before it bothers to look it up again.
mikeshaverAuthor Commented:
Non-authoritative answer:
<domain name>
primary nameserver =
responsible mail addr =
serial = 2008100200
refresh = 28800 <8 hours>
retry = 7200 <2 hours>
expire = 604800 <7 days>
Default TTL = 86400 <1 day>
mikeshaverAuthor Commented:
Just checked again...been 40 hours now and its still incorrect at some clients cannot send email to this domain...yet others can without issue.
I'm kinda running out of ideas...  when you log into your account at GoDaddy you can verify everything is configured correctly?  Would you mind providing the name of one of the domains?
mikeshaverAuthor Commented:
Me too.  Everything at Godaddy is right.  When you query their nameservers using nslookup, everything resolves correctly.  

It gets worse.  I made a new MX record for the domain and pointed it to the correct IP.  That worked, and DNS stuff showed the correct IP.  So I removed the old (incorrect IP) MX record.  That was about 4 hours ago.  I just checked at DNSstuff again, and now the newly created MX record is once again displaying the incorrect IP (but it showed up correctly a few hours ago!).

It seems that GoDaddy is perhaps propogating the wrong info...but when you query their name servers...its all correct!?
mikeshaverAuthor Commented:
I've made some changes.  I created a brand new A record on the destination domain.  

I pointed this A record to the correct IP of the mail server.  It seemed to work and propogate correctly for the last 6 hours.

So I added back in the "offending" mail server with a priority of 50.  As of right now, its showing the correct IP.  If it stays until morning...perhaps the issue is resolved.  If the secondary MX (pointed at the correct IP) reverts back to the odd/incorrect IP I think I will just nuke the secondary record and leave only the new primary one.  It will be different than every other one of our sites, but at least it appeared to be working.

I will report back in this thread.

I'll report back with results later tonight.
mikeshaverAuthor Commented:
Issue resolved
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.