Pihole + pivpn. static ip's stop dns and ftl

Please follow the below template, it will help us to help you!

Expected Behaviour:

assigning a static ip to a device not stopping dns and ftl

Actual Behaviour:

static ip's stopping dns and ftl

Debug Token:

not available because it cant upload it

You'll need to explain or provide some kind of information for us to help you with.

Check /etc/dnsmasq.d/04-pihole-static-dhcp.conf and remove any duplicates.

This will temporarily reset the nameserver on the Pi to bypass Pi-Hole DNS to allow you to upload a debug log.

sudo nano /etc/resolv.conf

edit nameserver 127.0.0.1 to nameserver 9.9.9.9 or your preferred third party DNS service, save and exit

Run pihole -d and upload the debug log

copy and paste the entire log into a reply, and I will quickly make it private.

Got it and deleted the link from your post.

It doesn't appear the pihole-FTL is running; it should be on port 53.

*** [ DIAGNOSING ]: Ports in use
*:5900 vncserver- (IPv6)
*:5900 vncserver- (IPv4)
*:22 sshd (IPv4)
*:22 sshd (IPv6)
*:80 is in use by lighttpd
*:80 is in use by lighttpd

Let's check all your ports for activity - what is the output of these commands from the Pi terminal:

sudo service pihole-FTL status

sudo netstat -nltup | grep 'Proto\|:53 \|:5053 \|:5353 \|:8953 \|:67 \|:80 \|:471'

From the Pi terrminal, what is the output of the following:

nslookup pi.hole

nslookup flurry.com

nslookup flurry.com 1.1.1.1

Edit, also include this command output:

sudo grep -v '#\|^$' -R /etc/dnsmasq.*

With your existing configuration as posted in your recent reply, what is the output of

sudo service pihole-FTL status

pihole-FTL dnsmasq-test

And, are you still experiencing the same problem in this configuration?

Are you certain? You have static IP'S listed in a configuration file inside /etc/dnsmasq.d. I don't believe Linux reads the file extension to see if the file should be used. Thus, all files in the directory are used.

Please post the complete contents of any files in /etc/dnsmasq.d that contain any static IP mappings, commented or not.

What IP did you intend to assign with this configuration line?

dhcp-host=AC:22:05:F2:1E:CA,Modem

Your next logical troubleshooting step is to enable a single static IP in one of your configuration files, restart FTL and see if there are errors. If so, figure out what's happening with that single configuration change. If no error, then add static IPs one at a time until you get an error, then stop and address that error.

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