Is Original Pi B up to the job

[Geffers]

Folks,

I never gave this a thought as I am running Pi-Hole on Raspian Stretch Lite so no GUI.

Am using one of my old Pi B devices, only two USB ports, now that is how old it is

Just checking that this is sufficiently up to the job, assuming as it is only really checking data that it should be fine although some web pages do take some time to load.

Ghostery (Firefox addon) reported that home.bt.com (entered as bt.com) took 52.7 seconds to load fully and https://news.sky.com/ (entered as sky.com/news) took 43.1 seconds.

Geffers

[DL6ER]

@Geffers

Just checking that this is sufficiently up to the job, assuming as it is only really checking data that it should be fine although some web pages do take some time to load.

Yes, until a few moths ago I even did all of the Pi-hole development myself on a Raspberry Pi B. Now I'm using a Pi v3 as compiling FTL on the v1 model was really awfully slow.

The long loading times you see aren't related to the computing power of your Pi-hole but they are caused by your browser which tries to download ads (most likely via HTTPS) and never get a response.

If you run the following command:

dig google.com

you will be shown the query time. If you try several times, you will see that the query time will be greatly reduced after the initial query due to the caching nature of our DNS resolver.

To attack the long loading times, please tell us what the following commands tell you:

sudo iptables -L
sudo ip6tables -L

[jacob.salmela]

The long load times are likely what @DL6ER mentioned. There is an FAQ on it:

Why do some sites take forever to load when using Pi-hole? (for versions < v4.0)

Update: 2018-08-06 As of v4.0, this should no longer be a problem unless you choose to deviate from the new default blocking mode and return to the IP-based mode. And the iptables rules mentioned in this article should not be needed. Update As of v3.1 the first reason should not be an issue anymore That being said, there are generally two reasons this happens: your ISP changes your IPv6 address (Global Unicast Address), causing Pi-hole to become misconfigured and timing out when trying…

[Geffers]

Just to clarify - are you asking that I run the commands mentioned on the Pi-Hole machine?

dig google.com went from 23ms first time to 1 ms second time.

pi@pi-dns:~ $ sudo iptables -L

Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination
pi@pi-dns:~ $ sudo ip6tables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination
pi@pi-dns:~ $

Geffers

[DL6ER]

@Geffers

Just to clarify - are you asking that I run the commands mentioned on the Pi-Hole machine?

dig google.com went from 23ms first time to 1 ms second time.

Okay, that is good. The article @jacob.salmela contains more material you can use to tackle this problem.