4 ms·
Can any of the DNS wizards here explain the potential performance implications of using this? I have been meaning to install this and begin using it but the lat
by whalesalad 8y ago
Can any of the DNS wizards here explain the potential performance implications of using this? I have been meaning to install this and begin using it but the latency of a Cloudflare DNS request is so low (and reliable) that I don't know if I want to risk introducing this into my network stack.
I have an R720 and a few old RPi's... so either major overkill hardware or major weaksauce hardware.
- lucb1e 8y agoDNS wizard checking in. This stuff was designed in the 80s and I ran BIND on the kind of potato that has a quarter of the RAM that a raspberry pi has, together with apache, mysql, php, vnc, utorrent, and some other stuff, and it still performed great. I don't know by heart which dns server pihole uses, but no, the latency added by a server on your LAN is negligible. Case in point, most (all?) routers do dns forwarding by default (is that not common in the USA? Since you mention cloudflare, which got to be slower than the default option unless you have some really cheapo isp).
- adzm 8y agoYou'd be surprised how slow our ISP's DNS servers can be.
- gerdesj 8y ago"and I ran BIND on the kind of potato that has a quarter of the RAM that a raspberry pi has" 256MB RAM? - bloody luxury! A very quick and a bit rubbish experiment: $ ping 9.9.9.9 5 packets transmitted, 5 received, 0% packet loss, time 10ms rtt min/avg/max/mdev = 9.982/10.838/12.531/0.888 ms $ dig @9.9.9.9 www.google.com A ;; Query time: 13 msec DNS is pretty quick. Note how I mistakenly use ICMP and a UDP service response time to imply something. If I'd tried to claim that DNS adds about 5ms overhead, I would have been first to put the boot in. The basic result stands though - DNS is quick. The above results are from: my laptop -> wifi -> switch -> switch -> APU2c based pfSense box with quite a lot going on -> modem (FTTC in UK - PPPoE/A) -> ISP .... etc.
- ben174 8y ago:D Yea I don't think anyone in the 80's was running 256 MB ram. Correct me if I'm wrong?
- ohyeshedid 8y ago640k ought to be enough for anybody.
- lucb1e 8y ago> 256MB RAM? Oh, an eighth then, I didn't know the raspi had that much RAM. And this was on a ~2002 laptop in 2011 or so, I'm not old enough to have run it in the 80s on a real potato :(
- abrugsch 8y agoonly the first revision (and the A/A+ until the 3A+ came out) had 256Mb. It was soon upgraded to 512 as one of the first design changes (before moving to the "plus" form factor with 40 pin GPIO header) the early A's even had 128Mb but they are a rare thing as the original A was not promoted much before the first upgrade cycle.
- xd1936 8y agoThey have forked dnsmasq to power their project[1]. 1. https://pi-hole.net/2018/02/22/coming-soon-ftldns-pi-holes-own-dns-dhcp-server/ https://pi-hole.net/2018/02/22/coming-soon-ftldns-pi-holes-o...
- mirceal 8y agoyou can configure what dns servers to use for the “upstream”. you can choose between a series of ones included by default (gooogle, etc) or specify your own
- skunkworker 8y agoIt's pretty quick. If it's running on your local network it can cache your DNS resolvers of choice and only add a few ms at most. On your network make sure to setup backup DNS resolvers when your pi-hole is updating etc. Currently I'm running it as a docker image on my local server.
- muppetman 8y agoYou should always run a local caching DNS server on your home network if you care about latency etc. That way when your iphone requests apple.com and then your laptop requests it 3 minutes later, the dns query time will be sub millisecond, instead of maybe 5-15ms. will you notice that? No, you will not. But you seem to be concerned about levels of latecy it's impossible to notice anyway, so you need this to get even more (unnoticeable) decreases in latency :) Then the pihole just queries 1.1.1.1 for you, so your DNS privacy etc is still kept.
- mirceal 8y ago2 things to consider: 1) any additional latency is on the 1st request and after that the response is cached for the duration if the record’s ttl 2) because it’s blocking all the crap you have more bw so overall in my experience it actually speeds things up considerably (even in the scenario of an already fast dns resolver)
- nikeee 8y agoIt's usually pretty quick. Unless the SD card of the Pi breaks randomly. Then, you've suddenly got inexplicable slow/unavailable internet because the Pi may not respond to DNS requests any more.
- nonamechicken 8y agoOne question I have is when we block ads and especially analytics/tracking, won't it decrease the battery life of mobile devices? Apps could be written in such a way that if a request gets blocked or dropped, it will keep on retrying which would impact battery life.