# Dnsmasq inactive, falling back to fallback DNS

**URL:** <https://discourse.pi-hole.net/t/dnsmasq-inactive-falling-back-to-fallback-dns/12859>\
**Category:** Help\
**Created:** [September 13, 2018, 12:46am UTC](https://discourse.pi-hole.net/t/dnsmasq-inactive-falling-back-to-fallback-dns/12859 "2018-09-13T00:46:35Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Udi\_M](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/u/8491ac/32.png) [@Udi\_M](https://discourse.pi-hole.net/u/Udi_M)\
**Post date:** [September 13, 2018, 12:46am UTC](https://discourse.pi-hole.net/t/dnsmasq-inactive-falling-back-to-fallback-dns/12859/1 "2018-09-13T00:46:35Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![jfb](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/jfb/32/4332_2.png) [@jfb](https://discourse.pi-hole.net/u/jfb)\
**Post date:** [September 13, 2018, 12:54am UTC](https://discourse.pi-hole.net/t/dnsmasq-inactive-falling-back-to-fallback-dns/12859/2 "2018-09-13T00:54:13Z")

</div>

> [@Udi\_M](#):
>
> it seems to fallback to the fallback DNS.

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

---

<div class="post-metadata">

**Author:** ![Udi\_M](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/u/8491ac/32.png) [@Udi\_M](https://discourse.pi-hole.net/u/Udi_M)\
**Post date:** [September 13, 2018, 7:59am UTC](https://discourse.pi-hole.net/t/dnsmasq-inactive-falling-back-to-fallback-dns/12859/3 "2018-09-13T07:59:50Z")

</div>

@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.

---

<div class="post-metadata">

**Author:** ![Udi\_M](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/u/8491ac/32.png) [@Udi\_M](https://discourse.pi-hole.net/u/Udi_M)\
**Post date:** [September 13, 2018, 9:06am UTC](https://discourse.pi-hole.net/t/dnsmasq-inactive-falling-back-to-fallback-dns/12859/5 "2018-09-13T09:06:05Z")

</div>

@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?

---

<div class="post-metadata">

**Author:** ![Udi\_M](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/u/8491ac/32.png) [@Udi\_M](https://discourse.pi-hole.net/u/Udi_M)\
**Post date:** [September 13, 2018, 11:14am UTC](https://discourse.pi-hole.net/t/dnsmasq-inactive-falling-back-to-fallback-dns/12859/7 "2018-09-13T11:14:23Z")

</div>

@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!

---

<div class="post-metadata">

**Author:** ![Udi\_M](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/u/8491ac/32.png) [@Udi\_M](https://discourse.pi-hole.net/u/Udi_M)\
**Post date:** [September 13, 2018, 1:23pm UTC](https://discourse.pi-hole.net/t/dnsmasq-inactive-falling-back-to-fallback-dns/12859/10 "2018-09-13T13:23:08Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Udi\_M](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/u/8491ac/32.png) [@Udi\_M](https://discourse.pi-hole.net/u/Udi_M)\
**Post date:** [September 13, 2018, 2:07pm UTC](https://discourse.pi-hole.net/t/dnsmasq-inactive-falling-back-to-fallback-dns/12859/12 "2018-09-13T14:07:36Z")

</div>

@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
> 
> - Pinging 192.168.0.1...  
> ping: Warning: source address might be selected on device other than wlan0.  
> [✗] Gateway did not respond. ([Why is a default gateway important for Pi-hole?](https://discourse.pi-hole.net/t/why-is-a-default-gateway-important-for-pi-hole/3546))
> 
> \*\*\* [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? ☹

Thanks

---

<div class="post-metadata">

**Author:** ![Udi\_M](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/u/8491ac/32.png) [@Udi\_M](https://discourse.pi-hole.net/u/Udi_M)\
**Post date:** [September 13, 2018, 3:23pm UTC](https://discourse.pi-hole.net/t/dnsmasq-inactive-falling-back-to-fallback-dns/12859/14 "2018-09-13T15:23:57Z")

</div>

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!!

---

<div class="post-metadata">

**Author:** ![system](https://discourse.pi-hole.net/uploads/default/original/3X/7/c/7c8792f649eeb921c5d2b4c41564ffa873d9a2b8.png) [@system](https://discourse.pi-hole.net/u/system)\
**Post date:** [October 4, 2018, 3:47pm UTC](https://discourse.pi-hole.net/t/dnsmasq-inactive-falling-back-to-fallback-dns/12859/16 "2018-10-04T15:47:17Z")

</div>

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