On Mon, Mar 04, 2024 at 02:03:32PM +0800, jeremy ardley wrote:
> I completely removed system-resolved as when it is installed it changes the
> DNS configuration to be non-standard
The issues described in this thread are related to libnss-resolve, which
is no longer installed in the Debian 12
Am 02.03.2024 um 15:06:01 Uhr schrieb Victor Sudakov:
> In my case the problem seems related to IPv6. That is, when I disable
> IPv6 via "sysctl net.ipv6.conf.all.disable_ipv6=1" the problem
> disappears.
Please run
resolvectl
that shows the resolvers available.
Check each of them with
dig
On 3/3/24 22:39, Victor Sudakov wrote:
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
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
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
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
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
jeremy ardley wrote:
>
> On 1/3/24 17:47, Victor Sudakov wrote:
> > Has anybody encountered this problem using systemd-resolved as a
> > resolver on Debian12? A DNS request via systemd-resolved fails, but
> > fails only occasionally. A failure can happen once per a hundred
> > successful requests
On 1/3/24 17:47, Victor Sudakov wrote:
Has anybody encountered this problem using systemd-resolved as a
resolver on Debian12? A DNS request via systemd-resolved fails, but
fails only occasionally. A failure can happen once per a hundred
successful requests or so. If I run:
I recall a
Dear Colleagues,
Has anybody encountered this problem using systemd-resolved as a
resolver on Debian12? A DNS request via systemd-resolved fails, but
fails only occasionally. A failure can happen once per a hundred
successful requests or so. If I run:
while resolvectl query myredis.my.domain ;
10 matches
Mail list logo
