I am solving this by using libvir's network, which uses dnsmasq for
network resolution. That dnsmasq should be able to resolve names of
containers, because they were registered by DHCP requests. Because they
share dns cache at host, there is single place where they can register to.
Not directly
> On Jun 18, 2021, at 16:02, Silvio Knizek wrote:
>
> Am Freitag, dem 18.06.2021 um 14:52 -0700 schrieb Johannes Ernst:
>>
>> Thanks, Silvio, but no luck:
>>
>> I have host, container a and container b.
>>
>> In both containers, .network for host0 has LLMNR=yes in the [Network]
>> section
>>
Am Freitag, dem 18.06.2021 um 14:52 -0700 schrieb Johannes Ernst:
>
> Thanks, Silvio, but no luck:
>
> I have host, container a and container b.
>
> In both containers, .network for host0 has LLMNR=yes in the [Network]
> section
>
> The host has LLMNR=yes in the [Resolve] section of
>
> On Jun 18, 2021, at 2:02, Silvio Knizek wrote:
>
> Am Donnerstag, dem 17.06.2021 um 20:26 -0700 schrieb Johannes Ernst:
>> I’d like to be able to DNS lookup container b from within container a, if
>> both were started with systemd-nspawn as siblings of each other, and shown
>> as a and b in
Am Donnerstag, dem 17.06.2021 um 20:26 -0700 schrieb Johannes Ernst:
> I’d like to be able to DNS lookup container b from within container a, if
> both were started with systemd-nspawn as siblings of each other, and shown as
> a and b in machinectl list.
>
> man nss-mymachines specifically notes
