how can i fix this?
[edited by: Webwork at 8:38 pm (utc) on May 21, 2007]
[edit reason] WebmasterWorld TOS and Domain Forum Charter [/edit]
I did a DNS query on my site
Which DNS server(s) are you querying? Those authoritative for your site, or one of your ISP's servers? Your ISP's server could be caching DNS records.
Did you recently update your DNS? How long ago? Did you reduce the TTL before the changes?
i have changed my nameservers in my godaddy registrar account several weeks ago....
the TTL originally was only 48 hours...
i did a query at the site DNS REPORT dot com, which is through an ISP where i can access my site via www.mysite.com, and noticed that my current server has this
"SOA EXPIRE valueOK.
Your SOA EXPIRE time: 1209600 seconds. This seems normal (about 1209600 to 2419200 seconds (2-4 weeks) is good). RFC1912 suggests 2-4 weeks. This is how long a secondary/slave nameserver will wait before considering its DNS data stale if it can't reach the primary nameserver."
If my current DNS server has this for my site, couldnt any top level DNS server have an SOA record for my old site that will be in there for 2-4 weeks?
Thus, some DNS servers got my new SOA record from my new hosting company maybe after a refresh, and some DNS servers have an Expire time of my site for up to 4 weeks..?
Did i understand and correlate that correctly?
SOA EXPIRE is how long your secondary (slave) nameserver(s) will wait if they can't reach the primary (master) before they consider their DNS data to be stale.
The DNS servers I manage have their SOA EXPIRE set to 604800 seconds (1 week) which means if the master DNS server dies, the slaves keep serving records for a week before they give up.
You **want** this setting to be reasonably long - it gives you time to repair the master server if it fails. If you set SOA EXPIRE to 5 minutes then your slaves would stop working 5 minutes after your master if your master were to fail. This is definitely not what you want :-)
The TTL values you set on your resource records are an indication of how long those records may be cached. Note that an ISP or any intermediate DNS server may choose to cache your records longer than this, this bends the rules but remember they're much more worried about their bandwidth bills than your stale DNS records.
Without giving the specifics of the nameservers, can you tell us whether your using your ISP's nameservers, third-party nameservers, or your own nameservers? Can you describe in general terms what the changes were?
We decided to scrap that plan and get basic hosting for www.oursite.com Once development was complete on the new hosting company, i switched the name servers in my go daddy account to point to the new hosting companys servers...ns1.newhost.com, ns2....etc.
So yes, i am using the name servers of the new hosting company.
Then i had the Mac Mini shut off and sent back to me.
Somehow, as i am sitting right here at an office, just did a query...the old IP address is still coming up as where my site is....and its not.
Its been over a month of this....its freaking pissn on me and so is my client.... im losing traffic and customers becuase somewhere i screwed up the process or someones DNS server is acting funny...
[edited by: tedster at 5:30 pm (utc) on May 23, 2007]
[edit reason] remove specific IP address [/edit]
Here is what i am guessing.... becuase if i didnt mention i can access my site from home just fine with ISP "one" (lets say), my downtown office just fine with ISP "two", but a remote offfice in a subdivision with ISP "three" does not work.
Sounds like an Upstream Caching issue. It may require that your provider put in a trouble ticket to the primary provider.
I'll assume that you've double checked everything in the GoDaddy interface to make sure all is in order with the name servers?
