<span id="hs_cos_wrapper_post_body" class="hs_cos_wrapper hs_cos_wrapper_meta_field hs_cos_wrapper_type_rich_text" style="" data-hs-cos-general-type="meta_field" data-hs-cos-type="rich_text" ><p>Sometimes it takes a major, sudden, shock to make people see the obvious. The recent Facebook outage, on its own, was a pretty big deal. When one of the largest companies, with thousands of the best engineers, could take itself offline for 8 hours, what is the hope for the average company? The details of <a href="https://blog.cloudflare.com/october-2021-facebook-outage/" rel="noopener" target="_blank">how it happened</a> are arcane, but it boils down to "<span style="font-weight: bold;">It's always the DNS</span>".</p> <h2><span style="font-weight: bold;"><!--more-->Why </span><span style="font-weight: bold;">is </span>DNS Always Involved?</h2> <p><span style="font-weight: bold;">The Domain Naming System (DNS) is like a phonebook for the internet.</span> Each device connected to the internet has its own unique IP address. Since websites are hosted on these distributed devices (web servers), they are located on a specific IP address. DNS translates domain names used by humans (like threatstop.com), to the machine-friendly IP addresses that services are hosted on. This technology lies at the core of the internet, so when DNS stops resolving for some reason - things go downhill. Fast.</p> <h2>Why Outages Will Keep Happening</h2> <p>The recent Facebook outage wasn't an isolated incident, it wasn't the first time, and won't be the last time DNS will be the cause of massive outages for the products and services we use daily. Just a few months ago, a big chunk of the internet went offline due to a <span style="font-weight: bold;">DNS issue at Akamai</span>. Popular services that rely on Akamai's Edge DNS service included <span>UPS and FedEx, Airbnb, Steam, LastPass, and the PlayStation Network, all of which went down in an instant. And that's not all - <span style="font-weight: bold;">Cloudflare suffered a DNS outage</span> during the summer as well, breaking access to Shopify, Discord and Politico.</span></p> <h2>DNS is a Frequent Target for Attackers&nbsp;</h2> <p>Aside from the common name server configuration and server issues, some DNS-based fallouts happen as a result of targeted cyber attacks. Dyn, a large DNS provider, became victim to a DDoS (<span>Distributed Denial-of-Service) attack that took down its DNS services for 12 hours. The result - Amazon, Twitter, Netflix, and another 60+ sites fell across the U.S. and Europe. The underlying infrastructure of the Internet, like plumbing and piping under a city, is brittle and subject to catastrophic failure through abuse, mistakes, and being overwhelmed by the billions of devices and users that depend on it.</span></p> <h2>The Solution? Host Your Own DNS!</h2> <p>Losing Netflix for a few hours when you want to binge a new show is annoying, but having services that your company needs go down could be company-ending. So if there's always an outage right around the corner, <span style="font-weight: bold;">what can you do to keep yourself connected when services are falling off the internet? </span></p> <p><span style="font-weight: normal;">Facebook and other gigantic internet services are monopolies, but you can <span style="font-weight: bold;">take the control into your own hands with an in-house DNS.</span> This way, you get g</span>reater <span style="font-weight: bold;">availability, visibility and control</span> of the traffic coming in and out of your network.</p> <h4 style="font-weight: bold;">1. Availability</h4> <p>When hosting your own DNS, you still have the external ones to fall back on, so having both is a fool proof solution that won't leave you DNS-less. In case an upstream ISP pushed the wrong button and took down their own DNS servers, no sweat - your own DNS resolver springs into action seamlessly. And there's&nbsp; no action required of you, and no downtime for your employees or apps. In fact, local DNS can offer performance advantages by caching responses.</p> <h4 style="font-weight: bold;">2. Visibility</h4> <p>The ability to find individual infected hosts and remediate them is critical. Most managed DNS solutions remove your ability to identify the private IP or hostname of a device making harmful DNS requests, and that makes pinpointing machines for remediation really tricky. To keep the network clean, you MUST be looking at enriched logs through a reporting mechanism.</p> <h4 style="font-weight: bold;">3. Control</h4> <p>Define the things your business considers "bad stuff", and stop those things things faster. Do you have customers in China? Would you like to block all DNS requests going there? Security policy and traffic enforcement can, and should, look strikingly different from one company to the next.&nbsp;</p> <h2>&nbsp;</h2> <h2>Summary</h2> <p>Your business relies on keeping your network up and running, and secure. Hosting your own DNS achieves both goals. And it's easier to do than you might think. Add in the fact that it's a zero risk move, and adding an in-house DNS is an easy objective to achieve, so why delay?</p> <p><span>At ThreatSTOP, we live and breath DNS.&nbsp;</span><span>ThreatSTOP's DNS Defense is a unique, highly adaptive Protective DNS service that stops threats early, before they cause damage.&nbsp;</span><span>Powered by continuous updates from 900+ Threat Intelligence sources, the platform knows and tracks the infrastructure used by cyber criminals to conduct attacks, and keeps network devices updated to block or redirect malicious and unwanted DNS requests.</span></p> <p>&nbsp;</p> <p><em>Want to learn more? Interested in how ThreatSTOP can stop attacks on your network?</em></p> <p><em></em></p></span>