Pihole DNS Upstream Issues

I am unable to load any sites due to queries not resolving.
I just had the modem replaced to a Bell Giga Hub. Hardware version: 5690-000001-000.
It looks like it's failing to receive a response from the gateway which is the modem but I have no issues reaching it from a different client. I tried port forwarding on 53 but that didn't do it.
I reinstalled Raspberry Pi OS and Pihole because I initially had some NIC config issues.

Pi-hole
Toggle navigationhostname: raspberrypi
Pi-hole logo
Status

 Active
 Load:  0  0  0
 Memory usage:  20.0 %
 Temp: 42.2 °C
MAIN
 Dashboard
ANALYSIS
 Query Log
 Long-term Data
GROUP MANAGEMENT
 Groups
 Clients
 Domains
 Adlists
DNS CONTROL
 Disable Blocking   
 Local DNS
SYSTEM
 Tools
 Pi-hole diagnosis
 Update Gravity
 Search Adlists
 Audit log
 Tail pihole.log
 Tail FTL.log
 Generate debug log
 Network
 Settings
DONATE
 Donate
Generate debug log
Options:
Execute database integrity check. This can add several minutes to debug log time.
Upload debug log and provide Debug Token. The URL token will be shown at the end of the report, once finished.

Once you click this button a debug log will be generated and can automatically be uploaded if we detect a working internet connection.

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.

***Debug log contents removed by moderator and made private.***

********************************************
********************************************
[✓] ** FINISHED DEBUGGING! **

   * The debug log can be uploaded to tricorder.pi-hole.net for sharing with developers only.
[i] Debug script running in automated mode
    * Using curl for transmission.
    * curl failed, contact Pi-hole support for assistance.
    * Error message: curl: (6) Could not resolve host: tricorder.pi-hole.net

[✗] There was an error uploading your debug log.
   * Please try again or contact the Pi-hole team for assistance.
   * A local copy of the debug log can be found at: /var/log/pihole/pihole_debug.log

Are you running any firewall or other software on your network that is blocking outgoing DNS traffic on port 53?

[✗] Failed to resolve doubleclick.com via a remote, public DNS server (8.8.8.8)

Also check if a traceroute comes through:

pi@ph5b:~ $ traceroute -n 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
[..]
 7  8.8.8.8  8.259 ms  9.118 ms  8.639 ms

Your router might drop ICMP ping requests on its firewall for the own host.
This is highly unlikely but still :wink:

Resolved my issue by letting Pihole handle DHCP. Not really sure why that would cause issues with ICMP packets or reaching upstream DNS.

Thanks for the replies.

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