Since upgrade to v5.0 internet is laggy

Help
1

I have a clean install and im finding that it often is slow to respond / quite laggy when browsing.

I have 46 lists in my Pi-Hole, could this be the reason it is struggling?

Are there any tests / optimizations I could perform to attempt to diagnose the performance issue?

Thanks guys

2

Please provide a debug log generated via

pihole -d

or Tools/Generate Debug Log.

3

Hi Guys,

Apparently the log file is available here

https://tricorder.pi-hole.net/f642d7jtzi

Let me know if that doesn't work.

Regards
Alasdair MacLeod

4

According to your debug log there are only 4 lists...

also:

*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✗] Failed to resolve deluxechoc.com via localhost (127.0.0.1)
[✗] Failed to resolve deluxechoc.com via Pi-hole (192.168.10.238)
[✓] doubleclick.com is 216.58.204.78 via a remote, public DNS server (8.8.8.8)

According to the first two lines there, it appears your pi-hole is not actually resolving anything...

What is the output of these commands from the CLI on your pi-hole device?

dig deluxechoc.com @127.0.0.1
dig google.com @127.0.0.1

Edit:

Also, you may have a feedback loop going on with conditional forwarding:

   Jun  3 00:00:15 dnsmasq[11893]: query[A] rfczlgflb.alshouse.local from 192.168.10.1
   Jun  3 00:00:15 dnsmasq[11893]: forwarded rfczlgflb.alshouse.local to 192.168.10.1

The above shows your router making a query for rfczlgflb.alshouse.local and then that query is being forwarded back to the router.

Do you still see the same issues if conditional forwarding is disabled?

5

Hi,

The result of dig were as follows;


pi@Pi-Hole:~ $ dig deluxechoc.com @127.0.0.1

; <<>> DiG 9.11.5-P4-5.1+deb10u1-Raspbian <<>> deluxechoc.com @127.0.0.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 44001
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;deluxechoc.com.                        IN      A

;; ANSWER SECTION:
deluxechoc.com.         2       IN      A       0.0.0.0

;; Query time: 23 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Sun Jun 07 10:25:29 BST 2020
;; MSG SIZE  rcvd: 48

pi@Pi-Hole:~ $ dig google.com @127.0.0.1

I have now disabled conditional forwarding to see how things go.

Regarding the block lists. I performed a clean install to see if this would help, unfortunately it hasn't, the performance still seems extremely slow.

Im just trying to figure out what could be causing it.

Thanks PromoFaux for the assistance, I really do appreciate it. Hopefully we can get to the bottom of it.

6

OK, this result is expected...

Did it just hang here? Could you run a fresh debug token please?

7

Hi PromoFuax,

Apologies, I didn't hit enter a second time when I ran the test. #FacePalm.

Please see complete results below;

Additionally, here is the link to the new debug : https://tricorder.pi-hole.net/gsef2volpv

pi@Pi-Hole:~ $ dig deluxechoc.com @127.0.0.1

; <<>> DiG 9.11.5-P4-5.1+deb10u1-Raspbian <<>> deluxechoc.com @127.0.0.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 16533
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;deluxechoc.com.                        IN      A

;; ANSWER SECTION:
deluxechoc.com.         2       IN      A       0.0.0.0

;; Query time: 1 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Sun Jun 07 11:22:03 BST 2020
;; MSG SIZE  rcvd: 48

pi@Pi-Hole:~ $ dig google.com @127.0.0.1

; <<>> DiG 9.11.5-P4-5.1+deb10u1-Raspbian <<>> google.com @127.0.0.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45333
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;google.com.                    IN      A

;; ANSWER SECTION:
google.com.             145     IN      A       172.217.169.14

;; Query time: 23 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Sun Jun 07 11:22:13 BST 2020
;; MSG SIZE  rcvd: 55

pi@Pi-Hole:~ $
8

OK, so according to your debug log it looks to be working now, however I still see in the sample output of /var/log/pihole.log, there are circular queries to/from 192.168.10.1:

   Jun  7 00:03:30 dnsmasq[712]: query[A] api.amazon.com.alshouse.local from 192.168.10.1
   Jun  7 00:03:31 dnsmasq[712]: forwarded api.amazon.com.alshouse.local to 192.168.10.1

That said, these may just be from earlier on if it is not currently around midnight localtime for you...

In terms of your clients, what are they using to resolve DNS? From a client device please run:

nslookup deluxechoc.com

I see that Pi-hole is not currently set up to be the DHCP server, too, so can only assume you have this set up on your router (or some other device). Make sure the DHCP server is handing out the IP address of the Pi-hole for DNS, and not it's own, otherwise your dashboard will show all queries as originating from the router... which might explain the feedback loop with conditional forwarding set

9

Hi PromoFaux,

This is the output from one of the clients.

Microsoft Windows [Version 10.0.18363.836]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\Users\alasd>nslookup deluxechoc.com
Server:  Pi-Hole
Address:  192.168.10.238

Name:    deluxechoc.com
Addresses:  ::
          0.0.0.0


C:\Users\alasd>
10

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.