It’s quite hard to understand why it takes even 2 days to have your site working just because you’ve moved your site from one server to another. And this headache is gracefully caused by our beloved DNS servers.
Actually it’s a little bit hard to understand (some people say that we don’t even have this DNS “propagation” thing, since it’s usually TTL caching issue). But let’s stick with a pretty simple explanation that works well for anyone with more than 2 neurons (sorry amoeboid and trolls):
Hosting servers on the internet actually don’t have a really cool name. For example, many of them have a “name” formed by 4 groups of digits, like 74.125.234.50. It’s even worse than “Rochester” isn’t it?
Look, something like 74.125.234.50 isn’t that easy to remember, right? So, that’s why we have things called Domain Name Service servers.
They’re quite smart guys that can remember the “nice name” (google.com) for each “ugly name” (74.125.234.50). So, when you type google.com in your browser, your Internet Service Provider asks DNS “bro, where is this google.com guy is hidden?” and DNS answers “Oh, you meant 74.125.234.50 , right?”.
So far, so good. Now you need to know just one more little thing, since we have several DNS servers over the web, when you change your hosting from company #1 to company #2, each DNS server has to tell his brothers about this change. So while one DNS server thinks that mysite.com is still hosted on company #1, others know that it’s actually on company #2, so a few users won’t be able to see your site in the meantime, depending on the route that they get (which DNS server their ISP ask).
No comments:
Post a Comment