Hi Lennart,
On Fri, Nov 19, 2021 at 2:23 PM Lennart Poettering
wrote:
> Two ideas I recently thought about:
>
> 1. Maybe resolved's "stub" logic should support listening on yet
>another local IP address: 127.0.0.54 or so, where the same stub
>listens as on 127.0.0.53, but where we uncondi
On Fr, 22.10.21 19:54, Tobias Hunger (tobias.hun...@gmail.com) wrote:
> Hello Systemd Mailing List!
>
> I have a laptop and run a couple of systemd-nspawn containers on that
> machine. This works great, except that name resolution insode the
> containers fails whenever the network on the outside c
> I have been wondering: Would it be possible to forward the containers
> resolver to the host machine resolver somehow?
On my laptop's host system, I set NetworkManager to use dnsmasq as the DNS
server. I added a config file snippet to that dnsmasq so it also listens on
my bridge interface (which
Hello Systemd Mailing List!
I have a laptop and run a couple of systemd-nspawn containers on that
machine. This works great, except that name resolution insode the
containers fails whenever the network on the outside changes.
This is not too surprising: At setup time the resolver information is
c
