From: David Howells <dhowells@redhat.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: dhowells@redhat.com, jlayton@redhat.com, libc-alpha@sourceware.org
Subject: Re: Can getaddrinfo() be extended to return the record TTL
Date: Tue, 14 Apr 2020 14:42:53 +0100 [thread overview]
Message-ID: <3810641.1586871773@warthog.procyon.org.uk> (raw)
In-Reply-To: <87a7clgkyj.fsf@oldenburg2.str.redhat.com>
Florian Weimer <fweimer@redhat.com> wrote:
> > Florian Weimer <fweimer@redhat.com> wrote:
> >
> >> > The userspace side of the upcall *should* be setting the expiry time
> >> > on the record - but it can't as the C library doesn't give us that
> >> > (and, indeed, it's not available from all sources).
> >>
> >> Is this merely a correctness thing, or does this enable some
> >> user-visible functionality?
> >
> > The kernel's DNS cache's ordinary records currently don't have their expiry
> > set as I don't have anything to set it to - with the result that the entries
> > in the cache never expire and have to be manually invalidated if you want them
> > to be reread.
> >
> > I can, and probably should, set the default timeout to something reasonably
> > small and finite (say 10 mins) in the absence of such data, but it would be
> > better, I think, to set the TTL from the record (if available).
> >
> > So, yes, this is actually causing a problem.
>
> I actually meant whether it enables some user-visible functionality,
> like failover or service migration.
>
> It's tricky to make this work in practice using DNS even if you know the
> TTL, which is why I'm asking. 8-)
Ah, sorry, I never got around to replying. The problem is that the address
mapping records in the kernel used by a variety of network filesystems (NFS,
AFS, CIFS, etc.) don't expire because I don't expire because I don't have any
expiration information to apply.
David
prev parent reply other threads:[~2020-04-14 13:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-02 16:42 David Howells
2019-08-02 17:21 ` Florian Weimer
2019-08-06 15:16 ` Eric Wong
2019-08-07 13:35 ` Florian Weimer
2019-08-02 19:33 ` David Howells
2019-08-02 21:47 ` Carlos O'Donell
2020-04-14 14:15 ` Jeff Layton
2019-08-07 13:32 ` Florian Weimer
2020-04-14 13:42 ` David Howells [this message]
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=3810641.1586871773@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=fweimer@redhat.com \
--cc=jlayton@redhat.com \
--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).