Today we will be talking about the Domain Name System (DNS). Us lowly humans prefer to give things names while computers need numbers. DNS acts like the Internet’s phone book, translating name like
www.kerryhatcher.com into an IP address like
184.108.40.206. This process is rather fast, but due to a quark of modern web apps, has to happen several times on each website you visit.
To be clear improving DNS lookup time won’t actually increase the throughput of your internet connection. A 300mbs connection would still be 300mbs. It will however increase the speed at which pages render on your screen and make downloads start faster (but not run faster).
Take this visit to the The Atlanta Journal-Constitution home page. In order for the browser (Firefox in this case) to load the page, my computer had to send requests for 109 different things. Those are spread across a dozen or so hostnames each requiring a DNS lookup.
Screenshot of ajc.com with dev tools turned on
Firefox has a really neat set of tools built in for looking at this sort of information. Just go to any website, right click, and select
inspect element. From there just select the Network tab and refresh the page to watch all the requests pile up.
Lets take a look at an individual request. You will see that the browser took the most time just doing the DNS resolution. The actual download only took 124 ms vs the 283 ms to lookup the address in DNS.
Screen shot of an individual asset load time from ajc.com
So you can see how if all these assets are waiting on DNS, the speed at which a page loads can be drastically impacted.
The issue that I’ve seen over the years is that DNS tends to be a bit of an afterthought among ISPs or is seen as a way to make money off your data. So they can be slower than you would want or they might be spying on you. The good news is that its relatively easy use a DNS server that your ISP doesn’t manage. Several great free options exist today for this including OpenDNS, Google DNS, Quad9, and my favorite CloudFlare DNS.
Screen capture of DNS providers query speed according to www.dnsperf.com/
My Favorite: CloudFlare’s 220.127.116.11
I have a few reasons why CloudFlare’s service is my favorite.
Its fairly common practice to sell DNS logs data to determine web browsing habits. While on the surface this isn’t inherently bad, I’m just not a fan. Cloudflare has a well established reputation for privacy, and even recently underwent an audit to show just how private it is.
3. DNS Specs
This really gets me angry at some DNS providers. I vividly remember one time trying to troubleshoot an issue and this tripped me up. As far as I could tell my tools were indicating all was well but the application wasn’t working. It turns out my new ISP would respond with a functioning webserver IP address if a resolution failed. That server would return a webpage of search results. The official spec would have the server return an
nx domain. so I wasted a very long time on that.
The trick was that the ISP was selling ads on the search page and was getting paid from the search engine. So it was just another way to milk me for more money.
4. CloudFlare CDN
CloudFlare’s primary business is providing CDN and WAF services. A significant number of websites you visit are probably already served by them (including this one). This means that if you us CloudFlare’s DNS you are more likely to get directed at the fastest website server available to you.
5. Malware Protection
By default CloudFlare DNS is a by the book DNS provider. However, they do provide a another set of DNS servers that include a handy feature, they maintain a list of known domains that host Malware and won’t resolve them. So if you have kids (or even adults) that have issues getting garbage off random corners of the internet, this will help keep your computers clean and happy. Also since this runs at the DNS level, there is no impact to the performance of you computer.
Cool, so how I get started?
If you are comfortable changing settings on your router or computer then the setup of Cloudflare or any of the others is straight forward.
There are two basic options; device config, or network config. If you setup your individual device (like your laptop) to use Cloudflare, then it won’t matter what network you are on (at home, or somewhere else) you will have the benefits of the service. With network config, you make changes to your router and all the devices on your network automatically start using the service of your choice.
CloudFlare has really good instructions at https://18.104.22.168/dns/. If you choose a different provider, they all have similar instructions.
Note: if you want to make use of Cloudflare’s malware protection, you will need to visit https://22.214.171.124/family/ for instructions.
What’s Firefox DoH?
Firefox has long had a focus on privacy. While setting up DNS isn’t the most complex process, it is still well above a vast number of people’s technical comfort level. The most effective privacy protections are those that happen by default. So newer versions of Firefox implement a protocol called DNS over HTTP (DoH). This means that Firefox will make DNS requests over encrypted HTTP (just like all other website traffic) to a default list of providers. Out of the box it actually uses Cloudflare, but users are able to select others from a list or disable the feature altogether.
I hope you found this post useful and interesting. If you did, please consider chipping in to help offset the cost of running this website. That way I can keep bringing you content without the need for ads.