Expected Behaviour:
DNS service should be running
Actual Behaviour:
DNS Service not running. Appears to sporadically run, but at most times shows as not running.
DNS service should be running
DNS Service not running. Appears to sporadically run, but at most times shows as not running.
There are a few issues noted in your debug log.
First, your DHCP server is distributing a number of DNS servers other than Pi-hole. Pi-hole is on IP 192.168.253.180.
*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] www.liquidityaggregator.com is 0.0.0.0 on lo (127.0.0.1)
[✓] www.liquidityaggregator.com is 0.0.0.0 on ens160 (192.168.253.180)
Your DNS server is distributing this:
*** [ DIAGNOSING ]: Discovering active DHCP servers (takes 10 seconds)
Scanning all your interfaces for DHCP servers
Timeout: 10 seconds
* Received 320 bytes from ens160:192.168.253.1
Offered IP address: 192.168.253.180
Server IP address: 192.168.253.1
Relay-agent IP address: N/A
BOOTP server: (empty)
BOOTP file: (empty)
DHCP options:
Message type: DHCPOFFER (2)
server-identifier: 192.168.253.1
lease-time: 86400 ( 1d )
renewal-time: 43200 ( 12h )
rebinding-time: 75600 ( 21h )
netmask: 255.255.255.0
domain-name: "***redacted***"
broadcast: 192.168.253.255
dns-server: 192.168.253.180
dns-server: 192.168.253.1
dns-server: 192.168.253.101
dns-server: 8.8.8.8
router: 192.168.253.1
--- end of options ---
DHCP packets received on interface ens160: 1
What is this DNS server in use by Pi-hole as the upstream DNS server?
PIHOLE_DNS_1=192.168.253.101
With logging disabled, your debug log doesn't show any of the recent query activity.
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.