Weird DNS issue

sqpp · May 24, 2023, 8:08pm

The issue I am facing:

DNS issues directly on the Raspberry.

Details about my system:

Since today I am experiencing strange issues, but I haven't really touched anything, however, I found something interesting. I have set my router 's DNS settings back to 8.8.8.8 for the time being, this works great on any other devices, but when I try to ping google.com for example, it says: temporary failure in name resolution, once I start the pihole, it works instantly, which tells me my raspberry is still using the PiHole as the DNS server, but how?

I use netplan and I don't have any DNS related settings, it gets from the gateway/router itself.

What I have changed since installing Pi-hole:

I only changed the proxy to OpenLiteSpeed which runs on port 80 and 443, as I have that as my daily driver.

rdwebdesign · May 24, 2023, 10:13pm

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

sqpp · May 25, 2023, 10:10pm

Sure, here you go:

https://tricorder.pi-hole.net/n5UjhTLV/

yubiuser · May 26, 2023, 8:17pm

Your device hosting Pi-hole is using Pi-hole for DNS resolution

-rw-r--r-- 1 root root 38 May 26 00:02 /etc/resolv.conf
   nameserver 127.0.0.11
   options ndots:0

Try, setting namserver in /etc/resolv.conf to any other (external) DNS server

sqpp · May 26, 2023, 8:19pm

I also did have systemd-resolve disabled for some reason.

yubiuser · May 26, 2023, 8:20pm

github.com

pi-hole/pi-hole/blob/d885e92674e8d8d9a673b35ae706b2c49ea05840/automated install/basic-install.sh#L1591-L1612


      
          disable_resolved_stublistener() {
              printf "  %b Testing if systemd-resolved is enabled\\n" "${INFO}"
              # Check if Systemd-resolved's DNSStubListener is enabled and active on port 53
              if check_service_active "systemd-resolved"; then
                  # Check if DNSStubListener is enabled
                  printf "  %b %b Testing if systemd-resolved DNSStub-Listener is active" "${OVER}" "${INFO}"
                  if ( grep -E '#?DNSStubListener=yes' /etc/systemd/resolved.conf &> /dev/null ); then
                      # Disable the DNSStubListener to unbind it from port 53
                      # Note that this breaks dns functionality on host until dnsmasq/ftl are up and running
                      printf "%b  %b Disabling systemd-resolved DNSStubListener" "${OVER}" "${TICK}"
                      # Make a backup of the original /etc/systemd/resolved.conf
                      # (This will need to be restored on uninstallation)
                      sed -r -i.orig 's/#?DNSStubListener=yes/DNSStubListener=no/g' /etc/systemd/resolved.conf
                      printf " and restarting systemd-resolved\\n"
                      systemctl reload-or-restart systemd-resolved
                  else
                      printf "%b  %b Systemd-resolved does not need to be restarted\\n" "${OVER}" "${INFO}"
                  fi
              else
                  printf "%b  %b Systemd-resolved is not enabled\\n" "${OVER}" "${INFO}"

This file has been truncated. show original

sqpp · May 26, 2023, 8:29pm

Now it makes sense, thank you.

system · June 17, 2023, 4:49pm

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