How to get the systemd resolver to resolve local (i.e. unqalified) names?
Chris Green
cl at isbd.net
Sun Jun 4 09:44:58 UTC 2017
On Sun, Jun 04, 2017 at 05:40:59AM -0400, Tom H wrote:
> On Sat, Jun 3, 2017 at 4:32 PM, Chris Green <cl at isbd.net> wrote:
> > On Sat, Jun 03, 2017 at 05:11:59PM -0300, Kleber Leal wrote:
> >> Do you have the *search* option defined with your /etc/resolv.conf?
> >> nameserver x.x.x.x
> >> nameserver x.x.x.y
> >> search [1]zbmc.eu
> >
> > /etc/resolv.conf hasn't been an editable configuration file since
> > somewhere around 10.04.
> >
> > /etc/resolv.conf in 17.04 is:-
> >
> > # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
> > # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
> > # 127.0.0.53 is the systemd-resolved stub resolver.
> > # run "systemd-resolve --status" to see details about the actual nameservers.
> >
> > nameserver 127.0.0.53
>
> resolved isn't the only generator. You could generate "resolv.conf"
> with resolvconf with "search" lines (you'd have to change the
> "/etc/resolv.conf" symlink).
>
Yes, I could create my own /etc/reolv.conf but that's a bodge. I
really don't like doing things like that. I want to find either the
right way to configure systemd-resolved to look up unqualified names
or report it as a bug/enhancement.
--
Chris Green
More information about the ubuntu-users
mailing list