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


Groups > linux.debian.user > #268005

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 16:00 +0100
Message-ID <IdVtM-e9PG-25@gated-at.bofh.it> (permalink)
References (1 earlier) <Idhwl-dLtL-3@gated-at.bofh.it> <Idztf-dWzA-3@gated-at.bofh.it> <IdHTP-e1Ed-1@gated-at.bofh.it> <IdMgN-e4oY-1@gated-at.bofh.it> <IdQkp-e6Qx-5@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 3/3/24 12:43, Victor Sudakov wrote:
> > 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 ?
> 
> 
> The AWS DNS resolver IPs are static and are widely published.

Do you mean 169.254.169.253?
> 
> It is permissible to not use AWS resolvers for upstream.
> 
> If you want to use AWS resolvers you may run into the problem that some RBL
> services reject queries from 'well known' free DNS servers; that may include
> AWS resolver addresses.
> 
> systemd-networkd without systemd-resolved maintains a list of DNS servers in
> /etc/resolv.conf that can be used by local services.

Do you just disable the systemd-resolved service or do you remove the
systemd-resolved package completely?

If you disable it, you are also supposed to remove the "resolve"
service from nsswitch.conf, right?

> You can override dynamic setting of the dns resolvers in the
> systemd-networkd configuration to use a local caching resolver such as
> bind9, usually listening at 127.0.0.1:53

What would this be for? Sorry, I did not understand this step.
> 
> You can then configure bind 9 as a caching only DNS resolver and set
> appropriate upstream (forwarder) sites, or none at all defaulting to the
> root servers.
> 

Thank you for the ideas, I may use them but first I would like to do
something about the obvious bug in systemd-resolved.

-- 
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