dig and nslookup the urls in question, the answer time is always below 60ms
change the blocking mode both to NODATA and NXDOMAIN
ran pihole debug and got two warnings
ran without pihole (over my mobile hotspot and with pi-hole off) and it is definitely only there when the pi-hole is enabled
skipped some ipv6 "solutions" out there because I have ipv6 not enabled in my internal network
*** [ DIAGNOSING ]: Dashboard and block page
[✗] Block page X-Header: X-Header does not match or could not be retrieved.
HTTP/1.1 200 OK
Content-type: text/html; charset=UTF-8
Expires: Thu, 11 Mar 2021 20:21:33 GMT
Cache-Control: max-age=0
Date: Thu, 11 Mar 2021 20:21:33 GMT
Server: lighttpd/1.4.53
and
[✓] IPv6 address(es) bound to the eth0 interface:
fe80::6201:75ad:e2df:4132 does not match the IP found in /etc/pihole/setupVars.conf (https://discourse.pi-hole.net/t/use-ipv6-ula-addresses-for-pi-hole/2127)
Expected Behaviour:
I expect ALL pages to be either slow or fast, not just
github.com
github.tools.sap
Note: I have to say that this only happens on my 11.2.2 Big Sur OSX (my phones seem to be always fast, same for the ipad) and I think only for Chrome (Version 88.0.4324.192 (Official Build) (x86_64)
). I do not know if the other browsers just did not cache something yet or if they generally behave differently
Actual Behaviour:
These two URLs are the only ones I can identify as slow, the rest of all pages out there run just fine.
Only one browser on one machine and two domains affected are very strong indications that Pi-hole isn't involved here, especially since your debug log shows you are not using group management to filter only specific clients.
I've switched your topic to the Community Help category accordingly.
If it is indeed only Chrome exhibiting this behaviour, you may want to check that DoH is disabled, and its "use a web service to help resolve navigation errors" (or similar) option should be disabled as well.
DoH is disabled but the other setting you state I can not find where it should be in my Chrome Version.
I forgot to mention one thing in the original post: When I restart the DNSResolver, for a very very short time, the pages are fast!
at:Bucking_Horn I agree that it is weird. But why does my same (100%) laptop work then directly after pihole is disabled or when I use my mobile hotspot?
That's a common privacy feature for all Chromium based browsers, though it may be named differently across browsers and versions, e.g. Chromium Edge matches the qouted string, Vivaldi shortens it to "DNS to help resolve navigation errors" under a Google Services section.
That feature may try to resolve a blocked domain name via Google's DNS servers after the browser has received 0.0.0.0 from Pi-hole, slowing down resolution and by-passing Pi-hole at the same time.
Try to search for DNS options in your browser's settings, or do a web research for your specific browser.
Whether those options actually help to address your problem is just a guess.
However, it is generally sound to disable these options when using Pi-hole for DNS.
I now "lived" it for some hours and I just come to the conclusion that something is off.
I go to GH or GHES or also this page (discourse) and then it takes like 10s to load. But then, the next clicks all is fast, until I go idle again on that browser. If I come back, 10s wait.
It seems that some kind of cache or TTL expires.
Also, it happens in Brave too. I have a worm sitting somewhere.
