On Wed, 2017-09-20 at 08:48 -0500, Chris wrote:
> On Wed, 2017-09-20 at 11:15 +0100, Martin Gregorie wrote:
> > On Tue, 2017-09-19 at 19:32 -0500, Chris wrote:
> > >
> > > Hi Martin, here's what I see:
> > >
> > > sudo systemctl status dnsmasq
> > > [sudo] password for chris:
> > > ● dnsmasq.service
> > > Loaded: not-found (Reason: No such file or directory)
> > > Active: inactive (dead)
> > > chris@localhost:~$ sudo systemctl enable dnsmasq
> > > Failed to execute operation: No such file or directory
> > > chris@localhost:~$ sudo systemctl status dnsmasq
> > > ● dnsmasq.service
> > > Loaded: not-found (Reason: No such file or directory)
> > > Active: inactive (dead)
> > >
> >
> > Yes, that agrees with systemd not knowing about dnsmasq.
> >
> > >
> > > I then installed dnsmasq (apparently it wasn't installed)
> > >
> >
> > I don't know why you'd want to do that since you should be running
> > named instead of dnsmasq.
> >
>
> I was tired and getting po'd at the whole mess. I installed via apt
> then removed via apt and also ran apt purge.
>
> > 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...
> >
>
> From the locate command I found these - https://pastebin.com/ECjZGX1M
>
> I'm not sure what to do with those that are associated with
> /snap/core.
>
Can't help there as I've not seen a /snap directory structure before. I
don't believe any RedHat distros use it and nor does Raspbian.
How was it installed in the first place? That may give you some clues,
or somebody who is more familiar Debian and its clones may know a safe
way to remove it: I'd be inclined to just remove the lot but then I
tend to go in boots and all in this sort of situation. Just take a
backup first.
OTOH, since there's apparently nothing that starts dnsmasq at boot time
apart from NetworkManager you can always just leave it there and accept
that it will continue to occupy space on disk. Then:
- do as others have said and reconfigure NetworkManager so it doesn't
start anything.
- configure named as a recursive nameserver if that isn't already done
- set up systemd to start named at boot time:
systemctl enable named # This makes it start at boot time
systemctl start named # Start it now
systemctl status named # see if it started OK
- if it didn't like the current /etc/named.conf or it it isn't doing
what you want, modify its configuration and:
systemctl restart named # kills named and restarts it with
the
# new config
systemctl status named # See what its gdoing
and repeat until its right
Martin
