The dnsmasq version is good. Did you follow the link @jacob.salmela posted?
Yes I'm read and make this opération explain in this link and no obtain good result.
Open the browser dev tools (F12) and use the network tab to see what is causing the query to take so long.
look this test
you see more script not respond
What is the output of
sudo iptables -L
here is the result of the order
root@srv-PiHole:~# 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
Did you try adding the
iptables6 rules as well (even if they IPv6 isn't enabled)? Run
pihole -d for a new debug token.
ok look the new debug token 2ziyvzg4ov
and see my
root@srv-PiHole:~# cat /etc/iptables/rules.v6 # Generated by ip6tables-save v1.6.0 on Wed Feb 28 09:35:40 2018 *filter :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [0:0] -A INPUT -p tcp -m tcp --dport 443 -j REJECT --reject-with tcp-reset -A INPUT -p tcp -m tcp --dport 443 -j REJECT --reject-with tcp-reset -A INPUT -p udp -m udp --dport 80 -j REJECT --reject-with icmp6-port-unreachable -A INPUT -p udp -m udp --dport 443 -j REJECT --reject-with icmp6-port-unreachable COMMIT # Completed on Wed Feb 28 09:35:40 2018
pihole -d for a new debug token. I was on vacation for awhile, and the rest of the team has also been busy working on getting the next update out the door.
it does not matter, thank you for seeing my problem.
my new token ob4j66201f
Your IPv6 address doesn't match what's in
gravity.list. Have you looked at:
Ii put the IPv6 see on the pinhole -d in setupVars.conf
but not change this situation.
Did you run
pihole -r > Repair after making this change?
the problem does not change.
I think my problem comes from my wifi router.
What happens if you clear all of your
iptables does the problem still exist?
no change after clear iptables
I'm update last version and my problem is not resolved.
Have you got one other idea ???
I'm not clear on whether or not you actually implemented the steps here:
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.