This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug network/15726] getaddrinfo() returns incorrect status
- From: "kurt at roeckx dot be" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Fri, 30 Aug 2013 07:11:23 +0000
- Subject: [Bug network/15726] getaddrinfo() returns incorrect status
- Auto-submitted: auto-generated
- References: <bug-15726-131 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=15726
--- Comment #29 from Kurt Roeckx <kurt at roeckx dot be> ---
(In reply to Rich Felker from comment #28)
> > We should just not use that nameserver anymore (for the current lookup), and if
> > we find no nameservers that give us an answer it should result in "no answer" /
> > EAI_FAIL. But I'm not sure how detailed we should go with all those things.
>
> If the nameserver gives response code 5, you could discontinue using
> it for the current request, but it probably shouldn't be dropped in
> general -- for example, the nameserver might be denying recursion but
> serving a local domain only. In any case, EAI_FAIL is the right
> response here if the only nameserver(s) available give(s) response
> code 5, since it's not a temporary condition, there's no way to work
> around it, and it's neither a positive result nor a negative result.
I meant "no answer" / EAI_AGAIN.
But I can also see how EAI_FAIL might be a good value for it. One of the
reasons for EAI_FAIL could be "local configuration error".
--
You are receiving this mail because:
You are on the CC list for the bug.