Re: Issue with stale resolv.conf state

[Philip Sanetra <code@psanetra.de>]

[-- Attachment #1.1: Type: text/plain, Size: 1671 bytes --]

Hi,

I think removing the automatic downgrade without also making the single-request option the defeault behavior would break a lot of systems.

I know of at least two environments in different companies where the default behavior results in 5 seconds timeouts and only the automatic downgrade improves performance in subsequent DNS lookups.

I would appreciate using single-request option as default, like mentioned in https://sourceware.org/bugzilla/show_bug.cgi?id=29017

Regards,
Philip Sanetra


On Tuesday, 12 March 2024 at 7:45 AM, Florian Weimer <fweimer@redhat.com> wrote:

> 

> 

> * Cristian Rodríguez:
> 

> > On Mon, Mar 11, 2024 at 7:51 AM Florian Weimer fweimer@redhat.com wrote:
> > 

> > > * John Levon:
> > 

> > cessing).
> > 

> > > Maybe we should just remove the automatic downgrade, basically not
> > > persist this across queries anymore.
> > 

> > Yeah. +1. Users of those broken nameservers deserve at least noticing
> > they are wrong if such systems are really still around ..
> 

> 

> I filed:
> 

> Automatic activation of single-request options break resolv.conf reloading
> https://sourceware.org/bugzilla/show_bug.cgi?id=31476
> 

> 

> On the other hand, we have this request:
> 

> | Change resolv.conf default to single-request
> | […]
> | We have the year 2022 and these issues still occur, so it was not some
> | kind of issue that went away by time as it was possibly expected when
> | glibc 2.10 was released.
> 

> https://sourceware.org/bugzilla/show_bug.cgi?id=29017
> 

> 

> So the solution might not be so straightforward.
> 

> Thanks,
> Florian


[-- Attachment #1.2: publickey - code@psanetra.de - 0x61B5EBD7.asc --]
[-- Type: application/pgp-keys, Size: 645 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 249 bytes --]