Pi hole should be functioning normally, DNS settings have been configured on router and pi-hole functioned for a few minutes.
No queries are appearing on admin panel, but sometimes clients will connect briefly before returning to 0. Pihole -g command also will not work so I can’t add to my blocklist.
This was successfull on
gravity_count 66054
Last gravity run finished at: Mon Mar 8 23:31:26 EST 2021
Please run
nslookup pi.hole
nslookup pi.hole 192.168.1.113
from one of your clients.
Is Pi-hole your router's upstream DNS server? Because your router advertises itself via DHCP as DNS server to clients
* Received 332 bytes from eth0:192.168.1.1
Offered IP address: 192.168.1.113
Server IP address: 192.168.1.1
Relay-agent IP address: N/A
BOOTP file: (empty)
DHCP options:
Message type: DHCPOFFER (2)
server-identifier: 192.168.1.1
lease-time: 86400 ( 1d )
renewal-time: 43200 ( 12h )
rebinding-time: 75600 ( 21h )
netmask: 255.255.255.0
broadcast: 192.168.1.255
hostname: "ubuntu-brick"
dns-server: 192.168.1.1
router: 192.168.1.1
--- end of options ---
DHCP packets received on interface wlp2s0: 0
DHCP packets received on interface lo: 0
DHCP packets received on interface eth0: 1
nslookup pi.hole returns with
nslookup pi.hole
Server: The-Park.lxtnkyaa.metronetinc.net
Address: 192.168.1.1
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to The-Park.lxtnkyaa.metronetinc.net timed-out
and for nslookup pi.hole 192.168.1.113
nslookup pi.hole 192.168.1.113
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 192.168.1.113
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out
Pi-hole is not set as routers upstream DNS because from my interpretation of the setup guide I do not have the correct router to do that.
Just to make sure I answered that question correctly, my router page has DHCP static DNS set to the local ip of the device running pi-hole. Upstream DNS servers on the admin panel is set to OpenDNS because the setup guide implied that I can't use custom upstream DNS since my router does not support additional dynmasq queries.
Still, your router advertises itself as DNS server
Also the client you posted the results is using primarily your router for DNS resolution
But there seems to be network connectivity issues on your network as both requests could not get an answer
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.