DietPi version | _DIETPI_VERSION_CORE=8
Distro version | bullseye 0
Kernel version | Linux RPi-4 5.15.76-v8+ #1597 SMP PREEMPT Fri Nov 4 12:16:41 GMT 2022 aarch64 GNU/Linux
SBC model | RPi 4 Model B (aarch64)
Power supply used | PoE
SD card used | SAMSUNG EVO
Additional Information (if applicable)
Software title | (EG: Nextcloud)
Was the software title installed freshly or updated/migrated?
Can this issue be replicated on a fresh installation of DietPi?
← If you sent a “dietpi-bugreport”, please paste the ID here →
Bug report ID | Reference code: af5cc7a0-c74e-461b-a889-2bd9dad3927b
Steps to reproduce
When I go to dietpi-config and change my DNS settings it won’t take the new settings. After applying the changes Ethernet details show all 0s for all entries. After restarting the RPi it goes back to it’s old settings (IP, MASK, DNS, Gateway). It will not retain the new DNS selected from the list.
7: Network Options: Adapters
Change Mode: DHCP to STATIC
Copy: Copy current address to static
Apply: Save all changes and restart networking.
New network settings including new DNS settings should persist.
After restarting the RPi, it goes back to it’s old settings.
# Generated by dhcpcd from eth0.dhcp
# /etc/resolv.conf.head can replace this line
# /etc/resolv.conf.tail can replace this line
I switched to STATIC and selected Quad9 for DNS. Rebooted and these are the results. Looks after all the changes are NOT persistent. For some reason it keeps reverting back to what is advertised by the DHCP.
As well due to PiVPN installed? I checked their installer and they install dhcpcd5 on Raspbian (our ARMv6 RPi image) since a long time, on Debian since a shorter while (to support RPi OS 64-bit). I’ll open a PR to replace the condition which whether dhcpcd is actually installed, to not mess with the systems network stack.