No i meant in my interfaces.
The dns-nameserver will be commented out with a hash at the start (# which means disabled) for DHCP. DietPi-Config > Networking will do this automatically for you when using it to setup network.
Would a fix for me be uninstalling resolvconf after installing 103, and manually setting the vallues in that file?
Yep, that would work for /etc/resolv.conf. If you are running Jessie, you could try disable/enable the service:
Ideally, its better practice to just set dns-nameserver in /etc/network/interfaces. This will override resolv.conf
For ethernet with DHCP:
Code: Select all
iface eth0 inet dhcp
#The below is google DNS nameservers. Put a hash sign before dns-nameservers to disable
dns-nameservers 184.108.40.206 220.127.116.11
Reboot system once done.
When you are running DHCP:
I'm very new to linux and everything i do is stitching together different tutorials on internet.
I fail to understand what the differences are with having dns entries on the interface, and the use of the resolv.conf file.
The IP entries in /etc/network/interfaces are ignored. Resolv.conf is then updated with the DNS server it pulled from your router. You can override the resolv.conf values by enabling dns-nameserver in /etc/network/interfaces
If your running STATIC IP
All the IP settings from /etc/network/interfaces will be used. Resolv.conf is no longer used. dns-nameserver value from /etc/network/interfaces will be used, and, must be enabled.
(On another note, I'm having a new router for chrismass, which might also solve all these issues
Hopefully it should, depends on which one santa is going to give you. Just dont be naughty or you'll end up with a coal powered router. I've had coal powered stuff in the past