On 2/3/24 23:06, Victor Sudakov wrote:
You know, the official Debian 12 AMI for AWS is built on
systemd-resolved and systemd-networkd. I'd prefer not to have to
modify the official AMI if I can help it, because this would probably
mean also replacing the systemd-networkd with some other network
manager.
systemd-networkd does not rely on systemd-resolved for name resolution.
There is a relationship where systemd-networkd can feed dns information
to system-resolved that could be helpful in dynamic IP configurations
like laptops. However this is not usual case in AWS deployments.
The Debian AWS AMI does not use the usual NetworkManager configuration
because the usual AWS deployment does not required dynamic DNS.
In my AWS deployments I remove systemd-resolved and use bind9 instead.
