Issue with stale resolv.conf state

Florian Weimer fweimer@redhat.com
Tue Mar 12 06:45:23 GMT 2024


* 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



More information about the Libc-alpha mailing list