{"id":19776,"date":"2020-07-20T21:04:53","date_gmt":"2020-07-20T21:04:53","guid":{"rendered":"https:\/\/rbsitsoftwaresolution.com\/blog\/why-the-internet-went-haywire-last-week.html"},"modified":"2020-07-20T21:04:53","modified_gmt":"2020-07-20T21:04:53","slug":"why-the-internet-went-haywire-last-week","status":"publish","type":"post","link":"https:\/\/www.rbsitsoftwaresolution.in\/blog\/why-the-internet-went-haywire-last-week.html","title":{"rendered":"Why the internet went haywire last week"},"content":{"rendered":"

It was another end of the workweek; what could possibly go wrong? Sure, Outlook had failed for a few hours earlier<\/a> in the week and Twitter lost control of some big-name<\/a> accounts, but surely nothing else could go awry? Right? Wrong. Bad things come in threes. Starting on Friday afternoon, Cloudflare<\/a>, the major content delivery network (CDN) and Domain Name System (DNS) service, had a major DNS failure, and tens of millions users found their internet services failing. <\/p>\n

Whoops. <\/p>\n

At the time, there was concern that the US internet itself was under attack. The real problem was much more mundane. Cloudflare’s technical support reported:<\/p>\n

\n

“This afternoon we saw an outage across some parts of our network. It was not as a result of an attack. It appears a router on our global backbone announced bad routes and caused some portions of the network to not be available. We believe we have addressed the root cause and monitoring systems for stability now.” <\/p>\n<\/blockquote>\n

Like, I said, whoops. <\/p>\n

There’s an old saying in network administration circles that when something goes awry on the network, “It’s always DNS.” In this case, that’s exactly right. It was DNS. <\/p>\n

Specifically, sites that use Cloudflare DNS hosting and anyone using Cloudflare’s free DNS 1.1.1.1 resolver service were knocked off the web for about half an hour. John Graham-Cumming, Cloudflare’s CTO explained in a blog posting:\u00a0 <\/p>\n

\n

The outage occurred because, while working on an unrelated issue with a segment of the backbone from Newark to Chicago, our network engineering team updated the configuration on a router in Atlanta to alleviate congestion. This configuration contained an error that caused all traffic across our backbone to be sent to Atlanta<\/a>. This quickly overwhelmed the Atlanta router and caused Cloudflare network locations connected to the backbone to fail. <\/p>\n<\/blockquote>\n

The error consisted of a single line of configuration code, but that was more than enough. Instead of removing the Atlanta routes from the backbone, a tiny change started leaking all Border Gateway Protocol (BGP)<\/a> routes into the backbone. BGP is the standardized exterior gateway protocol used to exchange routing and reachability information between the internet top-level autonomous systems (AS)<\/a>. Average users never deal with these.<\/p>\n

\n<\/section>\n

We ordinary mortals do, however, work with DNS all the time even if we’re not aware of it. DNS is the internet’s master phonebook. Whenever you type in or click a human-readable web link (such as zdnet.com<\/a>), your web browser calls on a DNS resolver to resolve its corresponding Internet Protocol (IP) address. <\/p>\n

DNS is not just for browsers, though. If it runs on the internet — Slack, email, you name it — DNS works behind the scenes to make sure all the application requests hook up with the appropriate internet resources. Whether a website, email link, or FTP site, it has an IPv4 address or its IPv6 address equivalent, and the 13 DNS master root servers<\/a> track them all. These authoritative DNS servers hold the addresses for every internet-connected device in the world. DNS is essential. Without it, there is no internet. Period.\u00a0<\/p>\n

And, when DNS goes wrong, especially at a high-level, the result, as we just saw last week, is a near-complete work stoppage. Fortunately, such failures are rare. <\/p>\n

Related Stories: <\/strong><\/p>\n