How do I get resolvconf to regenerate resolv.conf after I change /etc/network/interfaces?
Andrew Mclaughlin
After updating /etc/network/interfaces with something very similar to below, how do I get /etc/resolv.conf to update? I tried (as root) resolver -u, service networking restart but they didn't work. I also fixed the symlink for resolv.conf and tried resolver -u again. Finally in frustration I rebooted, which did fix the problem by rebuilding /etc/resolv.conf.
Ubuntu 12.04, 64bit server, all the latest patches installed.
Example /etc/network/interfaces:
iface eth0 inet static address 192.168.3.3 netmask 255.255.255.0 gateway 192.168.3.1 dns-search example.com dns-nameservers 192.168.3.45 192.168.8.10 2 12 Answers
service networking restart is not always a reliable way of down-upping all interfaces.
The resolvconf -u command only updates resolv.conf from resolvconf's own database. You need to update the database.
To update the database you have to call resolvconf with the -a or -d option. That happens behind the scenes when you run ifup or ifdown. So, normally, as with any other change to /etc/network/interfaces, to activate changes to the dns-* options you have to ifdown the interface in question and ifup it again. Or you can reboot.
If you want to make changes to an interface without ifdownupping it (perhaps because you are administering the machine remotely and happen to be connected via that interface, natch) then you can achieve the same result by running resolvconf directly from the command line. This requires a bit more knowledge of resolvconf's semantics. Assume the relevant /e/n/i stanza is
iface IIII FFFF static address ... ... dns-nameservers X.X.X.X Y.Y.Y.Y dns-search SSSSwhere FFFF is an address family ("inet" or "inet6").
To activate these dns-* options you run resolvconf as follows (yes, with newlines in the string piped to resolvconf).
echo "nameserver X.X.X.X
nameserver Y.Y.Y.Y
search SSSS" | sudo resolvconf -a IIII.FFFFFor the stanza given in the question this would be the following.
echo "nameserver 192.168.3.45
nameserver 192.168.8.10
search example.com" | sudo resolvconf -a eth0.inetConsult the resolvconf(8) manual page and the resolvconf package README file (/usr/share/doc/resolvconf/README.gz) for more information.
9Although the manpage isn't installed by default it's documented via the update scripts option, just run:
sudo resolvconf -u 3 For those of you managing your servers remotely you can:
- update the
dns-nameserversline in/etc/network/interfaces # ifdown eth01; ifup eth01
Notice that this has to be on one line divided with ; (the linux command line separator).
You should not even lose your current connection. The exception is making a typo in the interfaces file. If this happens ifup will fail and you will have to have physical access or another ethxx connection.
service resolvconf restart will regenerate /etc/resolv.conf file without much fuss.
Simple answer :
Just install resolvconf. apt install resolvconf
After that, ifup eth0 updates the dns in etc/resolv.conf, according to the dns-nameservers line in /etc/network/interfaces.
This answer is similar to the one above but uses the questions example configuration to answer the question. Plus this explains why both commands are necessary.
Edit /etc/network/interfaces:
iface eth0 inet static address 192.168.3.3 netmask 255.255.255.0 gateway 192.168.3.1 dns-search example.com dns-nameserver 192.168.3.45 dns-nameserver 192.168.8.10These changes will not take place unless you reboot or reload the configuration file:
In order to update the interfaces file live it is necessary to run the following command:
echo "nameserver 192.168.3.45
nameserver 192.168.8.10
search example.com" | sudo resolvconf -a eth0.inetThis allows an update to the interface without a reboot or reloading.
However, the above command changes will be lost after a reboot if the changes in the /etc/network/interfaces are not made.
By the way the last answer from BDenis in this list actually works in place of the last command by parsing the /etc/network/interfaces file and piping those lines into the command sudo resolvconf -a eth0 It's actually half the answer and a really good example of inline sed parsing. If you want to see how it does this just run the first part of the command and watch it parse the /etc/network/interfaces file and spit out all the necessary information you need to run the sudo resolvconf -a eth0 command:
sed 's/#.*$//' /etc/network/interfaces | grep dns- | sed 's/dns-//g'Notice this would produce the same out put as the command:
echo "nameserver 192.168.3.45
nameserver 192.168.8.10
search example.com"Provided that the /etc/network/interfaces file is configured with this information:
iface eth0 inet static address 192.168.3.3 netmask 255.255.255.0 gateway 192.168.3.1 dns-search example.com dns-nameserver 192.168.3.45 dns-nameserver 192.168.8.10 1 On 18.04, the following works reliably (run as root):
systemctl stop networking
ip address flush dev <device> # just to be safe
systemctl start networkingImportant: Make sure you have package resolvconf installed.
It doesn't seem to be by default, and without it some (!) changes from /etc/network/interfaces are silently ignored (e.g. dns-*).
On desktop version of Ubuntu 18.04, where there's no service networking, and resolvconf isn't installed by default, I've succeeded in regenerating resolv.conf by restarting network-manager:
sudo service network-manager restart 1 This worked for me:
sed -re '/nameservers|dns-search/ !d' -e 's/dns-nameservers/nameserver/' -e 's/dns-search/search/' /etc/network/interfaces | resolvconf -a eth0.inet && resolvconf -uAdjust accordingly.
I discovered that if I got rid of the [network] and generateResolvConf = false from /etc/wsl.conf, shutdown, and restarted, then /etc/resolv.conf regenerated without having to do all the reinstall stuff.
My config files were perfect. I restarted all the necessary services. I told resolveconf to update.
None of this dynamically updated my resolve.conf and gave me access to my local domain's name servers until I performed a "sudo reboot".
On boot up, resolv.conf was updated and I could ping and get access to a domain name on my manually added dns-nameserver.
Also you can try this command:
cat /etc/network/interfaces |sed 's/#.*$//'|grep dns-|sed 's/dns-//g'|sudo resolvconf -a eth0.inet 3