[Dnsmasq-discuss] Local dnsmasq server not utilized by Ubuntu
stappers at stappers.nl
Sun Aug 4 21:25:55 BST 2019
On Sun, Aug 04, 2019 at 09:53:29PM +0200, john doe wrote:
> On 8/4/2019 9:04 PM, dnsmasqyq.xpt at neverbox.com wrote:
> > Sorry I wasn't very clear first
> > as I don't know if anyone would read/reply.
Thing to think about
When there is no effort put in the question,
why should there be put effort in the answer?
> >> It's not a NetworkManager nor an Ubuntu problem: you have
> >> systemd-resolve installed on your machine (guess Ubuntu 18.04) which
> >> uses 127.0.0.53 as IP for DNS. You have to go in /etc/systemd and adapt
> >> the resolved.conf file to put your dnsmasq IP server as DNS.
> > Yes, exactly I'm using Ubuntu 18.04, thus systemd-resolve. So,
> > How to adapt the resolved.conf file so that my modification survive
> > reboot, and not hard-coding anything as when I take my laptop else
> > where, I don't want it still pointing to my home LAN dnsmasq server?
> Lookat the 'resolvconf' package if it is installed.
> Basically, look at the top of /etc/resolv.conf to see what is handeling it.
Which program updates /etc/resolv.conf is not (yet??) the issue.
The issue is what information gets picked-up by the programm
that updates /etc/resolv.conf
Leven en laten leven
More information about the Dnsmasq-discuss