Hello,
I have a question,
after installing pi-hole in my dhcpcd.conf I see the following line
static domain_name_servers=127.0.0.1
which means the servers own dhcp server is localhost.
The issue here is that when pi-hole doens't work and dns won't start pi-hole isn't able to update so it is unable to repear itself using
where the fallbacks are the selected nameservers for pi-hole.
I just had this issue after some stupid mistake I made and I changed the setting here to 1.1.1.1 so I was able to fix pihole.
I can imagine others have the same issue,
Also you might can send those alternative dns server to the client using dhcp, so if only dns fails and dhcp works, users can still use the internet.
If this last think is a security concern, it would be a solution to make this configurable
It configures the global DNS settings, not DHCP, on the local Pi-hole device:
pi@noads:~ $ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 127.0.0.1
IP 127.0.0.1 on the local loopback network interface "lo" is where pihole-FTL is listening on DNS ports 53 TCP & UDP:
pi@noads:~ $ ip a show lo
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
I believe if you configure other DNS servers here, it might break the displaying of the client hostnames on the web GUI.
I believe the web GUI also uses 127.0.0.1 for DNS resolution to display the client hostnames.
Maybe a mod or dev can confirm ?
Dont need to.
You can query for IPv6 addresses using only IPv4:
pi@noads:~ $ host -t aaaa pi-hole.net 8.8.8.8
Using domain server:
Name: 8.8.8.8
Address: 8.8.8.8#53
Aliases:
pi-hole.net has IPv6 address 2604:a880:400:d0::1071:1
But if want to go IPv6 all out, yes I would replace 127.0.0.1 with ::1 and leave out the subnet mask /128.
Pi-hole is listening to both (see previous posted netstat output).
If you mean the subnet mask for the lo interface, thats set by the distro and not the Pi-hole install.
The lo interface is not there for Pi-hole alone, other software make use if this loopback interface as well.