Originally Posted by
Voodoo
Thanks bud! :wub:
Thank you for the info. It seems this is becoming a trend. However, I'm 99% sure this is DNS-related. Although the URL works for most, some sort of local caching is causing that URL to not point to the correct server for some users.
Think of DNS like an infection. Every domain name (google.com, thegalantcenter.org) has a "name server" associated with it. Whenever that domain name is typed into a web browser, two requests are made. First, the user's computer tries to resolve the IP address that corresponds to that domain name (imagine trying to contact someone you know by name but you don't have their phone number, so you have to look it up first); it does this by looking in a local cache or by asking a "name server" for the IP (usually provided by your ISP, think of this as "the operator"). Once the IP address has been resolved (once you know the phone number), the user's computer then makes another request directly to the website server to download the webpage (you call your friend).
Changes made to DNS information begin at the website. There are many DNS "name servers" in between your computer and the website that all store/cache information, and they must each update their own records. Imagine, your friend changes his phone number, but you have to wait for the next phone book to be published so you can look it up.
Typically, the further you are from a website, the longer it will take for you to see DNS changes take effect.