I know there probably isn't a "right" way to do this but, while I've
been trying to sort out how to make my dns/dhcp more resilient, I have
looked at my existing dnsmasq running on a Pi and it looks a bit odd
to me.
It's a pretty standard, off the shelf Raspberry Pi installation using
the Lite version as it's headless. The dnsmasq.conf file has been
changed quite a lot over the years though and I wonder if it's still
optimal.
The upstream servers *seem* to be specified in /etc/dhcpcd.conf as
follows:-
# Example static IP configuration:
interface eth0
static ip_address=192.168.1.2/24
#static ip6_address=fd51:42f8:caae:d92e::ff/64
static routers=192.168.1.1
static domain_name_servers=192.168.1.2 1.1.1.1 212.159.13.49
/etc/resolv.conf is:-
# Generated by resolvconf
nameserver 127.0.0.1
So, is the above OK? Is it the "right" way to do it? ....etc.
The /etc/resolv.conf is written by /etc/init.d/dnsmasq and is, I
believe, correct so that dnsmasq does local cacheing. However I'm not
sure about the upstream servers in /etc/dhcpcd.conf including the
local host as well.
--
Chris Green
_______________________________________________
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
