Request on blocked domains should fail fairly quickly.
Requests to blocked domains visible in Chrome Developer tools take up to 30 seconds to timeout
https://tricorder.pi-hole.net/0EoDdQf8/
Am running Little Snitch but have put it in silent/bypass mode and the results are unchanged. Have tried running from different Raspberry Pi's and the results are the same. Thanks
Run from a client in your network, please provide the output of the following command
dig <some.blocked.domain>
where you substitute <some.blocked.domain> with a blocked domain you observe Chrome to resolve slowly.
~ dig https://pubads.g.doubleclick.net/activity\;xsp\=4793078\;ord\=1\?
; <<>> DiG 9.10.6 <<>> https://pubads.g.doubleclick.net/activity;xsp=4793078;ord=1?
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 55491
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;https://pubads.g.doubleclick.net/activity\;xsp=4793078\;ord=1?. IN A
;; AUTHORITY SECTION:
. 3600 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2021100700 1800 900 604800 86400
;; Query time: 20 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Thu Oct 07 09:23:56 EDT 2021
;; MSG SIZE rcvd: 164
You are trying to resolve a URL, not a domain.
Please try again with only the domain, pubads.g.doubleclick.net.
Likely, that client is not using Pi-hole, but your router for DNS (if 192.168.1.1 would be your router).
dig pubads.g.doubleclick.net
; <<>> DiG 9.10.6 <<>> pubads.g.doubleclick.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 18492
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;pubads.g.doubleclick.net. IN A
;; ANSWER SECTION:
pubads.g.doubleclick.net. 2 IN A 0.0.0.0
;; Query time: 7 msec
;; SERVER: 192.168.1.28#53(192.168.1.28)
;; WHEN: Thu Oct 07 09:53:27 EDT 2021
;; MSG SIZE rcvd: 69
.28 is the pi hole.
Thank you.
That dig result shows that Pi-hole has provided its answer within 7 ms.
Whatever makes your browser take so long, Pi-hole wouldn't contribute much to it.
Could you perhaps share a screenshot of the delay as shown by your Chrome developer tools? In this forum, you are able to paste images directly.
Thank you for your time and help, my thread title is a bit misleading as those were the symptoms before I cleaned out a few very old ad lists right before this post and I didn't give it enough time to notice while there still is kind of a hang effect in the browser as these scripts attempt to load but it is now reduced quite a bit. Probably something I need to figure out on my machine testing different browsers. Thanks for your time
sorted by time
sorted by status
Are you running OS Big Sur with Little Snitch? If so, I would check the Little Snitch site as there were reports of delays while using that software and NULL blocking (from memory only).
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.
