On Wed, 2017-09-20 at 19:05 +0100, Martin Gregorie wrote: > 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/ECjZGX > > 1M > > > > 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. It was installed by default when upgrading from 14.04LTS to 16.04LTS
>
> 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.
>
I have stopped Network Manager. I've not disabled or removed it yet as
I'm watching to see how named does the queries now.
> - 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
>
It already starts at boot.
> - 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
>
systemctl status bind9
● bind9.service - BIND Domain Name Server
Loaded: loaded (/etc/systemd/system/bind9.service; enabled; vendor
preset: enabled)
Drop-In: /run/systemd/generator/bind9.service.d
└─50-insserv.conf-$named.conf
Active: active (running) since Wed 2017-09-20 17:57:18 CDT; 3min 6s
ago
Docs: man:named(8)
Process: 19195 ExecStop=/usr/sbin/rndc stop (code=exited,
status=0/SUCCESS)
Main PID: 19203 (named)
CGroup: /system.slice/bind9.service
└─19203 /usr/sbin/named -4 -f -u bind
localhost named[19203]: automatic empty zone: EMPTY.AS112.ARPA
localhost named[19203]: configuring command channel from
'/etc/bind/rndc.key'
localhost named[19203]: command channel listening on 127.0.0.1#953
localhost named[19203]: managed-keys-zone: loaded serial 602
localhost named[19203]: zone localhost/IN: loaded serial 2
localhost named[19203]: zone 255.in-addr.arpa/IN: loaded serial 1
localhost named[19203]: zone 127.in-addr.arpa/IN: loaded serial 1
localhost named[19203]: zone 0.in-addr.arpa/IN: loaded serial 1
localhost named[19203]: all zones loaded
localhost named[19203]: running
/etc/named.conf is simply
# OPTIONS="-4 -u bind"
include "/etc/bind/named.conf.options";
include "/etc/bind/named.conf.local";
include "/etc/bind/named.conf.default-zones";
# allow-query-cache localnets;
My /etc/bind/named.conf.options reads
acl goodclients {
127.0.0.1;
localhost;
localnets;
};
options {
directory "/var/cache/bind";
geoip-directory "/usr/share/GeoIP";
recursion yes;
allow-query { goodclients; };
// If there is a firewall between you and nameservers you want
// to talk to, you may need to fix the firewall to allow
multiple
// ports to talk. See http://www.kb.cert.org/vuls/id/800113
// If your ISP provided one or more IP addresses for stable
// nameservers, you probably want to use them as forwarders.
// Uncomment the following block, and insert the addresses
replacing
// the all-0's placeholder.
//forwarders {
//127.0.0.1;
//};
//dnssec-validation auto;
auth-nxdomain no; # conform to RFC1035
//listen-on-v6 { any; };
listen-on { 127.0.0.1; };
};
--
Chris
KeyID 0xE372A7DA98E6705C
31.11972; -97.90167 (Elev. 1092 ft)
17:43:38 up 20:56, 1 user, load average: 0.05, 0.21, 0.52
Description: Ubuntu 16.04.3 LTS, kernel 4.10.0-35-generic
signature.asc
Description: This is a digitally signed message part
