mikeshaver
asked on
MX records incorrect on Dnsstuff.com, but are correct everywhere else?
I am using Godaddy.com to host websites and DNS records for a number of sites.
Tests are being done at dnsstuff.com
Every site I have is configured to use the same FQDN of our single mail server.
When you perform a dnsstuff.com "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 DNSStuff.com
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.
Tests are being done at dnsstuff.com
Every site I have is configured to use the same FQDN of our single mail server.
When you perform a dnsstuff.com "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 DNSStuff.com
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.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Non-authoritative answer:
<domain name>
primary nameserver = ns51.domaincontrol.com
responsible mail addr = dns.jomax.net
serial = 2008100200
refresh = 28800 <8 hours>
retry = 7200 <2 hours>
expire = 604800 <7 days>
Default TTL = 86400 <1 day>
<domain name>
primary nameserver = ns51.domaincontrol.com
responsible mail addr = dns.jomax.net
serial = 2008100200
refresh = 28800 <8 hours>
retry = 7200 <2 hours>
expire = 604800 <7 days>
Default TTL = 86400 <1 day>
ASKER
Just checked again...been 40 hours now and its still incorrect at dnsstuff.com...and some clients cannot send email to this domain...yet others can without issue.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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!?
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!?
ASKER
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.
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.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Issue resolved
ASKER
I've been typing this:
nslookup
server=ns51.domaincontrol.
(but then it searches for a domain called server=ns51.domaincontrol.
?