I was using dnsmasq for forward and reverse local resolution but now that's gone...
I have my /etc/hosts file setup with the names I want to use of the local machines I (not hostnames) and I don't use DHCP anywhere. I'm also using dnscrypt so I don't think unbound is a way forward either.
Any way I can use FTLDNS to achieve the same behavior as dnsmasq?
This should work already, since FTLDNS contains dnsmasq and runs in place of the dnsmasq process. All your existing dnsmasq configuration files should work as before. This command from the Linux terminal will show which dnsmasq version is running:
dig chaos txt version.bind +short
What are the contents of your /etc/hosts file?
Also, please generate a debug log, upload it and post the token here so we can look under the hood.
If I try and ping eve-ng from any of my workstations the pi-hole won't resolve the name to the IP address.
It worked fine 2 days ago using dnsmasq before I updated my pihole.
C:\>nslookup eve-ng
Server: pi-hole
Address: 192.168.1.20
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to pi-hole timed-out
C:\>nslookup eve-ng 192.168.1.20
Server: pi-hole
Address: 192.168.1.20
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to pi-hole timed-out
All devices with an IP address are using the pihole as their only DNS and local resolution has been working fine with dnsmasq for the past 3 years. I updated my pihole 2 days ago and now local resolution no longer works.
Are there any config files for ftldns that i have to edit to get this working? i had to edit dnsmasq.conf to get it working 3 years ago.
Edit - we were typing at the same time and your reply above already addresses some of this.
With FTLDNS, you don't want to make changes to dnsmasq.conf. This is set up as a directory index. Make changes as shown in the commented block below:
cat /etc/dnsmasq.conf
conf-dir=/etc/dnsmasq.d
cd /etc/dnsmasq.d
pi@Pi-3B-DEV:/etc/dnsmasq.d $ ls -lh
total 4.0K
-rw-r--r-- 1 root root 1.6K Mar 31 16:05 01-pihole.conf
cat 01-pihole.conf
# Pi-hole: A black hole for Internet advertisements
# (c) 2017 Pi-hole, LLC (https://pi-hole.net)
# Network-wide ad blocking via your own hardware.
#
# Dnsmasq config for Pi-hole's FTLDNS
#
# This file is copyright under the latest version of the EUPL.
# Please see LICENSE file for your rights under this license.
###############################################################################
# FILE AUTOMATICALLY POPULATED BY PI-HOLE INSTALL/UPDATE PROCEDURE. #
# ANY CHANGES MADE TO THIS FILE AFTER INSTALL WILL BE LOST ON THE NEXT UPDATE #
# #
# IF YOU WISH TO CHANGE THE UPSTREAM SERVERS, CHANGE THEM IN: #
# /etc/pihole/setupVars.conf #
# #
# ANY OTHER CHANGES SHOULD BE MADE IN A SEPARATE CONFIG FILE #
# WITHIN /etc/dnsmasq.d/yourname.conf #
###############################################################################
...
You have the server= directive configured twice on different ports.
Try configure with only one server= directive.
The one that needs to answer upstream.
EDIT: I would prefer delete the one in /etc/dnsmasq.d/02-dnscrypt.conf
EDIT2: or did you intentionally configure two upstream DNS servers that run on different ports ?
I added:
domain-needed
bogus-priv
interface=eth0
domain=local.lan
local=/local.lan/
The rest of the config in 01-pihole.conf it did it's self during the update.
I've created a file as suggested:/etc/dnsmasq.d/yourname.conf
and added the config from /etc/dnsmasq.conf.old to this file (not all of it, just the bits listed above)
IT'S WORKING!!!!
Thank you to the both of you for helping "resolve" my issue.