nmcli

[Jerry Geis]

On Fri, Feb 19, 2021 at 10:02 AM Tom H <tomh0665 at gmail.com> wrote:

> On Fri, Feb 19, 2021 at 3:50 PM Jerry Geis <jerry.geis at gmail.com>
> wrote:
> >
> > Ok - lets try this route.
> > I created the /etc/systemd/resolved.conf.d directory
> > made a file in there lsi.conf
> > [Resolve]
> > DNS=192.168.1.14
> > I am actually using static address on this box and have an internal
> > DNS of 192.168.1.14
> > I then rebooted and my internal DNS still not being used.
> > /etc/resolv.conf is still as it was - with nameserver 127.0.0.53
> > Do I need to issue a command after creating the file ?
>
> You can either run "systemctl restart systemd-resolved.service" or reboot.
>
> You'll still have "127.0.0.53" in "/etc/resolv.conf".
>
> You can check whether "192.168.1.14" is being used with "resolvectl".
>
> --
> ubuntu-users mailing list
> ubuntu-users at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-users



Tom - Thanks so much!

Adding the resolved.conf.d  and making my file in there makes it work.
Correct /etc/resolv.conf does not reflect this  but that is ok .
I just need the correct DNS look.

Perfect - thanks again.
Jerry
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-users/attachments/20210219/062b108b/attachment.html>