Want faster internet?
 

Use Cloudflares 1.1.1.1
http://1.1.1.1

Linus Tech Tips explains:
https://www.youtube.com/watch?v=kqnvrjgyEMc

Anyone here using 1.1.1.1?

As a former network designer, tuner, troubleshooter, and infrastructure guru....

Poor DNS performance (and I was a systems guy...) has caused more "network problems" than I can recall...from slowdowns to total lockups...

I knew what this was about before clicking :)

No thanks, I run my own caching server. That also spoofs all sorts of ad servers and trackers.

I always had the latest, most robust DNS servers too, running on some SERIOUSLY dedicated, high-octane, carrier grade servers ...doesn't matter ;). I'm not advocating the OP's product...just pointing out the first place I always looked when the shtf and it's a "network problem".... nah...it's DNS (again) :(

Still always was " my" problem....network or ???, until I fixed it...or rubbed the offender's nose in it...I often had a brown nose too....but it wasn't due to "the network problem" ;)

All sorts of concerning comments on that Youtube video. Buyer (user) beware.

This is how you do it.

Just how does one do this?

I think that is a major part of what is being discussed. Keith is running dedicated hardware and software -probably Linux or Unix- to support a large enterprise. My wife and I just retired as a 2 person IT consulting shop. We ran in the home office a full blown, but less intensive hardware infrastructure based on the latest MS server OS. For our respective users, I bet there is not a spec of performance difference.

But the average home user who wants better performance probably doesn't want to buy hardware and maybe software, plus have to manage it. So something like the OP's solution or even an Open DNS subscription is a better idea for the average user.

YMMV

I've been using this for about a month now to try it out. I used Google's DNS previously. Maybe it's faster or maybe it isn't, but I can't tell the difference between the two.


Sent from my iPad using Tapatalk

Get a Raspberry Pi. Flash a microsd card wtih latest Raspbian. Set it up on your network with a static IP address. Install bind9. Confirm bind9 is working with a few nslookups pointing at localhost for a source. Assuming it all works (it should) configure your DHCP server to give clients the IP you assigned to the Pi to use as their DNS server.

Just published a slightly older version of my course materials as a public resource in our LMS that has all sorts of good services with Linux networking info in it. The caching DNS is covered, as is setting up the same DNS service to block ads across your *entire* network.

https://courses.sfcollege.edu/courses/348388

:D

You would think that the replacement router firmwares (tomato, dd-wrt, etc) would include a caching DNS service ...

I've thought about packaging up a Pi and SD card wtih image and a SERIOUSLY strong filter (block all, whitelist some) as a "internet filter for the morally uptight that actually works". But I don't have time to do it, or the desire to deal with the morally uptight....

8.8.8.8

All very fine and good but what does Charlie Brown's little brother have to do with this?

Yep...never had to use it as a name server, but if at home, and I've suspected DNS issues I've pointed to it just to check in the past.

Use OpenDNS (now Cisco Umbrella) fantastic product.

Sometimes using a cloud based DNS, or Internet name server like (8.8.8.8), can be an excellent choice....then again, it could simply kill performance....it depends. Most of you are looking at this strictly from the client side....what if you have a web server that issues 57 DNS lookups (no cache) to deliver a single home page? There is no one size fits all DNS performance panacea imo...it just depends on what's going on behind the curtain...YMMV.