2 days ago, I applied a domain gtscomputers.com.au, and then changed the nameserver to the one from my hosting, and change all "A Record" to the IP

Yesterday, I applied another IP address and changed all "A Records" to the new IP, this morning the domain has been pointed to the new IP.

However, when I tried to access the website tonight, it has been point back to the previous IP address

I'm using (Google DNS) on my PC, and after I change to ISP's DNS, the website is pointed to the new IP which is correct, because this DNS has not been updated yet.

Can anyone tell me what's going on? I have checked all DSN settings.


The time to live (TTL) value for your domain name system record tells nameservers how long to cache the old data - unless you explicitly set a low TTL, nameservers will likely respond to DNS lookups with the last cached data until the TTL expires.

  • The strange thing is that this morning, the has pointed the domain name to the new IP address. – Stewart Hou Dec 7 '10 at 13:51
  • Use dig and dig @server for troubleshooting if you see the problem recur - hard to isolate the source of the problem otherwise. linux.die.net/man/1/dig – danlefree Dec 7 '10 at 16:22
  • 1 is an anycast address: it is actually a service comprised of a whole bunch of servers sprinkled throughout the world. You can and will get different results from subsequent queries to Google DNS, depending on the cache status of the particular server you hit. It is not surprising that you would see differing resposnses during a DNS change. – rmalayter Mar 21 '11 at 4:01

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.