Is your fav website down? Want your privacy back? Try this one quick trick.
Sometimes, when your favorite websites go "down," they're actually still right there. You just can't see them, because your computer doesn't know the route.
What if you could give your PC some better driving directions right now, in just a minute or two tops? What if this trick improved your privacy too?
To do that, you just need to change your DNS server.
"CNET.com" is just the street address of this website. To figure out the "driving directions," if you will, your computer contacts a special server (called DNS, for Domain Name System) to figure out the route. That server tells your web browser that "CNET.com" actually means "220.127.116.11". The number, known as an IP address, is a far better description of where CNET actually lives.
If your DNS server goes down... it's like your computer no longer has GPS! But you can simply switch to another public DNS server to resolve those issues.
By default, your computer probably reaches out to a DNS server controlled by your internet service provider (ISP), say Comcast or AT&T. That means they can easily see the websites you visit -- and because they've got your name and address, too, they could theoretically build a fairly complete profile of you.
If you use a DNS server provided by a different company, they might record that info too...but at least it'll be harder for them to figure out who exactly is browsing those websites, which could make the data less valuable.
And at least one DNS provider has sworn it won't keep a log: CloudFlare (18.104.22.168) says it'll open itself up to third-party auditors to guarantee they aren't collecting data from you.
22.214.171.124 = CloudFlare DNS
126.96.36.199 or 188.8.131.52 = OpenDNS
184.108.40.206 or 220.127.116.11 = GoogleDNS
18.104.22.168 or 22.214.171.124 = DNS.Watch
126.96.36.199 or 188.8.131.52 = VeriSign Public DNS
Note that you may need to try more than one to get your sites working. OpenDNS helped us around a Twitter and Netflix outage back in 2016, but GoogleDNS didn't.