1.1.1.1: Fast, privacy-first consumer DNS service

(blog.cloudflare.com)

1895 points _l4jh | 1 comments | 01 Apr 18 12:14 UTC | HN request time: 0s | source

Show context

tscs37 ◴[01 Apr 18 14:16 UTC] No.16728384[source]▶

I'm probably gonna switch my PiHole over from Google DNS. I trust Cloudflare more than Google to uphold my privacy. Not that I trust either very much.

Benchmarking Results for the interested: (sorted worst first, P value is bottom-X-percent)

    1.1.1.1:
      P00.5=48.2ms (55.8ms VPN)
      P50.0=32.8ms (37.0ms VPN)
      P95.0=29.1ms (33.0ms VPN)
      P99.5=29.1ms (32.7ms VPN)
    
    8.8.8.8:
      P00.5=225.4ms (71.5ms VPN)
      P50.0=48.0ms  (53.6ms VPN)
      P95.0=44.1ms  (51.3ms VPN)
      P99.5=43.8ms  (50.7ms VPN)

I've noticed I measured with my VPN on, so I put the VPN measurements in brackets behind the nominal values. The 8.8.8.8 benchmark is a bit odd but I repeated it several times with 100 iterations each and this is basically what I get.

replies(2): >>16728426 #>>16728591 #

Faaak ◴[01 Apr 18 14:24 UTC] No.16728426[source]▶

>>16728384 #

Why isn't your pihole a stand-alone DNS resolver instead on relying on 3rd-party services ?

replies(1): >>16728482 #

1. tscs37 ◴[01 Apr 18 14:35 UTC] No.16728482[source]▶

>>16728426 #

I'm not aware of any pihole native setting to enable a resolver instead of using forwarding.

Third-party services like this will also have a huge range of queries cached so the response time will definitely be better than have a rasppi with little free memory try/attempt to cache that.

↑