On Wed, 2017-09-20 at 08:01 -0700, Ian Zimmerman wrote: > On 2017-09-20 11:15, Martin Gregorie wrote: > > > > > I don't know why you'd want to do that since you should be running > > named instead of dnsmasq. > > > > Delete the version you just installed via the apt package manager > > and > > do a search and destroy mission to get rid of both the other copy > > of > > it and the associated configuration. > > > > Running "updatedb; locate dnsmasq" is probably the fastest way of > > finding it and its associated files. Anything with a similar name > > in > > /etc/init.d is probably its launcher script, so that can go too. If > > you have an /etc/rc.local file, check its contents because its run > > as > > part of the sysVinit process. It shouldn't have anything about > > dnsmasq > > in it but you never know... > Another thing to check in this kind of mess (and I think it wasn't > mentioned yet) is the state of /etc/resolv.conf. In Debian (and so > in > Ubuntu, too) packages that provide DNS daemons, whether authoritative > or > caching only, attempt to manage that file automatically, if the > resolvconf (traditionally) or openresolv package is also > installed. If > you do something "unexpected" you can end up with /etc/resolv.conf in > a > strange state. > Hi Ian, my /etc/resolv.conf is linked to /run/resolvconf/resolv.conf. Both appear to be the same. I don't know why the nameserver line is there twice.
/run/resolvconf/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 127.0.0.1 nameserver 127.0.0.1 search PK5001Z The /etc/resolv.conf is exactly the same. > To avoid that, on my Debian hosts I usually purge > resolvconf/openresolv, > make sure that /etc/resolv.conf is a real file (not a symlink), and > manually edit it to the correct state. If the host is on DHCP I also > make sure the ISC DHCP client is in use (not dhcpcd which seems to be > much less flexible), and change /etc/dhcp/dhclient.conf to not > request > (or override) the DNS info provided by DHCP, as that also messes with > resolv.conf. > So, IIUC it would be a good idea to remove the resolv.conf symlink in /run/resolvconf ? > Finally (and getting really OT), it helps to keep relevant /etc files > under version control, so you know when the system helpfully shifts > the > ground under you. > -- Chris KeyID 0xE372A7DA98E6705C 31.11972; -97.90167 (Elev. 1092 ft) 16:42:52 up 19:55, 1 user, load average: 0.65, 0.59, 0.83 Description: Ubuntu 16.04.3 LTS, kernel 4.10.0-35-generic
signature.asc
Description: This is a digitally signed message part
