jeremy ardley wrote: > > 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. How is it not usual when the Debian12 AMI for AWS works exactly this way? The system-resolved config is empty (contains only comments) this means that it obtains the upstream DNS address from systemd-networkd. > > The Debian AWS AMI does not use the usual NetworkManager configuration > because the usual AWS deployment does not required dynamic DNS. How does it not require dynamic DNS when an EC2 instance obtains the upstream DNS server address from DHCP? > > In my AWS deployments I remove systemd-resolved and use bind9 instead. > Not that I would use bind9 as a caching resolver but still, how do you pass the dynamically obtained AWS DNS server address from systemd-networkd to bind9 ? -- Victor Sudakov VAS4-RIPE http://vas.tomsk.ru/ 2:5005/49@fidonet
Attachment:
signature.asc
Description: PGP signature