Pi-hole as DNS server loses internet, but I can connect to admin interface

Expected Behaviour:

modem/router changed dns, all devices are able to connect to internet and have adblock

Actual Behaviour:

The webpage shows pihole up and running and even receiving queries, however any device such as laptop or phone is unable to connect to anything outside the LAN

Debug Token:https://tricorder.pi-hole.net/KwwuQgNo/

Your debug log shows that Pi-hole is working properly:

*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] sexyhotgirls.blogspot.ae is 0.0.0.0 on lo (127.0.0.1)
[✓] sexyhotgirls.blogspot.ae is 0.0.0.0 on eth0 (172.17.0.2)
[✓] doubleclick.com is 142.251.12.138 via a remote, public DNS server (8.8.8.8)

It is receiving queries from the router and answering those queries.

   Mar  4 06:26:57 dnsmasq[10685]: query[A] guarded-meadow-30850.herokuapp.com from 172.17.0.1
   Mar  4 06:26:57 dnsmasq[10686]: query[HTTPS] guarded-meadow-30850.herokuapp.com from 172.17.0.1
   Mar  4 06:26:57 dnsmasq[10686]: forwarded guarded-meadow-30850.herokuapp.com to 1.1.1.1
   Mar  4 06:26:57 dnsmasq[10686]: reply guarded-meadow-30850.herokuapp.com is NODATA
   Mar  4 06:26:57 dnsmasq[10685]: forwarded guarded-meadow-30850.herokuapp.com to 1.1.1.1
   Mar  4 06:26:57 dnsmasq[10685]: reply guarded-meadow-30850.herokuapp.com is 34.201.81.34
   Mar  4 06:26:57 dnsmasq[10685]: reply guarded-meadow-30850.herokuapp.com is 54.208.186.182
   Mar  4 06:26:57 dnsmasq[10685]: reply guarded-meadow-30850.herokuapp.com is 54.224.34.30
   Mar  4 06:26:57 dnsmasq[10685]: reply guarded-meadow-30850.herokuapp.com is 54.243.129.215

The DHCP discovery test was not successful:

*** [ 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
   WARN: Could not sendto() in send_dhcp_discover() (/__w/FTL/FTL/src/dhcp-discover.c:233): Network is unreachable
   DHCP packets received on interface sit0: 0DHCP packets received on interface tunl0: 0
   
   DHCP packets received on interface eth0: 0
   DHCP packets received on interface lo: 0

Check on individual clients to see which DNS clients are using.

oh, wait I'm dumb mb I had my network profile as public and not private now it works! thanks anyways tho!!!

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.