Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #267996
| From | jeremy ardley <jeremy.ardley@gmail.com> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: systemd-resolved resolving fails sometimes on Debian12 |
| Date | 2024-03-03 10:30 +0100 |
| Message-ID | <IdQkp-e6Qx-5@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> <IdMgN-e4oY-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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. 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. 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 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.
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll 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