You are not logged in.
If dhclient is invoked after the desktop has been started then /etc/resov.conf may be overwritten, to prevent this add a file at /etc/dhcp/dhclient-enter-hooks.d/nodnsupdate with the following content:
#!/bin/sh
make_resolv_conf() {
true
}
Then make it executable:
sudo chmod +x /etc/dhcp/dhclient-enter-hooks.d/nodnsupdate
Offline
^Tried it but did not work.
For
sudo lsof -nPi | grep \:53
I get
systemd 1 root 50u IPv4 15348 0t0 TCP 127.0.2.1:53 (LISTEN)
systemd 1 root 51u IPv4 15349 0t0 UDP 127.0.2.1:53
dnscrypt- 6276 _dnscrypt-proxy 3u IPv4 15348 0t0 TCP 127.0.2.1:53 (LISTEN)
dnscrypt- 6276 _dnscrypt-proxy 4u IPv4 15349 0t0 UDP 127.0.2.1:53
unbound 6585 unbound 3u IPv6 28099 0t0 UDP [::1]:53
unbound 6585 unbound 4u IPv6 28100 0t0 TCP [::1]:53 (LISTEN)
unbound 6585 unbound 5u IPv4 28101 0t0 UDP 127.0.0.1:53
unbound 6585 unbound 6u IPv4 28102 0t0 TCP 127.0.0.1:53 (LISTEN)
Somehow dnssec is still getting back to the isp's dns while testing a connection, inspite of forward-zone in the config file. Also noticed that root.key has TWO dnskeys (one is at least the key which I get via get-trust-anchor script from github).
Offline
^Tried it but did not work.
Sorry but that was a general comment (related to a problem I uncovered in my live ISO image) rather than a suggestion for you.
I will have to get back to you about this, Helium development is ramping up so this will have to take a back seat for a bit, sorry.
Offline