@rern
PI Zero W RA+Re5 (updated to 20200827)
Something is changing the file /etc/resolv.conf, I don't know what it is but it appears to be either at a reboot or overnight. This PI has been running for a couple of days without any problem then this morning I tried to listen to a web radio and nothing happened. As soon as I clicked the play button (top bar) it revered to the stop button. I have been having problems with this PI not finding its domain server (see
network-name-resolution-t7101.html) and as well as using a modified /etc/nsswitch.conf file I also updated /etc/resolvconf.conf to be:
# Configuration for resolvconf(8)
# See resolvconf.conf(5) for details
resolv_conf=/etc/resolv.conf
# If you run a local name server, you should uncomment the below line and
# configure your subscribers configuration files below.
#name_servers=127.0.0.1
name_servers=192.168.86.10
I then used resolvconf -u
to update the /etc/resolv.conf file as suggested by the Arch-Linux docs which gave me /etc/resolv.conf set to:
# Generated by resolvconf
domain lan
nameserver 192.168.86.10
nameserver 192.168.86.1
This morning however (after NO changes by me at all), /etc/resolv.conf was set to:
# This file is managed by man:systemd-resolved(8). Do not edit.
#
# This is a dynamic resolv.conf file for connecting local clients directly to
# all known uplink DNS servers. This file lists all configured search domains.
#
# Third party programs should typically not access this file directly, but only
# through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a
# different way, replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.
nameserver 1.1.1.1
nameserver 9.9.9.10
nameserver 8.8.8.8
# Too many DNS servers configured, the following entries may be ignored.
nameserver 2606:4700:4700::1111
nameserver 2620:fe::10
nameserver 2001:4860:4860::8888
# Configuration for resolvconf(8)
# See resolvconf.conf(5) for details
Hence the PI knew nothing about my DNS server and I DO NOT use IP6 addresses at all on my network, it takes me all my time to understand IP4 let alone a move to IP6
What could be causing this to happen and how do I stop it happening ? Are there any log files anywhere that might help explain what is going on ? If not perhaps this might be a useful addition in future to debug this and other issues ?
Regards.
Chris