cancel
Showing results for 
Search instead for 
Did you mean: 

Getting Pihole to work with Hub2

npr
Pro
Posts: 1,898
Thanks: 119
Fixes: 9
Registered: ‎21-01-2013

Re: Getting Pihole to work with Hub2

Glad you've got Pihole working with the hub2.

Have you tested the speed of pihole against other dns resolvers?
https://www.grc.com/dns/benchmark.htm

PNPihole
Hooked
Posts: 9
Registered: ‎09-08-2022

Re: Getting Pihole to work with Hub2

Thanks for this. The 'Unbound' resolver came out to about 20th place at 0.028. Level3 is 0.017. Not sure I'm going to even notice the difference but quicker is quicker so changed over now.

Anonymous
Not applicable

Re: Getting Pihole to work with Hub2

Are you saying that your local Unbound DNS is taking 28ms to respond ?

 

If so, have you disabled (or perhaps not enabled) caching ?, because running DNS benchmarks on cached local servers should be closer to 1ms or less !

 

Final benchmark results, sorted by nameserver performance:
 (average cached name retrieval speed, fastest to slowest)

  192.168.  2.  1 |  Min  |  Avg  |  Max  |Std.Dev|Reliab%|
  ----------------+-------+-------+-------+-------+-------+
  - Cached Name   | 0.000 | 0.000 | 0.000 | 0.000 | 100.0 |
  - Uncached Name | 0.007 | 0.029 | 0.233 | 0.045 | 100.0 |
  - DotCom Lookup | 0.009 | 0.011 | 0.016 | 0.001 | 100.0 |
  ---<O-OOO-OO>---+-------+-------+-------+-------+-------+

                Local Network Nameserver




    4.  2.  2.  1 |  Min  |  Avg  |  Max  |Std.Dev|Reliab%|
  ----------------+-------+-------+-------+-------+-------+
  - Cached Name   | 0.006 | 0.006 | 0.007 | 0.000 | 100.0 |
  - Uncached Name | 0.007 | 0.058 | 0.321 | 0.092 | 100.0 |
  - DotCom Lookup | 0.008 | 0.014 | 0.021 | 0.003 | 100.0 |
  ---<-------->---+-------+-------+-------+-------+-------+
                 a.resolvers.level3.net
                       LEVEL3, US

 

bobpullen
Community Gaffer
Community Gaffer
Posts: 16,887
Thanks: 4,979
Fixes: 316
Registered: ‎04-04-2007

Re: Getting Pihole to work with Hub2

That's interesting. How is the pi-hole connected to the hub? In my environment (also using Pihole/local Unbound instance), my local resolver is faster than all of the default public ones provided by the GRC app.

Edit: @Anonymous beat me to it.

Bob Pullen
Plusnet Product Team
If I've been helpful then please give thanks ⤵

PNPihole
Hooked
Posts: 9
Registered: ‎09-08-2022

Re: Getting Pihole to work with Hub2

As I understood it, yes it was taking 28ms to respond and wasn't appearing in first place. Regarding cache, I have no idea as the option never came up during install, however looking at the results I believe cache is enabled?. I was following the installation instructions as per the Diet Pi Site which doesn't make any mention of it. The RPi is connected via wifi. Its a Pi ZeroW so I've left the USB port free for the keyboard as I've not got around to sorting out SSH for it yet.

 

I've run the test again today with the Unbound DNS as the only IPv4 upstream (no IPv6 upstream) and its given me the following results for top two:

 

Final benchmark results, sorted by nameserver performance:
(average cached name retrieval speed, fastest to slowest)

192.168. X. XX | Min | Avg | Max |Std.Dev|Reliab%|
----------------+-------+-------+-------+-------+-------+
+ Cached Name | 0.006 | 0.015 | 0.023 | 0.004 | 100.0 |
+ Uncached Name | 0.030 | 0.081 | 0.259 | 0.069 | 100.0 |
+ DotCom Lookup | 0.032 | 0.043 | 0.062 | 0.008 | 100.0 |
---<O-OO---->---+-------+-------+-------+-------+-------+
pi.hole
Local Network Nameserver


4.2.2.4 | Min | Avg | Max |Std.Dev|Reliab%|
----------------+-------+-------+-------+-------+-------+
- Cached Name | 0.016 | 0.021 | 0.030 | 0.002 | 100.0 |
- Uncached Name | 0.016 | 0.063 | 0.269 | 0.068 | 100.0 |
- DotCom Lookup | 0.021 | 0.033 | 0.052 | 0.008 | 100.0 |
---<-------->---+-------+-------+-------+-------+-------+
d.resolvers.level3.net
LEVEL3, US

 Is this good?bad?