public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: "Cristian Rodríguez" <cristian@rodriguez.im>
Cc: John Levon <levon@movementarian.org>,  libc-alpha@sourceware.org
Subject: Re: Issue with stale resolv.conf state
Date: Tue, 12 Mar 2024 07:45:23 +0100	[thread overview]
Message-ID: <87ttlcvth8.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <CAPBLoAfKkD=CaFDn69QQpCX3iD-_0g-TEGrsd0ic5wnSegbCQQ@mail.gmail.com> ("Cristian =?utf-8?Q?Rodr=C3=ADguez=22's?= message of "Mon, 11 Mar 2024 21:51:44 -0300")

* 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


  reply	other threads:[~2024-03-12  6:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-11  9:08 John Levon
2024-03-11 10:51 ` Florian Weimer
2024-03-12  0:51   ` Cristian Rodríguez
2024-03-12  6:45     ` Florian Weimer [this message]
2024-03-12  9:09       ` Philip Sanetra
2024-03-12 10:04       ` John Levon
2024-03-12 14:25       ` Cristian Rodríguez
2024-03-12 14:30         ` Florian Weimer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ttlcvth8.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=cristian@rodriguez.im \
    --cc=levon@movementarian.org \
    --cc=libc-alpha@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).