Re: [PLUG] Defaulting the domain for a name lookup

["K.S. Bhaskar via plug" <plug@lists.phillylinux.org>]

I couldn't figure it out either. The only hint I could find was an obscure note that .local should be reserved for Avahi, and if you use .local for anything else, things might not work. Anyway, for now, I have something that works, and I will let sleeping dogs lie.

Linux system administration these days feels a little bit like working on a car. In my first car (a 67 Buick Special V6), I could open the hood, and identify pretty much every component in sight. I could fix anything for which I had the tools and muscle. In today's gas cars, if I open the hood, I haven't the foggiest notion of what's what.

Regards

– Bhaskar

On Tue, Dec 8, 2020 at 2:18 PM Rich Freeman <r-plug@thefreemanclan.net> wrote:

On Tue, Dec 8, 2020 at 2:10 PM K.S. Bhaskar via plug
<plug@lists.phillylinux.org> wrote:
>
> Rich –
>
> This is what /etc/resolv.conf says:
>
> # cat /etc/resolv.conf
> # Generated by NetworkManager
> search mybands.local
> nameserver 127.0.0.53
> #
>
> But this is after my last post, when I reported on the hack of statically assigning the IPv6 address that the system booted up with.
>

Interesting, I'd think that this should cause applications to search
mybands.local automatically.  I thought that was more a glibc thing
than a DNS thing.  But I haven't looked into that.

I also have near-zero experience with NetworkManager, so I'm not sure
if it is doing anything.  I'm not sure if it can run its own DNS
resolver separate from systemd-resolved.

--
Rich

___________________________________________________________________________
Philadelphia Linux Users Group         --        http://www.phillylinux.org
Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
General Discussion  --   http://lists.phillylinux.org/mailman/listinfo/plug