Hot answers tagged resolvconf
This was on Ubuntu server 12.04 LTS and Ubuntu 12.04 LTS Thanks all for the help. Turns out to be a result of a difference in the way host and the glibc resolver read /etc/resolv.conf. I was managing resolv.conf with a puppet module that edited the appropriate files in /etc/resolvconf/resolv.conf.d/. Said puppet module resulted in an /etc/resolv.conf ...
I think it would be beneficial to step back, teach a man how to fish instead of just telling you what's wrong. There are many components involved in making a good network connection It can be the hardware: ethernet card, cable contacts, network interface on your directly connected switch, etc. It can be the low level software: the kernel driver for your ...
The resolvconf records have names that follow the pattern IFACE.CONFIGURER So to force eth1* records to come before other eth* records you need to replace eth* with eth1* eth* After making this change, do sudo resolvconf -u
In Ubuntu 12.04 and later, /etc/resolv.conf is dynamically generated by the resolvconf utility. (Actually, resolvconf generates /run/resolvconf/resolv.conf and /etc/resolv.conf is a symbolic link to that. That's the default configuration; it is also possible to run with a static file at /etc/resolv.conf but that is non-standard.) Nameserver information ...
OK, I found a solution here which is to run sudo dpkg-reconfigure resolvconf In the interaction with dpkg-reconfigure, I answered YES to the first question and NO to the second one. This bug report may be relevant to the problem I had.
One of the problems is that resolvconf did not get configured properly. Ref: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1000244. To fix this, run sudo dpkg-reconfigure resolvconf This, however, can't be the reason that you cannot ping other machines by IP address.
Only top voted, non community-wiki answers of a minimum length are eligible