Problem with resolve.conf and systemd-resolved

[Przemysław Sztoch]

Hello,

The separate systemd-resolved package has the disadvantage that it 
automatically replaces the rsolve.conf file and causes that when the 
system is not booted with systemd (e.g. all kinds of installations and 
bootstrappings using chroot) network connectivity does not work (no 
dns), e.g. for apt install, curl, etc.

Is it possible to add configuration entries to the systemd-resolved 
package that will allow the resolve.conf file not to be touched?

Another suggestion is to update the resolve.conf file after the 
systemd-resolved service is run for the first time.

Currently, after apt install libnss-resolve, our chroot environment 
stops working, which is very frustrating. And you have to install this 
package at the end and you can't at the beginning.

-- 
Przemysław Sztoch | Mobile +48 509 99 00 66
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20230801/db690614/attachment.htm>