Bug 180481 (PR_GetAddrInfoByName) - Use PR_GetAddrInfoByName instead of PR_GetIPNodeByName/PR_GetHostByAddr
Summary: Use PR_GetAddrInfoByName instead of PR_GetIPNodeByName/PR_GetHostByAddr
Status: CLOSED DUPLICATE of bug 206724
Alias: PR_GetAddrInfoByName
Product: 389
Classification: Retired
Component: Directory Server
Version: 1.0
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Rich Megginson
QA Contact: Orla Hegarty
Depends On:
TreeView+ depends on / blocked
Reported: 2006-02-08 15:18 UTC by Rich Megginson
Modified: 2007-04-18 17:37 UTC (History)
4 users (show)

Clone Of:
Last Closed: 2006-10-09 22:50:03 UTC

Attachments (Terms of Use)

Description Rich Megginson 2006-02-08 15:18:53 UTC
PR_GetAddrInfoByName is the preferred method to get address information for an
IP address (IPv4 and IPv6) and to enumerate hostname lookups.  We especially
need this for HP-UX to support IPv6, because the older functions are based on
the deprecated getipnodebyname function, which is broken in HP-UX B.11.11 (with
IPv6 patch applied).  Instead of fixing PR_GetIPNodeByName for HP-UX B.11.11, we
should switch to the new PR_GetAddrInfoByName function.

Comment 1 Wan-Teh Chang 2006-02-08 21:09:59 UTC
We should replace all gethostbyname, PR_GetHostByName,
and PR_GetIPNodeByName calls with PR_GetAddrInfoByName
calls.  PR_GetAddrInfoByName supports both IPv4 and
IPv6, so we can test the new code on IPv4 networks now.
(In fact, PR_GetAddrInfoByName is supposed to make the
code more oblivious of the protocol address family.)
This work doesn't need to wait until we have set up an
IPv6 network.

Comment 2 Rich Megginson 2006-10-09 22:35:08 UTC
Was this already done as part of IPv6 enabling the server?  If so, can someone
mark this as a duplicate?

Comment 3 Noriko Hosoi 2006-10-09 22:50:03 UTC
Sorry, the subject of 206724 "Replacing PR_SetNetAddr with PRLDAP_SET_PORT for
IPv6 support" does not mention PR_GetAddrInfoByName, but the fix includes the
replacement, as well.

*** This bug has been marked as a duplicate of 206724 ***

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