public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bugs at jth dot net" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/26977] New: getaddrinfo does not handle the hosts file correctly Date: Sun, 29 Nov 2020 21:28:06 +0000 [thread overview] Message-ID: <bug-26977-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=26977 Bug ID: 26977 Summary: getaddrinfo does not handle the hosts file correctly Product: glibc Version: 2.32 Status: UNCONFIRMED Keywords: glibc_2.32 Severity: normal Priority: P2 Component: libc Assignee: unassigned at sourceware dot org Reporter: bugs at jth dot net CC: drepper.fsp at gmail dot com Target Milestone: 2.32 Host: Linux Fedora 33 On a dual stack IP4 + IP6 server the 2.32 release has introduced a problem of getaddrinfo omitting looking up the IP6 address in the DNS in case the IP4 address is found in the hosts file or vice versa. After upgrading 'ping -6 IP6.HOST' suddenly failed by "Address family for hostname not supported" and the monitoring software reported downtime. Similarly for the dig command. A test program for getaddrinfo verified the changed behaviour. Only after entering the IP6 address into or deleting the IP4 address from the hosts file the old behaviour was restored. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2020-11-29 21:28 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-29 21:28 bugs at jth dot net [this message] 2020-11-29 21:29 ` [Bug libc/26977] " bugs at jth dot net 2020-11-29 21:51 ` bugs at jth dot net 2020-11-30 11:47 ` fweimer at redhat dot com 2020-11-30 13:13 ` bugs at jth dot net 2020-11-30 13:34 ` bugs at jth dot net 2020-11-30 13:36 ` fweimer at redhat dot com 2020-11-30 13:37 ` [Bug network/26977] " fweimer at redhat dot com 2020-11-30 14:02 ` bugs at jth dot net
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=bug-26977-131@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@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: linkBe 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).