public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gauryogesh.nsit at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug network/14308] getaddrinfo DNS referral response returns host not found when A and AAAA questions are sent and one response is a referral
Date: Sat, 09 Feb 2013 08:50:00 -0000	[thread overview]
Message-ID: <bug-14308-131-JBUaCeIW9a@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14308-131@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=14308

Yogesh Gaur <gauryogesh.nsit at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |gauryogesh.nsit at gmail
                   |                            |dot com

--- Comment #1 from Yogesh Gaur <gauryogesh.nsit at gmail dot com> 2013-02-09 08:50:17 UTC ---
Hello All,

This issue is coming because of both message type of T_A and T_AAAA are being
send in parallel for processing through api _nss_dns_gethostbyname4_r().

Actually following conditions happens before coming this issue:
1> Receive request of type T_A, creating session table entry.
                        T_A -- Host address
This is non-referral response and would create its own session table entry.
2> Receive request of type T_AAAA on port x, reusing session table entry from
#1
                        T_AAAA -- Ip6 Address
This is referral response and would reuse previous created session table entry.
3> Respond to T_AAAA request on port x and remove session table entry.
4> Load-balancer receives response from DNS server for T_A request, but since
session table entry is gone, it simply forwards the traffic. 
Client receives a reply from a different IP not from the IP it expects and
simply ignores it.
5> This then lead to message failure and returns with error-code as EAI_NODATA
i.e. No address associated with hostname.

This issue is only coming with some bad DNS server as they are not able to
process the request correctly. There is no proper fix for this is yet been
released by glibc and this bug is being reported from glibc-2.9.

I found this link which contains patch information using which work-around for
this issue can be applied.

http://sourceware.org/bugzilla/show_bug.cgi?id=7060

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


  parent reply	other threads:[~2013-02-09  8:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-29  5:28 [Bug network/14308] New: " law at redhat dot com
2012-08-13  1:04 ` [Bug network/14308] " phattanon at nettree dot co.th
2013-02-09  8:50 ` gauryogesh.nsit at gmail dot com [this message]
2013-05-29  2:03 ` atsushi at onoe dot org
2013-05-29  2:04 ` atsushi at onoe dot org
2014-04-15 16:08 ` siddhesh at redhat dot com
2014-04-30  6:23 ` cvs-commit at gcc dot gnu.org
2014-04-30  6:37 ` siddhesh at redhat dot com
2014-04-30  6:38 ` siddhesh at redhat dot com
2014-06-18  4:28 ` fweimer at redhat dot com

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-14308-131-JBUaCeIW9a@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: 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).