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

v3-3
v3-2-1
v3-3-1

#42

Updated my post, thanks.


#43

Note that within the FTLDNS beta testing branches, there is a new option available that allows NXDOMAIN blocking. This should solve all these problems if you’re willing to try it out.


#44

@DL6ER
Thank you for the hint. Where I can find the

README of the FTLDNS branch

?


#45

I think we’ll be writing a blog post about this, too. Would be cool if someone in here could already confirm that it is a solution for this problem.


#46

Just wanted to give some feedback on the new FTLDNS branch which I’m now running as my main DNS.

After changing to BLOCKINGMODE=NXDOMAIN (it took me a while to locate the readme for this, which if anyone else needs is here: https://github.com/pi-hole/FTL/blob/FTLDNS/README.md ) I’m finding that unexplained delays in page loading have gone and that everything is now loading really quickly. For me personally the NXDOMAIN solution seems preferable to the previous pihole IP solution.

Well done to the developers!


#47

I inserted the BLOCKINGMODE=NXDOMAIN into my /etc/pihole/pihole-FTL.conf and restarted the FTL-Service. But there is no change to recognize. A ping to a blocked DNS-name still resolved to the local IP.


#48

Yes - I ran into that problem initially, but then pihole -up found an update which fixed it for me.


#49

I tried, but updates doesn’t work

  [i] Checking for updates...
  [i] Pi-hole Core:	up to date
  [i] Web Interface:	up to date
curl: (22) The requested URL returned error: 404 Not Found
  [i] FTL:		update available

  [i] Downloading and Installing FTL...curl: (22) The requested URL returned error: 404 Not Found
  [✗] Downloading and Installing FTL
      Error: URL not found
  [✗] FTL Engine not installed.
  [i] Restarting services...

#50

I can’t advise on that, but for me (checked just now):

    pi@RPi3-DNS:~ $ pihole -up
      [i] Checking for updates...
      [i] Pi-hole Core:     up to date
      [i] Web Interface:    up to date
      [i] FTL:              up to date

      [✓] Everything is up to date!

so maybe something else is broken…


#51

You’re probably on a branch that no longer exists. Try running pihole checkout ftl FTLDNS to get back on a main branch. Then try the pihole -up again to make sure you have the latest.


#52

I’m on the ftlbranch and want to stay here. I wouldn’t change back to the main branch.

Current Pi-hole version is v3.3-130-g2e6a937
Current AdminLTE version is v3.2.1-179-g3fd9b4d
Current FTL version is vDev-0f40cd1

#53

@DanSchaper Right know I understand Error updating latest beta ftldns with regex

I did it, all is fine now.

Thank you


#54

Really weird. Your instructions were great, but for some reason, now the https test page loads instead of being blocked. Before, it was blocked, but it took some time. So I read this thread in hopes of speeding things up. Why would I be able to get to the https site after implementing this? I checked the blacklist and the test site is indeed included:

pi@pihole:~ $ pihole -q secure.quantserve.com
Match found in Blacklist
secure.quantserve.com
Match found in Wildcards:
*.secure.quantserve.com
Match found in list.0.raw.githubusercontent.com.domains:
secure.quantserve.com
Match found in list.2.sysctl.org.domains:
secure.quantserve.com
Match found in list.6.hosts-file.net.domains:
secure.quantserve.com

And here’s my iptables:

pi@pihole:~ $ sudo iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
REJECT tcp – anywhere anywhere tcp dpt:https reject-with tcp-reset
REJECT udp – anywhere anywhere udp dpt:80 reject-with icmp-port-unreachable
REJECT udp – anywhere anywhere udp dpt:443 reject-with icmp-port-unreachable

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination


#55

What I don’t get …

is it /etc/iptables/rules.v4
or
is it /etc/pihole/rules.v4
like some people used in this thread?