Yesterday I reported about local DNS problems happening everywhere in the world lately. I am talking about the underlying service that tells your web browser where the server for a webpage is located.
I did not even notice until my blog suddenly disappeared from the Internet. Luckily this was just from my perspective. 99.2% of my regular visitors did not notice any problem accessing my blog.
And as of today, Telefonica, the large ISP operating in Europe and South America, servicing millions of customers with usually quality low- and high-speed internet access has fixed the problem.
This is truly a misleading statement, because most likely the problem has fixed itself. What I mean is that the Domain Name System guarantees that all changes are replicated throughout the globe within a maximum of 48 hours.
I know we have been spoiled with the way .com top level domains for example are set up nowadays, which is, you register a new .com domain and it will be accessible in huge portions of the globe within minutes or a few hours.
However, if a network administrator of an internet access service provider (ISP) messes up the DNS configuration by accident it can take up to 48 hours till the system is fully operational again. That's inherent with the IT/network architecture in use. Nothing or very little one can do to speed things up.
Again, my blog can be reached “normally” again without using any DNS magic tricks, which I wrote about yesterday.
Business Strategy Lesson - Repeated
I used this as an opportunity to write the article, How Safe Is Your Web Business?, stating that once your business is rolling and bringing in money, you should spend some effort to build redundancy and diversify your income streams, remove bottlenecks, single points of failure, and so forth, …
Only because you have the “Hacker Safe Logo” legitimately on your Web site doesn’t mean your web-based business is 100% safe.
Your site doesn’t need to be attacked by criminals there are many different possibilities for having your web based income stream disrupted. Now I remember that I wrote about the subject of protecting your virtual assets back in December 2007, too.