getipnodebyname.3 (5c564bae0a7655b1a517f322ad410a743e98e8d2) getipnodebyname.3 (33dee819339974eaf7dbf69068001771cbdcd548)
1.\" $KAME: getipnodebyname.3,v 1.6 2000/08/09 21:16:17 itojun Exp $
2.\"
3.\" Copyright (c) 1983, 1987, 1991, 1993
4.\" The Regents of the University of California. All rights reserved.
5.\"
6.\" Redistribution and use in source and binary forms, with or without
7.\" modification, are permitted provided that the following conditions
8.\" are met:

--- 441 unchanged lines hidden (view full) ---

450and
451.Fn getipnodebyaddr
452functions
453are documented in
454.Dq Basic Socket Interface Extensions for IPv6
455(RFC2553).
456.\"
457.Sh BUGS
1.\" $KAME: getipnodebyname.3,v 1.6 2000/08/09 21:16:17 itojun Exp $
2.\"
3.\" Copyright (c) 1983, 1987, 1991, 1993
4.\" The Regents of the University of California. All rights reserved.
5.\"
6.\" Redistribution and use in source and binary forms, with or without
7.\" modification, are permitted provided that the following conditions
8.\" are met:

--- 441 unchanged lines hidden (view full) ---

450and
451.Fn getipnodebyaddr
452functions
453are documented in
454.Dq Basic Socket Interface Extensions for IPv6
455(RFC2553).
456.\"
457.Sh BUGS
458Although the current implementation is otherwise thread-safe, using
459it in conjunction with
460.Fn gethostby*
461(see
462.Xr gethostbyname 3 )
463or
464.Xr yp 8
465breaks the thread-safety of both.
466.Pp
458The
459.Fn getipnodebyname
460and
461.Fn getipnodebyaddr
462functions
463do not handle scoped IPv6 address properly.
464If you use these functions,
465your program will not be able to handle scoped IPv6 addresses.
466For IPv6 address manipulation,
467.Fn getaddrinfo 3
468and
469.Fn getnameinfo 3
470are recommended.
471.Pp
467The
468.Fn getipnodebyname
469and
470.Fn getipnodebyaddr
471functions
472do not handle scoped IPv6 address properly.
473If you use these functions,
474your program will not be able to handle scoped IPv6 addresses.
475For IPv6 address manipulation,
476.Fn getaddrinfo 3
477and
478.Fn getnameinfo 3
479are recommended.
480.Pp
472The current implementation is not thread-safe.
473.Pp
474The text was shamelessly copied from RFC2553.
481The text was shamelessly copied from RFC2553.