Can't access only one site, OpenDNS resolves wrong IP

[matteck]

Hello:   I made some changes to a website I own, and that was 24 hours ago. The site comes up on every computer not using Open DNS.  If I change to google DNS, it comes up fine.  When I go back to Open DNS (flushing browser cache and doing ipconif /flushdns) I get the following error "The servers that run hannaheckman.com are having some trouble. This is usually just a temporary problem, so you might want to try again in a few minutes". 

When I do a NSlookup, I get a different IP address with OpenDNS servers than what I get with any other DNS server I use in the  NSlookup tool.  Any ideas? 

Here is my report: http://opendnsupdate.appspot.com/d/23762002

Thanks, Matt from Michigan USA.

[ahoncian]

Hello,

I've double-checked the IP address for hannaheckman.com and our resolvers are currently pointing to 

50.62.216.1. 

To ensure that OpenDNS is working properly for you, please flush your browser and DNS cache by following the instructions below:

http://www.opendns.com/support/article/67
http://www.opendns.com/support/article/68

Please let us know if you're still experiencing difficulties with this and we'll be more than happy to help you.

Best regards,

[matteck]

I have done that  multiple times on multiple servers.  Yet when I go and to a NSlookup, it shows I'm using 208.67.222.22, and resolves Hannaheckman.com to be "non-authoritative answer 67.215.66.132". 

When I go to this site http://www.opendns.com/support/cache, , I get the number 50.62.216.1.  So I'm trying to figure out how my local computer is coming up with this 67.215.66.132 number when I use nslookup in CMD.  Could it be from my router or something?  It is happening both at home and at work, and I have flush dns multiple times and cleared browser cache.

[rotblitz]

"Here is my report"

Nobody can see this except OpenDNS staff.

"When I do a NSlookup, I get a different IP address with OpenDNS servers"

Me not:

nslookup hannaheckman.com. 208.67.220.220
Server:  resolver2.opendns.com
Address:  208.67.220.220

Nicht autorisierte Antwort:
Name:    hannaheckman.com
Address:  50.62.216.1

"resolves Hannaheckman.com to be "non-authoritative answer 67.215.66.132"."

This is hit-servfail.opendns.com and could indicate a problem with the DNS configuration of your domain.  But I can't find any.

http://www.dnsstuff.com/tools#dnsReport|type=domain&&value=hannaheckman.com

[matteck]

The site started working, and I really don' t know why, but now it reads back the proper IP number.   I would say that it just took longer for DNS to update from my registar, except that OpenDNS rep Anthony Honcian stated above that he was getting the proper Ip address of 50.62.216.1.  So I guess I'll never know why I was getting the .37.215.66.132 number! 

[rotblitz]

"it just took longer for DNS to update from my registar"

Ah, this is new information!  So, you also made DNS changes?  You said "I made some changes to a website", and this does not include DNS changes.  If you did make DNS changes, then it clearly takes a while to propagate over the internet, although your current TTL is just an hour, but may have been much longer before.

"So I guess I'll never know why I was getting the .37.215.66.132 number! "

Wasn't it 67.215.66.132?  As I said above, this is a DNS SERVFAIL response à la OpenDNS.  There was conflicting DNS information/misconfiguration during propagation.

[matteck]

I'm sorry, I typed that wrong.  It was reading 67.215.66.132?, not 37.215.66.132. 

But yes, you are right I should have mentioned that the site had a NS change that Godaddy wanted us to make with the Registar, but I did not think it was a propagation problem because the OpenDNS tech rep. above said he was getting the proper IP address when he checked it.  And when I did a check the OpenDNS cache at http://www.opendns.com/support/cache/, it also showed the correct IP address on every server it read back.  So I still don't know why my NSlookup was giving me this 67.* IP address with OpenDNS server, when it appears that OpenDNS had already been propagated correctly according to the cache lookup.