Bug 206329 - libresolv query ids reused after fork()
libresolv query ids reused after fork()
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: glibc (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jakub Jelinek
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2006-09-13 14:06 EDT by Mark Plaksin
Modified: 2016-11-24 09:52 EST (History)
2 users (show)

See Also:
Fixed In Version: RHBA-2007-0210
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-05-01 19:06:50 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Mark Plaksin 2006-09-13 14:06:12 EDT
Description of problem:
The problem described here occurs in RHEL 4.4 too:

For us the problem manifests itself when sshing to our RHEL 4.4 boxes.  SSH
causes several DNS requests to be made.  Two of the requests use the same DNS
transaction ID.  Our firewall doesn't like this so it drops the second packet. 
After a 5-second timeout the request is retried, uses a different transaction
ID, and succeeds.

The user sees a 5-second delay when logging in via ssh.

Version-Release number of selected component (if applicable):

How reproducible:
See bug referenced above.
Comment 2 RHEL Product and Program Management 2006-09-14 18:46:11 EDT
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
Comment 7 Red Hat Bugzilla 2007-05-01 19:06:50 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.