Browsing web should be seamless and with possible improved stability and ad-free experience
-Win10 - Docker - PiHole 5.1
Tried pretty much every solution regarding IPV6 etc I could find to no avail.
Browsing and loading speed on most sites are very very slow
First step, clean up the duplicates in /etc/pihole/setupVars.conf
*** [ DIAGNOSING ]: Setup variables
DNSMASQ_LISTENING=single
PIHOLE_DNS_1=8.8.8.8
PIHOLE_DNS_2=127.17.0.1
REV_SERVER=true
REV_SERVER_CIDR=192.168.0.0/24
REV_SERVER_TARGET=192.168.0.1
REV_SERVER_DOMAIN=local
API_EXCLUDE_DOMAINS=
API_EXCLUDE_CLIENTS=
API_QUERY_LOG_SHOW=all
API_PRIVACY_MODE=false
REV_SERVER=true
REV_SERVER_DOMAIN=local
REV_SERVER_TARGET=192.168.0.1
REV_SERVER_CIDR=192.168.0.0/24
REV_SERVER=true
REV_SERVER_DOMAIN=local
REV_SERVER_TARGET=192.168.0.1
REV_SERVER_CIDR=192.168.0.0/24
QUERY_LOGGING=true
INSTALL_WEB_SERVER=true
INSTALL_WEB_INTERFACE=true
LIGHTTPD_ENABLED=true
IPV4_ADDRESS=192.168.0.11
IPV6_ADDRESS=
DNS_BOGUS_PRIV=true
DNS_FQDN_REQUIRED=false
DNSSEC=false
PIHOLE_INTERFACE=eth0
REV_SERVER=true
REV_SERVER_DOMAIN=local
REV_SERVER_TARGET=192.168.0.1
REV_SERVER_CIDR=192.168.0.0/24
BLOCKING_ENABLED=true
Second, disable Conditional Forwarding completely and check the speeds, you probably have a routing/DNS loop and that will slow things to a crawl.
Next, if it's still a problem provide us with dig output or things we can see what you are seeing as slow.
Last, there is no IPv6 address on the Pi-hole install so I'm not sure what solutions you are trying. Is this Pi-hole running in Docker? If so then IPv6 will be a relative nightmare to configure.
Hi,
WEBPASSWORD=f03bd09861cd9a12519fcf8e439e29b27691193b070d1fde1d1f92fd0878975f
BLOCKING_ENABLED=true
PIHOLE_DNS_1=8.8.8.8
PIHOLE_DNS_2=8.8.4.4
PIHOLE_DNS_3=192.168.0.1#53
DNSMASQ_LISTENING=single
DHCP_ACTIVE=true
DHCP_START=192.168.0.10
DHCP_END=192.168.0.100
DHCP_ROUTER=192.168.0.1
DHCP_LEASETIME=24
PIHOLE_DOMAIN=lan
DHCP_IPv6=false
DHCP_rapid_commit=false
QUERY_LOGGING=true
INSTALL_WEB_SERVER=true
INSTALL_WEB_INTERFACE=true
LIGHTTPD_ENABLED=
IPV4_ADDRESS=192.168.0.11
IPV6_ADDRESS=
DNS_BOGUS_PRIV=false
DNS_FQDN_REQUIRED=false
DNSSEC=false
CONDITIONAL_FORWARDING=true
CONDITIONAL_FORWARDING_IP=192.168.0.1
CONDITIONAL_FORWARDING_DOMAIN=local.local
CONDITIONAL_FORWARDING_REVERSE=0.168.192.in-addr.arpa
PIHOLE_INTERFACE=eth0
My Vars file is originally as i pasted above, dunno why it looks like that on the diag.
Just removed conditional forwarding now, there's no any change to it, I had done it as part of a suggested solution I think. There's no difference in speed to note.
Dig Google Result
dig google.com
; <<>> DiG 9.16.5 <<>> google.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 29771
;; 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. 60 IN A 172.217.169.110
;; Query time: 4475 msec
;; SERVER: 192.168.0.11#53(192.168.0.11)
;; WHEN: Sun Jul 19 10:55:06 Turkey Standard Time 2020
;; MSG SIZE rcvd: 55
3.1. dig instagram.com
dig instagram.com
; <<>> DiG 9.16.5 <<>> instagram.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45182
;; flags: qr rd ra; QUERY: 1, ANSWER: 8, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;instagram.com. IN A
;; ANSWER SECTION:
instagram.com. 27 IN A 52.205.68.57
instagram.com. 27 IN A 3.222.61.237
instagram.com. 27 IN A 3.225.55.231
instagram.com. 27 IN A 3.213.94.222
instagram.com. 27 IN A 52.0.103.197
instagram.com. 27 IN A 52.3.102.88
instagram.com. 27 IN A 52.45.116.207
instagram.com. 27 IN A 35.153.11.244
;; Query time: 1858 msec
;; SERVER: 192.168.0.11#53(192.168.0.11)
;; WHEN: Sun Jul 19 10:57:20 Turkey Standard Time 2020
;; MSG SIZE rcvd: 170
Even though it differs sometimes, I see 5-10 second delay, sometimes even more before the page starts to load.
I am kinda lost at this point, in ipconfig, I shoulnd't even have a public ipv6 address to begin with.
Thanks
Neither your original debug log nor your separate setupVars.conf shows you are using IPv6 - not for Pi-hole and not for any upstream DNS.
Why do you think that IPv6 would be relevant to your issue at all?
setupVars.conf's content from your debug log and the more recent version as posted by you separately differ substantially, e.g. Conditional Forwarding and DHCP are enabled and you are using different upstream DNS in the latter - it's almost as if you were using two Pi-hole installations.
Did configure your Docker to use volumes as suggested in Quick Start for Docker Pi-hole?
Anyway, it's difficult to assess your situation if debug log information isn't current.
Could you provide us with a new debug token, please?
Your dig commands show long resolution times, but it's not clear where those times actually accumulate. Both the client connection where you run them from as well as the upstream servers do contribute here in addition to Pi-hole.
For comparison, see if you can correlate lookup times with entries from your Pi-hole's query log, and also see how long resolution takes when you foce your dig directly through one of Pi-hole's upstream DNS server, e.g.
dig @8.8.8.8 instagram.com
As as side note:
You should not use .local as your local domain's search suffix, as that is the default domain for the mDNS protocol. While this is unrelated to your current issue, this may lead to unexpected or inconsistent name resolution results when some devices actually make use of mDNS in your network.
I googled the problem for quite a while now before posting here, almost every solution related to slowing down loading times were about IPV6, so I thought there might be something there to look for. That's the only reason really.
The debug output was correct and current when I posted it but as the previous reply suggested I removed the conditional forwarding from there. But DHCP shouldn't really be enabled as I've done no such action.
New Debug Token: https://tricorder.pi-hole.net/sku94zkr8j
Secondary DNS Dig Output:
dig @8.8.8.8 instagram.com
; <<>> DiG 9.16.5 <<>> @8.8.8.8 instagram.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 27464
;; flags: qr rd ra; QUERY: 1, ANSWER: 8, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;instagram.com. IN A
;; ANSWER SECTION:
instagram.com. 11 IN A 3.225.55.231
instagram.com. 11 IN A 52.6.166.166
instagram.com. 11 IN A 107.21.50.66
instagram.com. 11 IN A 52.3.87.113
instagram.com. 11 IN A 52.205.68.57
instagram.com. 11 IN A 52.54.9.148
instagram.com. 11 IN A 3.223.74.156
instagram.com. 11 IN A 34.226.75.20
;; Query time: 31 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Sun Jul 19 15:57:55 Turkey Standard Time 2020
;; MSG SIZE rcvd: 170
I've done quite a few installs by deleting the container and installing again, If there is a method to do a fool-proof clean install method, I could do that too.
.local thing was another google solution tbh. It never worked anyway, I wanted to see the connected devices without using DHCP from PiHole since it's in docker container.
Thanks
Edit: Forgot to mention, the SetupVars file contens i shared in a reply was from "Documents\pi-hole-config\pihole" and the debug may have showed something different but I don't know how that's possible or 2 instances of pi-hole is possible in a single docker container, I am pretty sure I haven't done anything weird while setting the container up. Here is the script snippet I used after docker pull:
docker run -d --name pihole -e ServerIP=192.168.0.11 -e WEBPASSWORD="PW" -e TZ=Europe/Istanbul -e DNS1=127.17.0.1 -e DNS2=8.8.8.8 -e DNS3=8.8.4.4 -p 80:80 -p 53:53/tcp -p 53:53/udp -p 443:443 --restart=unless-stopped pihole/pihole:latest
I do not know what writes to files in that Document directory, but I doubt it's Pi-hole: As far as your docker run is concerned, that's not a location that is referenced anywhere. In fact, that docker run does not mount any volumes to export to your host system.
Thanks for providing this! Actually, that command is more in line with your debug outputs than the setupVars.conf you've posted separately.
Get rid of -e DNS1=127.17.0.1 in your docker run - that could have closed a DNS loop.
Maybe that's just a typo anyway (e.g. for 172.17.0.1), but you'd normally use several public DNS servers as upstream, or just one local DNS (as a way to achieve local hostname resolution without defining Conditional Forwarding).
For both volumes and docker run options in general, please refer to the Quick Start link I've posted previously and then use the Docker run script as a reference.
Doing a free install after backup my adlists with the quickstart docker-compose solved the problem. I believe i messed up somewhere on the installation and repeated that same mistake every time i reinstalled.
Here is the latest instagram dig:
dig instagram.com
; <<>> DiG 9.16.5 <<>> instagram.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2851
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;instagram.com. IN A
;; ANSWER SECTION:
instagram.com. 2 IN A 0.0.0.0
;; Query time: 5 msec
;; SERVER: 192.168.0.11#53(192.168.0.11)
;; WHEN: Sun Jul 19 19:24:18 Turkey Standard Time 2020
;; MSG SIZE rcvd: 47
Thank you for your help.
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.