Fresh install of pihole.
first nothing shows in querys (nothing)
I can resolv domain names with pihole (using nslookup)
the domains I insert as blacklisted is getting resolved and the only blocks that works is that ad-list thats available when installing.
have updated, restarted pihole.
nothings works.
Are you sure your devices are using Pi-hole as DNS server?
Did you make changes to your router or devices to use Pi-hole?
Yes (manuelly configured dns in ipv4 settings)
And yes (have also tried with configure the dhcp server to use pihole dns server
I have installed it on a azure Virtual Machine
And set up a site 2 site vpn tunnel between azure cloud and my firewall.
Please upload a debug log and post just the token URL that is generated after the log is uploaded by running the following command from the Pi-hole host terminal:
pihole -d
or do it through the Web interface:
Tools > Generate Debug Log
Your debug log shows that Pi-hole is fully operational and does block if requested. However, it has barely received any queries
[2023-04-19 12:38:26.778 2272M] Imported 11 queries from the long-term database
[2023-04-19 12:38:26.778 2272M] -> Total DNS queries: 11
[2023-04-19 12:38:26.778 2272M] -> Cached DNS queries: 7
[2023-04-19 12:38:26.778 2272M] -> Forwarded DNS queries: 0
[2023-04-19 12:38:26.778 2272M] -> Blocked DNS queries: 4
[2023-04-19 12:38:26.778 2272M] -> Unknown DNS queries: 0
[2023-04-19 12:38:26.778 2272M] -> Unique domains: 4
[2023-04-19 12:38:26.778 2272M] -> Unique clients: 4
[2023-04-19 12:38:26.778 2272M] -> Known forward destinations: 0
Maybe it's because Pi-hole's IP does not match the one distributed by your DHCP server.
Please post the output of those commands from a client
nslookup pi.hole
nslookup flurry.com
nslookup flurry.com @PI-HOLE_IP
Your Pi-hole is configured for the ethernet interface at this IP:
*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] netflipld.com is 0.0.0.0 on lo (127.0.0.1)
[✓] netflipld.com is 0.0.0.0 on eth0 (**192.168.59.196**)
[✓] doubleclick.com is 142.250.74.46 via a remote, public DNS server (8.8.8.8)
Your DHCP server (which may be on a different VLAN, is offering up a different DNS server than Pi-hole.
*** [ DIAGNOSING ]: Discovering active DHCP servers (takes 10 seconds)
Scanning all your interfaces for DHCP servers
Timeout: 10 seconds
* Received 372 bytes from eth0:168.63.129.16
Offered IP address: 192.168.59.196
Server IP address: 168.63.129.16
Relay-agent IP address: 168.63.129.16
BOOTP server: OSL211051213045
BOOTP file: (empty)
DHCP options:
netmask: 255.255.255.240
router: 192.168.59.193
dns-server: 168.63.129.16
domain-name: "01oh4d44njmubfwqt2mmpi0znc.oslx.internal.cloudapp.net"
lease-time: Infinite
Message type: DHCPOFFER (2)
server-identifier: 168.63.129.16
renewal-time: Infinite
rebinding-time: Infinite
Unknown option 245: A8 3F 81 10 (length 4)
--- end of options ---
* Received 372 bytes from eth0:168.63.129.16
Offered IP address: 192.168.59.196
Server IP address: 168.63.129.16
Relay-agent IP address: 168.63.129.16
BOOTP server: OSL211051213045
BOOTP file: (empty)
DHCP options:
netmask: 255.255.255.240
router: 192.168.59.193
dns-server: 168.63.129.16
domain-name: "01oh4d44njmubfwqt2mmpi0znc.oslx.internal.cloudapp.net"
lease-time: Infinite
Message type: DHCPOFFER (2)
server-identifier: 168.63.129.16
renewal-time: Infinite
rebinding-time: Infinite
Unknown option 245: A8 3F 81 10 (length 4)
--- end of options ---
DHCP packets received on interface eth0: 2
DHCP packets received on interface lo: 0
DHCP packets received on interface enP5555s1: 0
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.