Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #267994

Re: systemd-resolved resolving fails sometimes on Debian12

From Victor Sudakov <vas@sibptus.ru>
Newsgroups linux.debian.user
Subject Re: systemd-resolved resolving fails sometimes on Debian12
Date 2024-03-03 06:10 +0100
Message-ID <IdMgN-e4oY-1@gated-at.bofh.it> (permalink)
References <Id8jn-dFmJ-1@gated-at.bofh.it> <Idhwl-dLtL-3@gated-at.bofh.it> <Idztf-dWzA-3@gated-at.bofh.it> <IdHTP-e1Ed-1@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

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

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

systemd-resolved resolving fails sometimes on Debian12 Victor Sudakov <vas@sibptus.ru> - 2024-03-01 11:30 +0100
  Re: systemd-resolved resolving fails sometimes on Debian12 jeremy ardley <jeremy.ardley@gmail.com> - 2024-03-01 21:20 +0100
    Re: systemd-resolved resolving fails sometimes on Debian12 Victor Sudakov <vas@sibptus.ru> - 2024-03-02 16:30 +0100
      Re: systemd-resolved resolving fails sometimes on Debian12 jeremy ardley <jeremy.ardley@gmail.com> - 2024-03-03 01:30 +0100
        Re: systemd-resolved resolving fails sometimes on Debian12 Victor Sudakov <vas@sibptus.ru> - 2024-03-03 06:10 +0100
          Re: systemd-resolved resolving fails sometimes on Debian12 jeremy ardley <jeremy.ardley@gmail.com> - 2024-03-03 10:30 +0100
            Re: systemd-resolved resolving fails sometimes on Debian12 Victor Sudakov <vas@sibptus.ru> - 2024-03-03 16:00 +0100
              Re: systemd-resolved resolving fails sometimes on Debian12 jeremy ardley <jeremy.ardley@gmail.com> - 2024-03-04 07:30 +0100
                Re: systemd-resolved resolving fails sometimes on Debian12 Noah Meyerhans <noahm@debian.org> - 2024-05-21 21:40 +0200
      Re: systemd-resolved resolving fails sometimes on Debian12 Marco Moock <mm@dorfdsl.de> - 2024-03-04 08:40 +0100

csiph-web