Ive been playing with pihole for over 2 weeks now and i cannot get my raspberry pi 3 (V2) with pihole installed to do anything at all. Ive googled for days trying all the settings, but nothing works, the pages still load like nothing has happened. So i followed the following tutorial => https://www.youtube.com/watch?v=FnFtWsZ8IP0
Here is what ive tried:
change DNS (IPv4) settings in windows (old GUI) to 192.168.0.99
change DNS (IPv4) settings in windows (new GUI) to 192.168.0.99
change DNS (IPv6) settings in windows (old GUI) to 192.168.0.99
change DNS (IPv6) settings in windows (new GUI) to 192.168.0.99
disabled IPv6
CMD => ipconfig /release then /renew
cleared browser cache / settings / cookies
rebooting pc
rebooting PI
reboorting DNS resolver
using different computer
Audit log does nothing at all, on chrome and ff
FTL.log does nothing at all, on chrome and ff
Query log shows BLOCKED (gravity)
adding to a group in pihole
adding a known website to pihole for blocking
using a mobile phone (android)
blocking domain "9gag.com" (as a test site) with and without regex
Which part of this did you not understand? Posting your log publicly (twice) is not doing any good to protect your privacy.
These are the first three lines of a debug log:
This process collects information from your Pi-hole, and optionally uploads it to a unique and random directory on tricorder.pi-hole.net.
The intent of this script is to allow users to self-diagnose their installations. This is accomplished by running tests against our software and providing the user with links to FAQ articles when a problem is detected. Since we are a small team and Pi-hole has been growing steadily, it is our hope that this will help us spend more time on development.
NOTE: All log files auto-delete after 48 hours and ONLY the Pi-hole developers can access your data via the given token. We have taken these extra steps to secure your data and will work to further reduce any personal information gathered.
Your debug log shows that Pi-hole is working properly at the following IP:
*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] impost.dellvery-45812.xyz is 0.0.0.0 on lo (127.0.0.1)
[✓] impost.dellvery-45812.xyz is 0.0.0.0 on eth0 (192.168.0.99)
[✓] doubleclick.com is 216.58.214.14 via a remote, public DNS server (8.8.8.8)
Your DHCP server (appears to be your router) is not distributing the IP of Pi-hole as DNS server:
*** [ DIAGNOSING ]: Discovering active DHCP servers (takes 10 seconds)
Scanning all your interfaces for DHCP servers
Timeout: 10 seconds
WARN: Could not sendto() in send_dhcp_discover() (/__w/FTL/FTL/src/dhcp-discover.c:233): Network is unreachable
* Received 548 bytes from eth0:192.168.0.1
Offered IP address: 192.168.0.156
Server IP address: 192.168.0.1
Relay-agent IP address: N/A
BOOTP server: (empty)
BOOTP file: (empty)
DHCP options:
Message type: DHCPOFFER (2)
server-identifier: 192.168.0.1
lease-time: 3600 ( 1h )
netmask: 255.255.255.0
router: 192.168.0.1
dns-server: 195.130.131.2
dns-server: 195.130.130.2
domain-name: "home"
default-ttl: 64
ntp-server: 195.130.132.20
ntp-server: 195.130.132.18
--- end of options ---
DHCP packets received on interface wlan0: 0
DHCP packets received on interface lo: 0
DHCP packets received on interface eth0: 1
From a client that you believe should be connected to the Pi-Hole for DNS (the Windows machine), from the command prompt or terminal on that client (and not via ssh or Putty to the Pi), what is the output of
nslookup pi.hole
nslookup flurry.com
nslookup flurry.com 192.168.0.99
If these show Pi-hole is answering the queries, then you need to look at other settings on the Windows machine. Browser set to private or secure DNS (which would bypass Pi-hole). Avast or other similar software. Any active VPN sessions, etc.
This was the correct and expected answer. Pi-hole blocked the domain per your blacklist.
