Dnsmasq inactive, falling back to fallback DNS

Help
1

Currently, none of my traffic goes through the filtering, it seems to fallback to the fallback DNS.

I ran the debugger and saw that dnsmasq isn't working.

I've run this as well:

sudo netstat -nltup | grep 'Proto|:53 |:67 |:80 |:471'

And saw that FTL is running:

Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 127.0.0.1:4711 0.0.0.0:* LISTEN 11602/pihole-FTL
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 7067/lighttpd
tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN 11602/pihole-FTL
tcp6 0 0 ::1:4711 :::* LISTEN 11602/pihole-FTL
tcp6 0 0 :::80 :::* LISTEN 7067/lighttpd
tcp6 0 0 :::53 :::* LISTEN 11602/pihole-FTL
udp 0 0 0.0.0.0:53 0.0.0.0:* 11602/pihole-FTL
udp6 0 0 :::53 :::* 11602/pihole-FTL

Debug Token:

ame8qfp7ug

2

What “fallback” DNS do you have set and where?

3

@jfb in this file:

/etc/systemd/resolved.conf

I had to do this manually because during the install Pi had no access to the outside world and setup didn't finish properly.

5

@anon55913113 I don't know why. I went over 30 posts here and tried different stuff to make it work.
What should I put in /etc/resolve.conf then?

7

@anon55913113 can you post me the exact input for /etc/resolv.conf? is it the same as resolver.conf?
Currently my resolv.conf has only the nameserver.

Thank you!

10

@anon55913113 thanks, but I don't understand.
What upgrade?
I have a fresh install of Pihole that just doesn't work.

12

@anon55913113 ok, I've done it, issue still remains the same.

After further checking I saw that dnsmasq isn't even installed on my Pi. When I do install it then FTL can't start (I assume they listen to the same port).

Also, dnsmasq.conf wasn't including 01-pihole.conf file, I fixed that too (I assume its supposed to include it).

Now, when running debug, I see this:

*** [ DIAGNOSING ]: Networking
[✗] No IPv4 address(es) found on the wlan0 interface.

[✗] No IPv6 address(es) found on the wlan0 interface.

[i] Default IPv4 gateway: 192.168.0.1

*** [ DIAGNOSING ]: Ports in use
*:22 sshd (IPv4)
*:22 sshd (IPv6)
*:53 dnsmasq (IPv4)
*:53 dnsmasq (IPv6)
*:80 lighttpd (IPv4)
*:80 lighttpd (IPv6)

*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] wrxviatrhzoists.review is 162.255.119.155 via localhost (127.0.0.1)
[✗] Failed to resolve wrxviatrhzoists.review via Pi-hole (192.168.0.100)
[✓] doubleclick.com is 216.58.210.14 via a remote, public DNS server (8.8.8.8)

*** [ DIAGNOSING ]: Pi-hole processes
[✓] dnsmasq daemon is active
[✓] lighttpd daemon is active
[✓] pihole-FTL daemon is active

So..

  1. Installing DNSMasq manually was a good idea? if so, what I do about FTL?
  2. Should I give up on life now? :frowning:

Thanks

14

Ok, so I figured what the issue was.

I used Ethernet and not WiFi to connect my Pi. Completely forgot about it, usually my Pies connected via WiF.

I re-installed, and it all works now.

SOORRRYYYY for wasting your time,
@anon55913113 thank you!!

16

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