pihole showing query in the blocklist but not clocking it
I am using Docker on a ubuntu machine. with local IP 192.168.1.32
Expected Behaviour:
_Client machine should not allowed to visit web page if it is in blocked list.
e.g I have added "amazon.com" to the blocklist as a wildcard. when I try to open amazon.com from client it shows on query list with time
output for nslookup amazon.com
on ubuntu
Server: 192.168.1.32
Address: 192.168.1.32#53
Name: amazon.com
Address: 0.0.0.0
Name: amazon.com
Address: ::
Actual Behaviour:
I can browse amazon.com with any issue on client
output for nslookup amazon.com
on client (windows)
Server: dns.google
Address: 2001:4860:4860::8888
Non-authoritative answer:
Name: amazon.com
Addresses: 205.251.242.103
52.94.236.248
54.239.28.85
This means Pi-hole is blocking this domain.
Vipul_Sharma:
I can browse amazon.com with any issue on client
output for nslookup amazon.com
on client (windows)
Server: dns.google
Address: 2001:4860:4860::8888
Non-authoritative answer:
Name: amazon.com
Addresses: 205.251.242.103
52.94.236.248
54.239.28.85
This means your Windows machine is not using Pi-hole as DNS server.
It is using Google (dns.google
).
Interesting that your expected behavior shows IPV4 as blocking but actual behaviour as IPV6 not blocking. Perhaps some IPV6 issues?
1 Like
correct, when I disabled window PC IPv6, and it works
but I am not sure how to get/set static IPv6 in Ubuntu and set it on my G-2425G-A
router
here is my IP config for interface wlx14ebb647225b
which I am using
inet 192.168.1.32 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 2402:e280:4111:13a:138b:a24e:d575:2033 prefixlen 64 scopeid 0x0<global>
inet6 fe80::e23e:2857:4803:1e6 prefixlen 64 scopeid 0x20<link>
ether 14:eb:b6:47:22:5b txqueuelen 1000 (Ethernet)
RX packets 1456455 bytes 1222744070 (1.2 GB)
RX errors 0 dropped 8834 overruns 0 frame 0
TX packets 729860 bytes 207815471 (207.8 MB)
TX errors 0 dropped 334 overruns 0 carrier 0 collisions 0
system
Closed
February 9, 2025, 11:06am
5
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.