Rawwwrrrrrrrr ~~~~~~~ !! This site is finally up and running again
beh tong nia... I can't believe my lame ISP really took 72hrs to update their cache for DNS records ! Last week, my webhosting company actually planned to do some RAM upgrades for the server. Then in the middle, I'm sort of confused, but I think they moved some of the accounts to another new server/datacenter in US. So new server means new IP address. That also means http://ahkuan.com is pointing to another new IP address. The changes is made effective pretty quick in the top registration database and the webhosting's DNS servers, however, the so called
DNS propagation process is causing all the mess around.
Let's go in plain english... You see, every ISP cache the master DNS records and read them locally instead of looking them up on the Internet each time someone wants to view a website. Some ISP fetch a new copy once every 24 hrs. However, some ISP (like the one that I'm using) they fetch a new copy once every 72 hrs... or even longer ! So even though the domain name ahkuan.com is already mapped to a new IP address in the top level domain servers, but your ISP's DNS cache is still pointing to the old IP address ! So there will be chaos... some will be viewing the most updated content on the new server but some will still be visiting the old content on old server. Unless everybody is using pure IP address xxx.xxx.xxx.xxx instead of ahkuan.com, you'll probably have to wait up to 72hrs until your ISP refresh their DNS records cache.
It won't be surprised if you're still having problem to resolve to the correct address even after your ISP updated the cache. The problem might be your operating system is caching its own copy of DNS records. For windows user, go to command prompt, and type the following command:
This will flushes and resets the contents of the DNS client resolver cache. Try
/displaydns to display the cache content.
