2017-11-20 19:45:28 +00:00
|
|
|
/*-
|
2017-12-08 15:57:29 +00:00
|
|
|
* SPDX-License-Identifier: (ISC AND BSD-3-Clause)
|
2017-11-20 19:45:28 +00:00
|
|
|
*
|
2014-08-05 23:16:31 +00:00
|
|
|
* Portions Copyright (C) 2004, 2005, 2008, 2009 Internet Systems Consortium, Inc. ("ISC")
|
|
|
|
* Portions Copyright (C) 1995-2003 Internet Software Consortium.
|
|
|
|
*
|
|
|
|
* Permission to use, copy, modify, and/or distribute this software for any
|
|
|
|
* purpose with or without fee is hereby granted, provided that the above
|
|
|
|
* copyright notice and this permission notice appear in all copies.
|
|
|
|
*
|
|
|
|
* THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH
|
|
|
|
* REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
|
|
|
|
* AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
|
|
|
|
* INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
|
|
|
|
* LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
|
|
|
|
* OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
|
|
|
|
* PERFORMANCE OF THIS SOFTWARE.
|
|
|
|
*/
|
|
|
|
|
Update the resolver in libc to BIND9's one.
Since, res_sendsigned(3) and the friends use MD5 functions, it is
hard to include them without having MD5 functions in libc. So,
res_sendsigned(3) is not merged into libc.
Since, res_update(3) in BIND9 is not binary compatible with our
res_update(3), res_update(3) is leaved as is, except some
necessary modifications.
The res_update(3) and the friends are not essential part of the
resolver. They are not defined in resolv.h but defined in
res_update.h separately in BIND9. Further, they are not called from
our tree. So, I hide them from our resolv.h, but leave them only
for binary backward compatibility (perhaps, no one calls them).
Since, struct __res_state_ext is not exposed in BIND9, I hide it
from our resolv.h. And, global variable _res_ext is removed. It
breaks binary backward compatibility. But, since it is not used from
outside of our libc, I think it is safe.
Reviewed by: arch@ (no objection)
2006-03-21 16:11:11 +00:00
|
|
|
/*
|
|
|
|
* Copyright (c) 1983, 1987, 1989
|
|
|
|
* The Regents of the University of California. All rights reserved.
|
2014-08-05 23:16:31 +00:00
|
|
|
*
|
1994-05-24 09:57:34 +00:00
|
|
|
* Redistribution and use in source and binary forms, with or without
|
|
|
|
* modification, are permitted provided that the following conditions
|
|
|
|
* are met:
|
|
|
|
* 1. Redistributions of source code must retain the above copyright
|
|
|
|
* notice, this list of conditions and the following disclaimer.
|
|
|
|
* 2. Redistributions in binary form must reproduce the above copyright
|
|
|
|
* notice, this list of conditions and the following disclaimer in the
|
|
|
|
* documentation and/or other materials provided with the distribution.
|
2010-02-16 19:39:50 +00:00
|
|
|
* 3. Neither the name of the University nor the names of its contributors
|
1994-05-24 09:57:34 +00:00
|
|
|
* may be used to endorse or promote products derived from this software
|
|
|
|
* without specific prior written permission.
|
2014-08-05 23:16:31 +00:00
|
|
|
*
|
1994-05-24 09:57:34 +00:00
|
|
|
* THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
|
|
|
|
* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
|
|
|
|
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
|
|
|
|
* ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
|
|
|
|
* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
|
|
|
|
* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
|
|
|
|
* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
|
|
|
|
* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
|
|
|
|
* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
|
|
|
|
* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
|
|
|
* SUCH DAMAGE.
|
1998-06-11 08:55:17 +00:00
|
|
|
*/
|
|
|
|
|
2007-06-03 17:20:27 +00:00
|
|
|
/*%
|
2014-08-05 23:16:31 +00:00
|
|
|
* $Id: resolv.h,v 1.30 2009/03/03 01:52:48 each Exp $
|
1994-05-24 09:57:34 +00:00
|
|
|
*/
|
|
|
|
|
|
|
|
#ifndef _RESOLV_H_
|
|
|
|
#define _RESOLV_H_
|
|
|
|
|
1994-09-25 02:12:49 +00:00
|
|
|
#include <sys/param.h>
|
1994-05-24 09:57:34 +00:00
|
|
|
#include <sys/types.h>
|
1994-09-25 02:12:49 +00:00
|
|
|
#include <sys/cdefs.h>
|
1999-12-28 02:37:14 +00:00
|
|
|
#include <sys/socket.h>
|
1994-09-25 02:12:49 +00:00
|
|
|
#include <stdio.h>
|
2024-01-08 11:52:08 +00:00
|
|
|
#include <netinet/in.h>
|
Update the resolver in libc to BIND9's one.
Since, res_sendsigned(3) and the friends use MD5 functions, it is
hard to include them without having MD5 functions in libc. So,
res_sendsigned(3) is not merged into libc.
Since, res_update(3) in BIND9 is not binary compatible with our
res_update(3), res_update(3) is leaved as is, except some
necessary modifications.
The res_update(3) and the friends are not essential part of the
resolver. They are not defined in resolv.h but defined in
res_update.h separately in BIND9. Further, they are not called from
our tree. So, I hide them from our resolv.h, but leave them only
for binary backward compatibility (perhaps, no one calls them).
Since, struct __res_state_ext is not exposed in BIND9, I hide it
from our resolv.h. And, global variable _res_ext is removed. It
breaks binary backward compatibility. But, since it is not used from
outside of our libc, I think it is safe.
Reviewed by: arch@ (no objection)
2006-03-21 16:11:11 +00:00
|
|
|
#include <arpa/nameser.h>
|
1994-09-25 02:12:49 +00:00
|
|
|
|
2007-06-03 17:20:27 +00:00
|
|
|
/*%
|
1996-12-30 13:08:54 +00:00
|
|
|
* Revision information. This is the release date in YYYYMMDD format.
|
|
|
|
* It can change every day so the right thing to do with it is use it
|
|
|
|
* in preprocessor commands such as "#if (__RES > 19931104)". Do not
|
1994-09-25 02:12:49 +00:00
|
|
|
* compare for equality; rather, use it to determine whether your resolver
|
|
|
|
* is new enough to contain a certain feature.
|
|
|
|
*/
|
|
|
|
|
2014-08-05 23:16:31 +00:00
|
|
|
#define __RES 20090302
|
Update the resolver in libc to BIND9's one.
Since, res_sendsigned(3) and the friends use MD5 functions, it is
hard to include them without having MD5 functions in libc. So,
res_sendsigned(3) is not merged into libc.
Since, res_update(3) in BIND9 is not binary compatible with our
res_update(3), res_update(3) is leaved as is, except some
necessary modifications.
The res_update(3) and the friends are not essential part of the
resolver. They are not defined in resolv.h but defined in
res_update.h separately in BIND9. Further, they are not called from
our tree. So, I hide them from our resolv.h, but leave them only
for binary backward compatibility (perhaps, no one calls them).
Since, struct __res_state_ext is not exposed in BIND9, I hide it
from our resolv.h. And, global variable _res_ext is removed. It
breaks binary backward compatibility. But, since it is not used from
outside of our libc, I think it is safe.
Reviewed by: arch@ (no objection)
2006-03-21 16:11:11 +00:00
|
|
|
|
2007-06-03 17:20:27 +00:00
|
|
|
/*%
|
Update the resolver in libc to BIND9's one.
Since, res_sendsigned(3) and the friends use MD5 functions, it is
hard to include them without having MD5 functions in libc. So,
res_sendsigned(3) is not merged into libc.
Since, res_update(3) in BIND9 is not binary compatible with our
res_update(3), res_update(3) is leaved as is, except some
necessary modifications.
The res_update(3) and the friends are not essential part of the
resolver. They are not defined in resolv.h but defined in
res_update.h separately in BIND9. Further, they are not called from
our tree. So, I hide them from our resolv.h, but leave them only
for binary backward compatibility (perhaps, no one calls them).
Since, struct __res_state_ext is not exposed in BIND9, I hide it
from our resolv.h. And, global variable _res_ext is removed. It
breaks binary backward compatibility. But, since it is not used from
outside of our libc, I think it is safe.
Reviewed by: arch@ (no objection)
2006-03-21 16:11:11 +00:00
|
|
|
* This used to be defined in res_query.c, now it's in herror.c.
|
|
|
|
* [XXX no it's not. It's in irs/irs_data.c]
|
|
|
|
* It was
|
|
|
|
* never extern'd by any *.h file before it was placed here. For thread
|
|
|
|
* aware programs, the last h_errno value set is stored in res->h_errno.
|
|
|
|
*
|
|
|
|
* XXX: There doesn't seem to be a good reason for exposing RES_SET_H_ERRNO
|
|
|
|
* (and __h_errno_set) to the public via <resolv.h>.
|
|
|
|
* XXX: __h_errno_set is really part of IRS, not part of the resolver.
|
|
|
|
* If somebody wants to build and use a resolver that doesn't use IRS,
|
|
|
|
* what do they do? Perhaps something like
|
|
|
|
* #ifdef WANT_IRS
|
|
|
|
* # define RES_SET_H_ERRNO(r,x) __h_errno_set(r,x)
|
|
|
|
* #else
|
|
|
|
* # define RES_SET_H_ERRNO(r,x) (h_errno = (r)->res_h_errno = (x))
|
|
|
|
* #endif
|
|
|
|
*/
|
|
|
|
|
|
|
|
#define RES_SET_H_ERRNO(r,x) __h_errno_set(r,x)
|
2007-06-03 17:20:27 +00:00
|
|
|
struct __res_state; /*%< forward */
|
Update the resolver in libc to BIND9's one.
Since, res_sendsigned(3) and the friends use MD5 functions, it is
hard to include them without having MD5 functions in libc. So,
res_sendsigned(3) is not merged into libc.
Since, res_update(3) in BIND9 is not binary compatible with our
res_update(3), res_update(3) is leaved as is, except some
necessary modifications.
The res_update(3) and the friends are not essential part of the
resolver. They are not defined in resolv.h but defined in
res_update.h separately in BIND9. Further, they are not called from
our tree. So, I hide them from our resolv.h, but leave them only
for binary backward compatibility (perhaps, no one calls them).
Since, struct __res_state_ext is not exposed in BIND9, I hide it
from our resolv.h. And, global variable _res_ext is removed. It
breaks binary backward compatibility. But, since it is not used from
outside of our libc, I think it is safe.
Reviewed by: arch@ (no objection)
2006-03-21 16:11:11 +00:00
|
|
|
__BEGIN_DECLS
|
|
|
|
void __h_errno_set(struct __res_state *, int);
|
|
|
|
__END_DECLS
|
1994-09-25 02:12:49 +00:00
|
|
|
|
2007-06-03 17:20:27 +00:00
|
|
|
/*%
|
1994-05-24 09:57:34 +00:00
|
|
|
* Resolver configuration file.
|
|
|
|
* Normally not present, but may contain the address of the
|
Update the resolver in libc to BIND9's one.
Since, res_sendsigned(3) and the friends use MD5 functions, it is
hard to include them without having MD5 functions in libc. So,
res_sendsigned(3) is not merged into libc.
Since, res_update(3) in BIND9 is not binary compatible with our
res_update(3), res_update(3) is leaved as is, except some
necessary modifications.
The res_update(3) and the friends are not essential part of the
resolver. They are not defined in resolv.h but defined in
res_update.h separately in BIND9. Further, they are not called from
our tree. So, I hide them from our resolv.h, but leave them only
for binary backward compatibility (perhaps, no one calls them).
Since, struct __res_state_ext is not exposed in BIND9, I hide it
from our resolv.h. And, global variable _res_ext is removed. It
breaks binary backward compatibility. But, since it is not used from
outside of our libc, I think it is safe.
Reviewed by: arch@ (no objection)
2006-03-21 16:11:11 +00:00
|
|
|
* initial name server(s) to query and the domain search list.
|
1994-05-24 09:57:34 +00:00
|
|
|
*/
|
|
|
|
|
|
|
|
#ifndef _PATH_RESCONF
|
1994-09-25 02:12:49 +00:00
|
|
|
#define _PATH_RESCONF "/etc/resolv.conf"
|
1994-05-24 09:57:34 +00:00
|
|
|
#endif
|
|
|
|
|
Update the resolver in libc to BIND9's one.
Since, res_sendsigned(3) and the friends use MD5 functions, it is
hard to include them without having MD5 functions in libc. So,
res_sendsigned(3) is not merged into libc.
Since, res_update(3) in BIND9 is not binary compatible with our
res_update(3), res_update(3) is leaved as is, except some
necessary modifications.
The res_update(3) and the friends are not essential part of the
resolver. They are not defined in resolv.h but defined in
res_update.h separately in BIND9. Further, they are not called from
our tree. So, I hide them from our resolv.h, but leave them only
for binary backward compatibility (perhaps, no one calls them).
Since, struct __res_state_ext is not exposed in BIND9, I hide it
from our resolv.h. And, global variable _res_ext is removed. It
breaks binary backward compatibility. But, since it is not used from
outside of our libc, I think it is safe.
Reviewed by: arch@ (no objection)
2006-03-21 16:11:11 +00:00
|
|
|
typedef enum { res_goahead, res_nextns, res_modified, res_done, res_error }
|
|
|
|
res_sendhookact;
|
|
|
|
|
|
|
|
typedef res_sendhookact (*res_send_qhook)(struct sockaddr * const *,
|
|
|
|
const u_char **, int *,
|
|
|
|
u_char *, int, int *);
|
|
|
|
|
|
|
|
typedef res_sendhookact (*res_send_rhook)(const struct sockaddr *,
|
|
|
|
const u_char *, int, u_char *,
|
|
|
|
int, int *);
|
|
|
|
|
|
|
|
struct res_sym {
|
2007-06-03 17:20:27 +00:00
|
|
|
int number; /*%< Identifying number, like T_MX */
|
|
|
|
const char * name; /*%< Its symbolic name, like "MX" */
|
|
|
|
const char * humanname; /*%< Its fun name, like "mail exchanger" */
|
Update the resolver in libc to BIND9's one.
Since, res_sendsigned(3) and the friends use MD5 functions, it is
hard to include them without having MD5 functions in libc. So,
res_sendsigned(3) is not merged into libc.
Since, res_update(3) in BIND9 is not binary compatible with our
res_update(3), res_update(3) is leaved as is, except some
necessary modifications.
The res_update(3) and the friends are not essential part of the
resolver. They are not defined in resolv.h but defined in
res_update.h separately in BIND9. Further, they are not called from
our tree. So, I hide them from our resolv.h, but leave them only
for binary backward compatibility (perhaps, no one calls them).
Since, struct __res_state_ext is not exposed in BIND9, I hide it
from our resolv.h. And, global variable _res_ext is removed. It
breaks binary backward compatibility. But, since it is not used from
outside of our libc, I think it is safe.
Reviewed by: arch@ (no objection)
2006-03-21 16:11:11 +00:00
|
|
|
};
|
|
|
|
|
2007-06-03 17:20:27 +00:00
|
|
|
/*%
|
1994-05-24 09:57:34 +00:00
|
|
|
* Global defines and variables for resolver stub.
|
|
|
|
*/
|
2007-06-03 17:20:27 +00:00
|
|
|
#define MAXNS 3 /*%< max # name servers we'll track */
|
|
|
|
#define MAXDFLSRCH 3 /*%< # default domain levels to try */
|
|
|
|
#define MAXDNSRCH 6 /*%< max # domains in search path */
|
|
|
|
#define LOCALDOMAINPARTS 2 /*%< min levels in name that is "local" */
|
|
|
|
#define RES_TIMEOUT 5 /*%< min. seconds between retries */
|
|
|
|
#define MAXRESOLVSORT 10 /*%< number of net to sort on */
|
|
|
|
#define RES_MAXNDOTS 15 /*%< should reflect bit field size */
|
|
|
|
#define RES_MAXRETRANS 30 /*%< only for resolv.conf/RES_OPTIONS */
|
|
|
|
#define RES_MAXRETRY 5 /*%< only for resolv.conf/RES_OPTIONS */
|
|
|
|
#define RES_DFLRETRY 2 /*%< Default #/tries. */
|
|
|
|
#define RES_MAXTIME 65535 /*%< Infinity, in milliseconds. */
|
Update the resolver in libc to BIND9's one.
Since, res_sendsigned(3) and the friends use MD5 functions, it is
hard to include them without having MD5 functions in libc. So,
res_sendsigned(3) is not merged into libc.
Since, res_update(3) in BIND9 is not binary compatible with our
res_update(3), res_update(3) is leaved as is, except some
necessary modifications.
The res_update(3) and the friends are not essential part of the
resolver. They are not defined in resolv.h but defined in
res_update.h separately in BIND9. Further, they are not called from
our tree. So, I hide them from our resolv.h, but leave them only
for binary backward compatibility (perhaps, no one calls them).
Since, struct __res_state_ext is not exposed in BIND9, I hide it
from our resolv.h. And, global variable _res_ext is removed. It
breaks binary backward compatibility. But, since it is not used from
outside of our libc, I think it is safe.
Reviewed by: arch@ (no objection)
2006-03-21 16:11:11 +00:00
|
|
|
struct __res_state_ext;
|
1994-05-24 09:57:34 +00:00
|
|
|
|
|
|
|
struct __res_state {
|
2007-06-03 17:20:27 +00:00
|
|
|
int retrans; /*%< retransmission time interval */
|
|
|
|
int retry; /*%< number of times to retransmit */
|
Update the resolver in libc to BIND9's one.
Since, res_sendsigned(3) and the friends use MD5 functions, it is
hard to include them without having MD5 functions in libc. So,
res_sendsigned(3) is not merged into libc.
Since, res_update(3) in BIND9 is not binary compatible with our
res_update(3), res_update(3) is leaved as is, except some
necessary modifications.
The res_update(3) and the friends are not essential part of the
resolver. They are not defined in resolv.h but defined in
res_update.h separately in BIND9. Further, they are not called from
our tree. So, I hide them from our resolv.h, but leave them only
for binary backward compatibility (perhaps, no one calls them).
Since, struct __res_state_ext is not exposed in BIND9, I hide it
from our resolv.h. And, global variable _res_ext is removed. It
breaks binary backward compatibility. But, since it is not used from
outside of our libc, I think it is safe.
Reviewed by: arch@ (no objection)
2006-03-21 16:11:11 +00:00
|
|
|
/*
|
|
|
|
* XXX: If `sun' is defined, `options' and `pfcode' are
|
|
|
|
* defined as u_int in original BIND9 distribution. However,
|
|
|
|
* it breaks binary backward compatibility against FreeBSD's
|
|
|
|
* resolver. So, we changed not to see `sun'.
|
|
|
|
*/
|
|
|
|
#if defined(sun) && 0
|
2007-06-03 17:20:27 +00:00
|
|
|
u_int options; /*%< option flags - see below. */
|
Update the resolver in libc to BIND9's one.
Since, res_sendsigned(3) and the friends use MD5 functions, it is
hard to include them without having MD5 functions in libc. So,
res_sendsigned(3) is not merged into libc.
Since, res_update(3) in BIND9 is not binary compatible with our
res_update(3), res_update(3) is leaved as is, except some
necessary modifications.
The res_update(3) and the friends are not essential part of the
resolver. They are not defined in resolv.h but defined in
res_update.h separately in BIND9. Further, they are not called from
our tree. So, I hide them from our resolv.h, but leave them only
for binary backward compatibility (perhaps, no one calls them).
Since, struct __res_state_ext is not exposed in BIND9, I hide it
from our resolv.h. And, global variable _res_ext is removed. It
breaks binary backward compatibility. But, since it is not used from
outside of our libc, I think it is safe.
Reviewed by: arch@ (no objection)
2006-03-21 16:11:11 +00:00
|
|
|
#else
|
2007-06-03 17:20:27 +00:00
|
|
|
u_long options; /*%< option flags - see below. */
|
Update the resolver in libc to BIND9's one.
Since, res_sendsigned(3) and the friends use MD5 functions, it is
hard to include them without having MD5 functions in libc. So,
res_sendsigned(3) is not merged into libc.
Since, res_update(3) in BIND9 is not binary compatible with our
res_update(3), res_update(3) is leaved as is, except some
necessary modifications.
The res_update(3) and the friends are not essential part of the
resolver. They are not defined in resolv.h but defined in
res_update.h separately in BIND9. Further, they are not called from
our tree. So, I hide them from our resolv.h, but leave them only
for binary backward compatibility (perhaps, no one calls them).
Since, struct __res_state_ext is not exposed in BIND9, I hide it
from our resolv.h. And, global variable _res_ext is removed. It
breaks binary backward compatibility. But, since it is not used from
outside of our libc, I think it is safe.
Reviewed by: arch@ (no objection)
2006-03-21 16:11:11 +00:00
|
|
|
#endif
|
2007-06-03 17:20:27 +00:00
|
|
|
int nscount; /*%< number of name servers */
|
1994-09-25 02:12:49 +00:00
|
|
|
struct sockaddr_in
|
2007-06-03 17:20:27 +00:00
|
|
|
nsaddr_list[MAXNS]; /*%< address of name server */
|
|
|
|
#define nsaddr nsaddr_list[0] /*%< for backward compatibility */
|
|
|
|
u_short id; /*%< current message id */
|
|
|
|
char *dnsrch[MAXDNSRCH+1]; /*%< components of domain to search */
|
|
|
|
char defdname[256]; /*%< default domain (deprecated) */
|
Update the resolver in libc to BIND9's one.
Since, res_sendsigned(3) and the friends use MD5 functions, it is
hard to include them without having MD5 functions in libc. So,
res_sendsigned(3) is not merged into libc.
Since, res_update(3) in BIND9 is not binary compatible with our
res_update(3), res_update(3) is leaved as is, except some
necessary modifications.
The res_update(3) and the friends are not essential part of the
resolver. They are not defined in resolv.h but defined in
res_update.h separately in BIND9. Further, they are not called from
our tree. So, I hide them from our resolv.h, but leave them only
for binary backward compatibility (perhaps, no one calls them).
Since, struct __res_state_ext is not exposed in BIND9, I hide it
from our resolv.h. And, global variable _res_ext is removed. It
breaks binary backward compatibility. But, since it is not used from
outside of our libc, I think it is safe.
Reviewed by: arch@ (no objection)
2006-03-21 16:11:11 +00:00
|
|
|
#if defined(sun) && 0
|
2007-06-03 17:20:27 +00:00
|
|
|
u_int pfcode; /*%< RES_PRF_ flags - see below. */
|
Update the resolver in libc to BIND9's one.
Since, res_sendsigned(3) and the friends use MD5 functions, it is
hard to include them without having MD5 functions in libc. So,
res_sendsigned(3) is not merged into libc.
Since, res_update(3) in BIND9 is not binary compatible with our
res_update(3), res_update(3) is leaved as is, except some
necessary modifications.
The res_update(3) and the friends are not essential part of the
resolver. They are not defined in resolv.h but defined in
res_update.h separately in BIND9. Further, they are not called from
our tree. So, I hide them from our resolv.h, but leave them only
for binary backward compatibility (perhaps, no one calls them).
Since, struct __res_state_ext is not exposed in BIND9, I hide it
from our resolv.h. And, global variable _res_ext is removed. It
breaks binary backward compatibility. But, since it is not used from
outside of our libc, I think it is safe.
Reviewed by: arch@ (no objection)
2006-03-21 16:11:11 +00:00
|
|
|
#else
|
2007-06-03 17:20:27 +00:00
|
|
|
u_long pfcode; /*%< RES_PRF_ flags - see below. */
|
Update the resolver in libc to BIND9's one.
Since, res_sendsigned(3) and the friends use MD5 functions, it is
hard to include them without having MD5 functions in libc. So,
res_sendsigned(3) is not merged into libc.
Since, res_update(3) in BIND9 is not binary compatible with our
res_update(3), res_update(3) is leaved as is, except some
necessary modifications.
The res_update(3) and the friends are not essential part of the
resolver. They are not defined in resolv.h but defined in
res_update.h separately in BIND9. Further, they are not called from
our tree. So, I hide them from our resolv.h, but leave them only
for binary backward compatibility (perhaps, no one calls them).
Since, struct __res_state_ext is not exposed in BIND9, I hide it
from our resolv.h. And, global variable _res_ext is removed. It
breaks binary backward compatibility. But, since it is not used from
outside of our libc, I think it is safe.
Reviewed by: arch@ (no objection)
2006-03-21 16:11:11 +00:00
|
|
|
#endif
|
2007-06-03 17:20:27 +00:00
|
|
|
unsigned ndots:4; /*%< threshold for initial abs. query */
|
|
|
|
unsigned nsort:4; /*%< number of elements in sort_list[] */
|
1994-09-25 02:12:49 +00:00
|
|
|
char unused[3];
|
|
|
|
struct {
|
|
|
|
struct in_addr addr;
|
|
|
|
u_int32_t mask;
|
|
|
|
} sort_list[MAXRESOLVSORT];
|
2007-06-03 17:20:27 +00:00
|
|
|
res_send_qhook qhook; /*%< query hook */
|
|
|
|
res_send_rhook rhook; /*%< response hook */
|
|
|
|
int res_h_errno; /*%< last one set for this context */
|
|
|
|
int _vcsock; /*%< PRIVATE: for res_send VC i/o */
|
|
|
|
u_int _flags; /*%< PRIVATE: see below */
|
2015-12-14 17:21:06 +00:00
|
|
|
u_int _pad; /*%< make _u 64 bit aligned */
|
Update the resolver in libc to BIND9's one.
Since, res_sendsigned(3) and the friends use MD5 functions, it is
hard to include them without having MD5 functions in libc. So,
res_sendsigned(3) is not merged into libc.
Since, res_update(3) in BIND9 is not binary compatible with our
res_update(3), res_update(3) is leaved as is, except some
necessary modifications.
The res_update(3) and the friends are not essential part of the
resolver. They are not defined in resolv.h but defined in
res_update.h separately in BIND9. Further, they are not called from
our tree. So, I hide them from our resolv.h, but leave them only
for binary backward compatibility (perhaps, no one calls them).
Since, struct __res_state_ext is not exposed in BIND9, I hide it
from our resolv.h. And, global variable _res_ext is removed. It
breaks binary backward compatibility. But, since it is not used from
outside of our libc, I think it is safe.
Reviewed by: arch@ (no objection)
2006-03-21 16:11:11 +00:00
|
|
|
union {
|
|
|
|
/* On an 32-bit arch this means 512b total. */
|
2014-08-12 12:36:06 +00:00
|
|
|
char pad[72 - 4*sizeof (int) - 3*sizeof (void *)];
|
Update the resolver in libc to BIND9's one.
Since, res_sendsigned(3) and the friends use MD5 functions, it is
hard to include them without having MD5 functions in libc. So,
res_sendsigned(3) is not merged into libc.
Since, res_update(3) in BIND9 is not binary compatible with our
res_update(3), res_update(3) is leaved as is, except some
necessary modifications.
The res_update(3) and the friends are not essential part of the
resolver. They are not defined in resolv.h but defined in
res_update.h separately in BIND9. Further, they are not called from
our tree. So, I hide them from our resolv.h, but leave them only
for binary backward compatibility (perhaps, no one calls them).
Since, struct __res_state_ext is not exposed in BIND9, I hide it
from our resolv.h. And, global variable _res_ext is removed. It
breaks binary backward compatibility. But, since it is not used from
outside of our libc, I think it is safe.
Reviewed by: arch@ (no objection)
2006-03-21 16:11:11 +00:00
|
|
|
struct {
|
|
|
|
u_int16_t nscount;
|
2007-06-03 17:20:27 +00:00
|
|
|
u_int16_t nstimes[MAXNS]; /*%< ms. */
|
Update the resolver in libc to BIND9's one.
Since, res_sendsigned(3) and the friends use MD5 functions, it is
hard to include them without having MD5 functions in libc. So,
res_sendsigned(3) is not merged into libc.
Since, res_update(3) in BIND9 is not binary compatible with our
res_update(3), res_update(3) is leaved as is, except some
necessary modifications.
The res_update(3) and the friends are not essential part of the
resolver. They are not defined in resolv.h but defined in
res_update.h separately in BIND9. Further, they are not called from
our tree. So, I hide them from our resolv.h, but leave them only
for binary backward compatibility (perhaps, no one calls them).
Since, struct __res_state_ext is not exposed in BIND9, I hide it
from our resolv.h. And, global variable _res_ext is removed. It
breaks binary backward compatibility. But, since it is not used from
outside of our libc, I think it is safe.
Reviewed by: arch@ (no objection)
2006-03-21 16:11:11 +00:00
|
|
|
int nssocks[MAXNS];
|
2012-01-07 16:10:15 +00:00
|
|
|
struct __res_state_ext *ext; /*%< extension for IPv6 */
|
Update the resolver in libc to BIND9's one.
Since, res_sendsigned(3) and the friends use MD5 functions, it is
hard to include them without having MD5 functions in libc. So,
res_sendsigned(3) is not merged into libc.
Since, res_update(3) in BIND9 is not binary compatible with our
res_update(3), res_update(3) is leaved as is, except some
necessary modifications.
The res_update(3) and the friends are not essential part of the
resolver. They are not defined in resolv.h but defined in
res_update.h separately in BIND9. Further, they are not called from
our tree. So, I hide them from our resolv.h, but leave them only
for binary backward compatibility (perhaps, no one calls them).
Since, struct __res_state_ext is not exposed in BIND9, I hide it
from our resolv.h. And, global variable _res_ext is removed. It
breaks binary backward compatibility. But, since it is not used from
outside of our libc, I think it is safe.
Reviewed by: arch@ (no objection)
2006-03-21 16:11:11 +00:00
|
|
|
} _ext;
|
|
|
|
} _u;
|
2014-08-12 12:36:06 +00:00
|
|
|
u_char *_rnd; /*%< PRIVATE: random state */
|
Update the resolver in libc to BIND9's one.
Since, res_sendsigned(3) and the friends use MD5 functions, it is
hard to include them without having MD5 functions in libc. So,
res_sendsigned(3) is not merged into libc.
Since, res_update(3) in BIND9 is not binary compatible with our
res_update(3), res_update(3) is leaved as is, except some
necessary modifications.
The res_update(3) and the friends are not essential part of the
resolver. They are not defined in resolv.h but defined in
res_update.h separately in BIND9. Further, they are not called from
our tree. So, I hide them from our resolv.h, but leave them only
for binary backward compatibility (perhaps, no one calls them).
Since, struct __res_state_ext is not exposed in BIND9, I hide it
from our resolv.h. And, global variable _res_ext is removed. It
breaks binary backward compatibility. But, since it is not used from
outside of our libc, I think it is safe.
Reviewed by: arch@ (no objection)
2006-03-21 16:11:11 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
typedef struct __res_state *res_state;
|
|
|
|
|
|
|
|
union res_sockaddr_union {
|
|
|
|
struct sockaddr_in sin;
|
|
|
|
#ifdef IN6ADDR_ANY_INIT
|
|
|
|
struct sockaddr_in6 sin6;
|
|
|
|
#endif
|
|
|
|
#ifdef ISC_ALIGN64
|
2007-06-03 17:20:27 +00:00
|
|
|
int64_t __align64; /*%< 64bit alignment */
|
Update the resolver in libc to BIND9's one.
Since, res_sendsigned(3) and the friends use MD5 functions, it is
hard to include them without having MD5 functions in libc. So,
res_sendsigned(3) is not merged into libc.
Since, res_update(3) in BIND9 is not binary compatible with our
res_update(3), res_update(3) is leaved as is, except some
necessary modifications.
The res_update(3) and the friends are not essential part of the
resolver. They are not defined in resolv.h but defined in
res_update.h separately in BIND9. Further, they are not called from
our tree. So, I hide them from our resolv.h, but leave them only
for binary backward compatibility (perhaps, no one calls them).
Since, struct __res_state_ext is not exposed in BIND9, I hide it
from our resolv.h. And, global variable _res_ext is removed. It
breaks binary backward compatibility. But, since it is not used from
outside of our libc, I think it is safe.
Reviewed by: arch@ (no objection)
2006-03-21 16:11:11 +00:00
|
|
|
#else
|
2007-06-03 17:20:27 +00:00
|
|
|
int32_t __align32; /*%< 32bit alignment */
|
Update the resolver in libc to BIND9's one.
Since, res_sendsigned(3) and the friends use MD5 functions, it is
hard to include them without having MD5 functions in libc. So,
res_sendsigned(3) is not merged into libc.
Since, res_update(3) in BIND9 is not binary compatible with our
res_update(3), res_update(3) is leaved as is, except some
necessary modifications.
The res_update(3) and the friends are not essential part of the
resolver. They are not defined in resolv.h but defined in
res_update.h separately in BIND9. Further, they are not called from
our tree. So, I hide them from our resolv.h, but leave them only
for binary backward compatibility (perhaps, no one calls them).
Since, struct __res_state_ext is not exposed in BIND9, I hide it
from our resolv.h. And, global variable _res_ext is removed. It
breaks binary backward compatibility. But, since it is not used from
outside of our libc, I think it is safe.
Reviewed by: arch@ (no objection)
2006-03-21 16:11:11 +00:00
|
|
|
#endif
|
2007-06-03 17:20:27 +00:00
|
|
|
char __space[128]; /*%< max size */
|
1994-05-24 09:57:34 +00:00
|
|
|
};
|
|
|
|
|
2007-06-03 17:20:27 +00:00
|
|
|
/*%
|
Update the resolver in libc to BIND9's one.
Since, res_sendsigned(3) and the friends use MD5 functions, it is
hard to include them without having MD5 functions in libc. So,
res_sendsigned(3) is not merged into libc.
Since, res_update(3) in BIND9 is not binary compatible with our
res_update(3), res_update(3) is leaved as is, except some
necessary modifications.
The res_update(3) and the friends are not essential part of the
resolver. They are not defined in resolv.h but defined in
res_update.h separately in BIND9. Further, they are not called from
our tree. So, I hide them from our resolv.h, but leave them only
for binary backward compatibility (perhaps, no one calls them).
Since, struct __res_state_ext is not exposed in BIND9, I hide it
from our resolv.h. And, global variable _res_ext is removed. It
breaks binary backward compatibility. But, since it is not used from
outside of our libc, I think it is safe.
Reviewed by: arch@ (no objection)
2006-03-21 16:11:11 +00:00
|
|
|
* Resolver flags (used to be discrete per-module statics ints).
|
1999-12-28 02:37:14 +00:00
|
|
|
*/
|
2007-06-03 17:20:27 +00:00
|
|
|
#define RES_F_VC 0x00000001 /*%< socket is TCP */
|
|
|
|
#define RES_F_CONN 0x00000002 /*%< socket is connected */
|
|
|
|
#define RES_F_EDNS0ERR 0x00000004 /*%< EDNS0 caused errors */
|
|
|
|
#define RES_F__UNUSED 0x00000008 /*%< (unused) */
|
|
|
|
#define RES_F_LASTMASK 0x000000F0 /*%< ordinal server of last res_nsend */
|
|
|
|
#define RES_F_LASTSHIFT 4 /*%< bit position of LASTMASK "flag" */
|
Update the resolver in libc to BIND9's one.
Since, res_sendsigned(3) and the friends use MD5 functions, it is
hard to include them without having MD5 functions in libc. So,
res_sendsigned(3) is not merged into libc.
Since, res_update(3) in BIND9 is not binary compatible with our
res_update(3), res_update(3) is leaved as is, except some
necessary modifications.
The res_update(3) and the friends are not essential part of the
resolver. They are not defined in resolv.h but defined in
res_update.h separately in BIND9. Further, they are not called from
our tree. So, I hide them from our resolv.h, but leave them only
for binary backward compatibility (perhaps, no one calls them).
Since, struct __res_state_ext is not exposed in BIND9, I hide it
from our resolv.h. And, global variable _res_ext is removed. It
breaks binary backward compatibility. But, since it is not used from
outside of our libc, I think it is safe.
Reviewed by: arch@ (no objection)
2006-03-21 16:11:11 +00:00
|
|
|
#define RES_GETLAST(res) (((res)._flags & RES_F_LASTMASK) >> RES_F_LASTSHIFT)
|
|
|
|
|
|
|
|
/* res_findzonecut2() options */
|
2007-06-03 17:20:27 +00:00
|
|
|
#define RES_EXHAUSTIVE 0x00000001 /*%< always do all queries */
|
|
|
|
#define RES_IPV4ONLY 0x00000002 /*%< IPv4 only */
|
|
|
|
#define RES_IPV6ONLY 0x00000004 /*%< IPv6 only */
|
1999-12-28 02:37:14 +00:00
|
|
|
|
2007-06-03 17:20:27 +00:00
|
|
|
/*%
|
1994-05-24 09:57:34 +00:00
|
|
|
* Resolver options (keep these in synch with res_debug.c, please)
|
|
|
|
*/
|
2007-06-03 17:20:27 +00:00
|
|
|
#define RES_INIT 0x00000001 /*%< address initialized */
|
|
|
|
#define RES_DEBUG 0x00000002 /*%< print debug messages */
|
|
|
|
#define RES_AAONLY 0x00000004 /*%< authoritative answers only (!IMPL)*/
|
|
|
|
#define RES_USEVC 0x00000008 /*%< use virtual circuit */
|
|
|
|
#define RES_PRIMARY 0x00000010 /*%< query primary server only (!IMPL) */
|
|
|
|
#define RES_IGNTC 0x00000020 /*%< ignore truncation errors */
|
|
|
|
#define RES_RECURSE 0x00000040 /*%< recursion desired */
|
|
|
|
#define RES_DEFNAMES 0x00000080 /*%< use default domain name */
|
|
|
|
#define RES_STAYOPEN 0x00000100 /*%< Keep TCP socket open */
|
|
|
|
#define RES_DNSRCH 0x00000200 /*%< search up local domain tree */
|
|
|
|
#define RES_INSECURE1 0x00000400 /*%< type 1 security disabled */
|
|
|
|
#define RES_INSECURE2 0x00000800 /*%< type 2 security disabled */
|
|
|
|
#define RES_NOALIASES 0x00001000 /*%< shuts off HOSTALIASES feature */
|
|
|
|
#define RES_USE_INET6 0x00002000 /*%< use/map IPv6 in gethostbyname() */
|
|
|
|
#define RES_ROTATE 0x00004000 /*%< rotate ns list after each query */
|
|
|
|
#define RES_NOCHECKNAME 0x00008000 /*%< do not check names for sanity. */
|
|
|
|
#define RES_KEEPTSIG 0x00010000 /*%< do not strip TSIG records */
|
|
|
|
#define RES_BLAST 0x00020000 /*%< blast all recursive servers */
|
2008-12-14 19:39:53 +00:00
|
|
|
#define RES_NSID 0x00040000 /*%< request name server ID */
|
2007-06-03 17:20:27 +00:00
|
|
|
#define RES_NOTLDQUERY 0x00100000 /*%< don't unqualified name as a tld */
|
|
|
|
#define RES_USE_DNSSEC 0x00200000 /*%< use DNSSEC using OK bit in OPT */
|
Update the resolver in libc to BIND9's one.
Since, res_sendsigned(3) and the friends use MD5 functions, it is
hard to include them without having MD5 functions in libc. So,
res_sendsigned(3) is not merged into libc.
Since, res_update(3) in BIND9 is not binary compatible with our
res_update(3), res_update(3) is leaved as is, except some
necessary modifications.
The res_update(3) and the friends are not essential part of the
resolver. They are not defined in resolv.h but defined in
res_update.h separately in BIND9. Further, they are not called from
our tree. So, I hide them from our resolv.h, but leave them only
for binary backward compatibility (perhaps, no one calls them).
Since, struct __res_state_ext is not exposed in BIND9, I hide it
from our resolv.h. And, global variable _res_ext is removed. It
breaks binary backward compatibility. But, since it is not used from
outside of our libc, I think it is safe.
Reviewed by: arch@ (no objection)
2006-03-21 16:11:11 +00:00
|
|
|
/* #define RES_DEBUG2 0x00400000 */ /* nslookup internal */
|
2001-06-10 20:25:24 +00:00
|
|
|
/* KAME extensions: use higher bit to avoid conflict with ISC use */
|
2007-06-03 17:20:27 +00:00
|
|
|
#define RES_USE_DNAME 0x10000000 /*%< use DNAME */
|
|
|
|
#define RES_USE_EDNS0 0x40000000 /*%< use EDNS0 if configured */
|
|
|
|
#define RES_NO_NIBBLE2 0x80000000 /*%< disable alternate nibble lookup */
|
1994-09-25 02:12:49 +00:00
|
|
|
|
Update the resolver in libc to BIND9's one.
Since, res_sendsigned(3) and the friends use MD5 functions, it is
hard to include them without having MD5 functions in libc. So,
res_sendsigned(3) is not merged into libc.
Since, res_update(3) in BIND9 is not binary compatible with our
res_update(3), res_update(3) is leaved as is, except some
necessary modifications.
The res_update(3) and the friends are not essential part of the
resolver. They are not defined in resolv.h but defined in
res_update.h separately in BIND9. Further, they are not called from
our tree. So, I hide them from our resolv.h, but leave them only
for binary backward compatibility (perhaps, no one calls them).
Since, struct __res_state_ext is not exposed in BIND9, I hide it
from our resolv.h. And, global variable _res_ext is removed. It
breaks binary backward compatibility. But, since it is not used from
outside of our libc, I think it is safe.
Reviewed by: arch@ (no objection)
2006-03-21 16:11:11 +00:00
|
|
|
#define RES_DEFAULT (RES_RECURSE | RES_DEFNAMES | \
|
|
|
|
RES_DNSRCH | RES_NO_NIBBLE2)
|
1994-05-24 09:57:34 +00:00
|
|
|
|
2007-06-03 17:20:27 +00:00
|
|
|
/*%
|
1994-05-24 09:57:34 +00:00
|
|
|
* Resolver "pfcode" values. Used by dig.
|
|
|
|
*/
|
1994-09-25 02:12:49 +00:00
|
|
|
#define RES_PRF_STATS 0x00000001
|
1998-06-11 08:55:17 +00:00
|
|
|
#define RES_PRF_UPDATE 0x00000002
|
1994-09-25 02:12:49 +00:00
|
|
|
#define RES_PRF_CLASS 0x00000004
|
|
|
|
#define RES_PRF_CMD 0x00000008
|
|
|
|
#define RES_PRF_QUES 0x00000010
|
|
|
|
#define RES_PRF_ANS 0x00000020
|
|
|
|
#define RES_PRF_AUTH 0x00000040
|
|
|
|
#define RES_PRF_ADD 0x00000080
|
|
|
|
#define RES_PRF_HEAD1 0x00000100
|
|
|
|
#define RES_PRF_HEAD2 0x00000200
|
|
|
|
#define RES_PRF_TTLID 0x00000400
|
|
|
|
#define RES_PRF_HEADX 0x00000800
|
|
|
|
#define RES_PRF_QUERY 0x00001000
|
|
|
|
#define RES_PRF_REPLY 0x00002000
|
Update the resolver in libc to BIND9's one.
Since, res_sendsigned(3) and the friends use MD5 functions, it is
hard to include them without having MD5 functions in libc. So,
res_sendsigned(3) is not merged into libc.
Since, res_update(3) in BIND9 is not binary compatible with our
res_update(3), res_update(3) is leaved as is, except some
necessary modifications.
The res_update(3) and the friends are not essential part of the
resolver. They are not defined in resolv.h but defined in
res_update.h separately in BIND9. Further, they are not called from
our tree. So, I hide them from our resolv.h, but leave them only
for binary backward compatibility (perhaps, no one calls them).
Since, struct __res_state_ext is not exposed in BIND9, I hide it
from our resolv.h. And, global variable _res_ext is removed. It
breaks binary backward compatibility. But, since it is not used from
outside of our libc, I think it is safe.
Reviewed by: arch@ (no objection)
2006-03-21 16:11:11 +00:00
|
|
|
#define RES_PRF_INIT 0x00004000
|
|
|
|
#define RES_PRF_TRUNC 0x00008000
|
|
|
|
/* 0x00010000 */
|
1994-05-24 09:57:34 +00:00
|
|
|
|
Update the resolver in libc to BIND9's one.
Since, res_sendsigned(3) and the friends use MD5 functions, it is
hard to include them without having MD5 functions in libc. So,
res_sendsigned(3) is not merged into libc.
Since, res_update(3) in BIND9 is not binary compatible with our
res_update(3), res_update(3) is leaved as is, except some
necessary modifications.
The res_update(3) and the friends are not essential part of the
resolver. They are not defined in resolv.h but defined in
res_update.h separately in BIND9. Further, they are not called from
our tree. So, I hide them from our resolv.h, but leave them only
for binary backward compatibility (perhaps, no one calls them).
Since, struct __res_state_ext is not exposed in BIND9, I hide it
from our resolv.h. And, global variable _res_ext is removed. It
breaks binary backward compatibility. But, since it is not used from
outside of our libc, I think it is safe.
Reviewed by: arch@ (no objection)
2006-03-21 16:11:11 +00:00
|
|
|
/* Things involving an internal (static) resolver context. */
|
|
|
|
__BEGIN_DECLS
|
|
|
|
extern struct __res_state *__res_state(void);
|
|
|
|
__END_DECLS
|
|
|
|
#define _res (*__res_state())
|
1994-05-24 09:57:34 +00:00
|
|
|
|
Update the resolver in libc to BIND9's one.
Since, res_sendsigned(3) and the friends use MD5 functions, it is
hard to include them without having MD5 functions in libc. So,
res_sendsigned(3) is not merged into libc.
Since, res_update(3) in BIND9 is not binary compatible with our
res_update(3), res_update(3) is leaved as is, except some
necessary modifications.
The res_update(3) and the friends are not essential part of the
resolver. They are not defined in resolv.h but defined in
res_update.h separately in BIND9. Further, they are not called from
our tree. So, I hide them from our resolv.h, but leave them only
for binary backward compatibility (perhaps, no one calls them).
Since, struct __res_state_ext is not exposed in BIND9, I hide it
from our resolv.h. And, global variable _res_ext is removed. It
breaks binary backward compatibility. But, since it is not used from
outside of our libc, I think it is safe.
Reviewed by: arch@ (no objection)
2006-03-21 16:11:11 +00:00
|
|
|
#ifndef __BIND_NOSTATIC
|
|
|
|
#define fp_nquery __fp_nquery
|
|
|
|
#define fp_query __fp_query
|
|
|
|
#define hostalias __hostalias
|
|
|
|
#define p_query __p_query
|
|
|
|
#define res_close __res_close
|
|
|
|
#define res_init __res_init
|
|
|
|
#define res_isourserver __res_isourserver
|
|
|
|
#define res_mkquery __res_mkquery
|
|
|
|
#define res_opt __res_opt
|
|
|
|
#define res_query __res_query
|
|
|
|
#define res_querydomain __res_querydomain
|
|
|
|
#define res_search __res_search
|
|
|
|
#define res_send __res_send
|
|
|
|
#define res_sendsigned __res_sendsigned
|
1996-12-30 13:08:54 +00:00
|
|
|
|
Make the resolver(3) and many associated interfaces much more reentrant.
The getaddrinfo(3), getipnodebyname(3) and resolver(3) can coincide now
with what should be totally reentrant, and h_errno values will now
be preserved correctly, but this does not affect interfaces such as
gethostbyname(3) which are still mostly non-reentrant.
In all of these relevant functions, the thread-safety has been pushed
down as far as it seems possible right now. This means that operations
that are selected via nsdispatch(3) (i.e. files, yp, dns) are protected
still under global locks that getaddrinfo(3) defines, but where possible
the locking is greatly reduced. The most noticeable improvement is
that multiple DNS lookups can now be run at the same time, and this
shows major improvement in performance of DNS-lookup threaded programs,
and solves the "Mozilla tab serialization" problem.
No single-threaded applications need to be recompiled. Multi-threaded
applications that reference "_res" to change resolver(3) options will
need to be recompiled, and ones which reference "h_errno" will also
if they desire the correct h_errno values. If the applications already
understood that _res and h_errno were not thread-safe and had their own
locking, they will see no performance improvement but will not
actually break in any way.
Please note that when NSS modules are used, or when nsdispatch(3)
defaults to adding any lookups of its own to the individual libc
_nsdispatch() calls, those MUST be reentrant as well.
2004-02-25 21:03:46 +00:00
|
|
|
__BEGIN_DECLS
|
Update the resolver in libc to BIND9's one.
Since, res_sendsigned(3) and the friends use MD5 functions, it is
hard to include them without having MD5 functions in libc. So,
res_sendsigned(3) is not merged into libc.
Since, res_update(3) in BIND9 is not binary compatible with our
res_update(3), res_update(3) is leaved as is, except some
necessary modifications.
The res_update(3) and the friends are not essential part of the
resolver. They are not defined in resolv.h but defined in
res_update.h separately in BIND9. Further, they are not called from
our tree. So, I hide them from our resolv.h, but leave them only
for binary backward compatibility (perhaps, no one calls them).
Since, struct __res_state_ext is not exposed in BIND9, I hide it
from our resolv.h. And, global variable _res_ext is removed. It
breaks binary backward compatibility. But, since it is not used from
outside of our libc, I think it is safe.
Reviewed by: arch@ (no objection)
2006-03-21 16:11:11 +00:00
|
|
|
void fp_nquery(const u_char *, int, FILE *);
|
|
|
|
void fp_query(const u_char *, FILE *);
|
|
|
|
const char * hostalias(const char *);
|
|
|
|
void p_query(const u_char *);
|
|
|
|
void res_close(void);
|
|
|
|
int res_init(void);
|
|
|
|
int res_isourserver(const struct sockaddr_in *);
|
|
|
|
int res_mkquery(int, const char *, int, int, const u_char *,
|
|
|
|
int, const u_char *, u_char *, int);
|
|
|
|
int res_opt(int, u_char *, int, int);
|
|
|
|
int res_query(const char *, int, int, u_char *, int);
|
|
|
|
int res_querydomain(const char *, const char *, int, int,
|
|
|
|
u_char *, int);
|
|
|
|
int res_search(const char *, int, int, u_char *, int);
|
|
|
|
int res_send(const u_char *, int, u_char *, int);
|
|
|
|
int res_sendsigned(const u_char *, int, ns_tsig_key *,
|
|
|
|
u_char *, int);
|
Make the resolver(3) and many associated interfaces much more reentrant.
The getaddrinfo(3), getipnodebyname(3) and resolver(3) can coincide now
with what should be totally reentrant, and h_errno values will now
be preserved correctly, but this does not affect interfaces such as
gethostbyname(3) which are still mostly non-reentrant.
In all of these relevant functions, the thread-safety has been pushed
down as far as it seems possible right now. This means that operations
that are selected via nsdispatch(3) (i.e. files, yp, dns) are protected
still under global locks that getaddrinfo(3) defines, but where possible
the locking is greatly reduced. The most noticeable improvement is
that multiple DNS lookups can now be run at the same time, and this
shows major improvement in performance of DNS-lookup threaded programs,
and solves the "Mozilla tab serialization" problem.
No single-threaded applications need to be recompiled. Multi-threaded
applications that reference "_res" to change resolver(3) options will
need to be recompiled, and ones which reference "h_errno" will also
if they desire the correct h_errno values. If the applications already
understood that _res and h_errno were not thread-safe and had their own
locking, they will see no performance improvement but will not
actually break in any way.
Please note that when NSS modules are used, or when nsdispatch(3)
defaults to adding any lookups of its own to the individual libc
_nsdispatch() calls, those MUST be reentrant as well.
2004-02-25 21:03:46 +00:00
|
|
|
__END_DECLS
|
Update the resolver in libc to BIND9's one.
Since, res_sendsigned(3) and the friends use MD5 functions, it is
hard to include them without having MD5 functions in libc. So,
res_sendsigned(3) is not merged into libc.
Since, res_update(3) in BIND9 is not binary compatible with our
res_update(3), res_update(3) is leaved as is, except some
necessary modifications.
The res_update(3) and the friends are not essential part of the
resolver. They are not defined in resolv.h but defined in
res_update.h separately in BIND9. Further, they are not called from
our tree. So, I hide them from our resolv.h, but leave them only
for binary backward compatibility (perhaps, no one calls them).
Since, struct __res_state_ext is not exposed in BIND9, I hide it
from our resolv.h. And, global variable _res_ext is removed. It
breaks binary backward compatibility. But, since it is not used from
outside of our libc, I think it is safe.
Reviewed by: arch@ (no objection)
2006-03-21 16:11:11 +00:00
|
|
|
#endif
|
1999-12-28 02:37:14 +00:00
|
|
|
|
Update the resolver in libc to BIND9's one.
Since, res_sendsigned(3) and the friends use MD5 functions, it is
hard to include them without having MD5 functions in libc. So,
res_sendsigned(3) is not merged into libc.
Since, res_update(3) in BIND9 is not binary compatible with our
res_update(3), res_update(3) is leaved as is, except some
necessary modifications.
The res_update(3) and the friends are not essential part of the
resolver. They are not defined in resolv.h but defined in
res_update.h separately in BIND9. Further, they are not called from
our tree. So, I hide them from our resolv.h, but leave them only
for binary backward compatibility (perhaps, no one calls them).
Since, struct __res_state_ext is not exposed in BIND9, I hide it
from our resolv.h. And, global variable _res_ext is removed. It
breaks binary backward compatibility. But, since it is not used from
outside of our libc, I think it is safe.
Reviewed by: arch@ (no objection)
2006-03-21 16:11:11 +00:00
|
|
|
#if !defined(SHARED_LIBBIND) || defined(LIB)
|
|
|
|
/*
|
|
|
|
* If libbind is a shared object (well, DLL anyway)
|
2014-08-05 23:16:31 +00:00
|
|
|
* these externs break the linker when resolv.h is
|
Update the resolver in libc to BIND9's one.
Since, res_sendsigned(3) and the friends use MD5 functions, it is
hard to include them without having MD5 functions in libc. So,
res_sendsigned(3) is not merged into libc.
Since, res_update(3) in BIND9 is not binary compatible with our
res_update(3), res_update(3) is leaved as is, except some
necessary modifications.
The res_update(3) and the friends are not essential part of the
resolver. They are not defined in resolv.h but defined in
res_update.h separately in BIND9. Further, they are not called from
our tree. So, I hide them from our resolv.h, but leave them only
for binary backward compatibility (perhaps, no one calls them).
Since, struct __res_state_ext is not exposed in BIND9, I hide it
from our resolv.h. And, global variable _res_ext is removed. It
breaks binary backward compatibility. But, since it is not used from
outside of our libc, I think it is safe.
Reviewed by: arch@ (no objection)
2006-03-21 16:11:11 +00:00
|
|
|
* included by a lib client (like named)
|
|
|
|
* Make them go away if a client is including this
|
|
|
|
*
|
|
|
|
*/
|
|
|
|
extern const struct res_sym __p_key_syms[];
|
|
|
|
extern const struct res_sym __p_cert_syms[];
|
1996-12-30 13:08:54 +00:00
|
|
|
extern const struct res_sym __p_class_syms[];
|
|
|
|
extern const struct res_sym __p_type_syms[];
|
Update the resolver in libc to BIND9's one.
Since, res_sendsigned(3) and the friends use MD5 functions, it is
hard to include them without having MD5 functions in libc. So,
res_sendsigned(3) is not merged into libc.
Since, res_update(3) in BIND9 is not binary compatible with our
res_update(3), res_update(3) is leaved as is, except some
necessary modifications.
The res_update(3) and the friends are not essential part of the
resolver. They are not defined in resolv.h but defined in
res_update.h separately in BIND9. Further, they are not called from
our tree. So, I hide them from our resolv.h, but leave them only
for binary backward compatibility (perhaps, no one calls them).
Since, struct __res_state_ext is not exposed in BIND9, I hide it
from our resolv.h. And, global variable _res_ext is removed. It
breaks binary backward compatibility. But, since it is not used from
outside of our libc, I think it is safe.
Reviewed by: arch@ (no objection)
2006-03-21 16:11:11 +00:00
|
|
|
extern const struct res_sym __p_rcode_syms[];
|
|
|
|
#endif /* SHARED_LIBBIND */
|
1994-05-24 09:57:34 +00:00
|
|
|
|
Update the resolver in libc to BIND9's one.
Since, res_sendsigned(3) and the friends use MD5 functions, it is
hard to include them without having MD5 functions in libc. So,
res_sendsigned(3) is not merged into libc.
Since, res_update(3) in BIND9 is not binary compatible with our
res_update(3), res_update(3) is leaved as is, except some
necessary modifications.
The res_update(3) and the friends are not essential part of the
resolver. They are not defined in resolv.h but defined in
res_update.h separately in BIND9. Further, they are not called from
our tree. So, I hide them from our resolv.h, but leave them only
for binary backward compatibility (perhaps, no one calls them).
Since, struct __res_state_ext is not exposed in BIND9, I hide it
from our resolv.h. And, global variable _res_ext is removed. It
breaks binary backward compatibility. But, since it is not used from
outside of our libc, I think it is safe.
Reviewed by: arch@ (no objection)
2006-03-21 16:11:11 +00:00
|
|
|
#define b64_ntop __b64_ntop
|
|
|
|
#define b64_pton __b64_pton
|
|
|
|
#define dn_comp __dn_comp
|
|
|
|
#define dn_count_labels __dn_count_labels
|
|
|
|
#define dn_expand __dn_expand
|
|
|
|
#define dn_skipname __dn_skipname
|
|
|
|
#define fp_resstat __fp_resstat
|
|
|
|
#define loc_aton __loc_aton
|
|
|
|
#define loc_ntoa __loc_ntoa
|
|
|
|
#define p_cdname __p_cdname
|
|
|
|
#define p_cdnname __p_cdnname
|
|
|
|
#define p_class __p_class
|
|
|
|
#define p_fqname __p_fqname
|
|
|
|
#define p_fqnname __p_fqnname
|
|
|
|
#define p_option __p_option
|
|
|
|
#define p_secstodate __p_secstodate
|
|
|
|
#define p_section __p_section
|
|
|
|
#define p_time __p_time
|
|
|
|
#define p_type __p_type
|
|
|
|
#define p_rcode __p_rcode
|
|
|
|
#define p_sockun __p_sockun
|
|
|
|
#define putlong __putlong
|
|
|
|
#define putshort __putshort
|
|
|
|
#define res_dnok __res_dnok
|
|
|
|
#if 0
|
|
|
|
#define res_findzonecut __res_findzonecut
|
|
|
|
#endif
|
2006-05-21 11:19:36 +00:00
|
|
|
#define res_findzonecut2 __res_findzonecut2
|
Update the resolver in libc to BIND9's one.
Since, res_sendsigned(3) and the friends use MD5 functions, it is
hard to include them without having MD5 functions in libc. So,
res_sendsigned(3) is not merged into libc.
Since, res_update(3) in BIND9 is not binary compatible with our
res_update(3), res_update(3) is leaved as is, except some
necessary modifications.
The res_update(3) and the friends are not essential part of the
resolver. They are not defined in resolv.h but defined in
res_update.h separately in BIND9. Further, they are not called from
our tree. So, I hide them from our resolv.h, but leave them only
for binary backward compatibility (perhaps, no one calls them).
Since, struct __res_state_ext is not exposed in BIND9, I hide it
from our resolv.h. And, global variable _res_ext is removed. It
breaks binary backward compatibility. But, since it is not used from
outside of our libc, I think it is safe.
Reviewed by: arch@ (no objection)
2006-03-21 16:11:11 +00:00
|
|
|
#define res_hnok __res_hnok
|
|
|
|
#define res_hostalias __res_hostalias
|
|
|
|
#define res_mailok __res_mailok
|
|
|
|
#define res_nameinquery __res_nameinquery
|
|
|
|
#define res_nclose __res_nclose
|
|
|
|
#define res_ninit __res_ninit
|
|
|
|
#define res_nmkquery __res_nmkquery
|
|
|
|
#define res_pquery __res_pquery
|
|
|
|
#define res_nquery __res_nquery
|
|
|
|
#define res_nquerydomain __res_nquerydomain
|
|
|
|
#define res_nsearch __res_nsearch
|
|
|
|
#define res_nsend __res_nsend
|
|
|
|
#if 0
|
|
|
|
#define res_nsendsigned __res_nsendsigned
|
|
|
|
#endif
|
|
|
|
#define res_nisourserver __res_nisourserver
|
|
|
|
#define res_ownok __res_ownok
|
|
|
|
#define res_queriesmatch __res_queriesmatch
|
2014-08-05 23:16:31 +00:00
|
|
|
#define res_rndinit __res_rndinit
|
Update the resolver in libc to BIND9's one.
Since, res_sendsigned(3) and the friends use MD5 functions, it is
hard to include them without having MD5 functions in libc. So,
res_sendsigned(3) is not merged into libc.
Since, res_update(3) in BIND9 is not binary compatible with our
res_update(3), res_update(3) is leaved as is, except some
necessary modifications.
The res_update(3) and the friends are not essential part of the
resolver. They are not defined in resolv.h but defined in
res_update.h separately in BIND9. Further, they are not called from
our tree. So, I hide them from our resolv.h, but leave them only
for binary backward compatibility (perhaps, no one calls them).
Since, struct __res_state_ext is not exposed in BIND9, I hide it
from our resolv.h. And, global variable _res_ext is removed. It
breaks binary backward compatibility. But, since it is not used from
outside of our libc, I think it is safe.
Reviewed by: arch@ (no objection)
2006-03-21 16:11:11 +00:00
|
|
|
#define res_randomid __res_randomid
|
2014-08-05 23:16:31 +00:00
|
|
|
#define res_nrandomid __res_nrandomid
|
Update the resolver in libc to BIND9's one.
Since, res_sendsigned(3) and the friends use MD5 functions, it is
hard to include them without having MD5 functions in libc. So,
res_sendsigned(3) is not merged into libc.
Since, res_update(3) in BIND9 is not binary compatible with our
res_update(3), res_update(3) is leaved as is, except some
necessary modifications.
The res_update(3) and the friends are not essential part of the
resolver. They are not defined in resolv.h but defined in
res_update.h separately in BIND9. Further, they are not called from
our tree. So, I hide them from our resolv.h, but leave them only
for binary backward compatibility (perhaps, no one calls them).
Since, struct __res_state_ext is not exposed in BIND9, I hide it
from our resolv.h. And, global variable _res_ext is removed. It
breaks binary backward compatibility. But, since it is not used from
outside of our libc, I think it is safe.
Reviewed by: arch@ (no objection)
2006-03-21 16:11:11 +00:00
|
|
|
#define sym_ntop __sym_ntop
|
|
|
|
#define sym_ntos __sym_ntos
|
|
|
|
#define sym_ston __sym_ston
|
|
|
|
#define res_nopt __res_nopt
|
2008-12-14 19:39:53 +00:00
|
|
|
#define res_nopt_rdata __res_nopt_rdata
|
Update the resolver in libc to BIND9's one.
Since, res_sendsigned(3) and the friends use MD5 functions, it is
hard to include them without having MD5 functions in libc. So,
res_sendsigned(3) is not merged into libc.
Since, res_update(3) in BIND9 is not binary compatible with our
res_update(3), res_update(3) is leaved as is, except some
necessary modifications.
The res_update(3) and the friends are not essential part of the
resolver. They are not defined in resolv.h but defined in
res_update.h separately in BIND9. Further, they are not called from
our tree. So, I hide them from our resolv.h, but leave them only
for binary backward compatibility (perhaps, no one calls them).
Since, struct __res_state_ext is not exposed in BIND9, I hide it
from our resolv.h. And, global variable _res_ext is removed. It
breaks binary backward compatibility. But, since it is not used from
outside of our libc, I think it is safe.
Reviewed by: arch@ (no objection)
2006-03-21 16:11:11 +00:00
|
|
|
#define res_ndestroy __res_ndestroy
|
|
|
|
#define res_nametoclass __res_nametoclass
|
|
|
|
#define res_nametotype __res_nametotype
|
|
|
|
#define res_setservers __res_setservers
|
|
|
|
#define res_getservers __res_getservers
|
2006-05-13 12:43:12 +00:00
|
|
|
#if 0
|
Update the resolver in libc to BIND9's one.
Since, res_sendsigned(3) and the friends use MD5 functions, it is
hard to include them without having MD5 functions in libc. So,
res_sendsigned(3) is not merged into libc.
Since, res_update(3) in BIND9 is not binary compatible with our
res_update(3), res_update(3) is leaved as is, except some
necessary modifications.
The res_update(3) and the friends are not essential part of the
resolver. They are not defined in resolv.h but defined in
res_update.h separately in BIND9. Further, they are not called from
our tree. So, I hide them from our resolv.h, but leave them only
for binary backward compatibility (perhaps, no one calls them).
Since, struct __res_state_ext is not exposed in BIND9, I hide it
from our resolv.h. And, global variable _res_ext is removed. It
breaks binary backward compatibility. But, since it is not used from
outside of our libc, I think it is safe.
Reviewed by: arch@ (no objection)
2006-03-21 16:11:11 +00:00
|
|
|
#define res_buildprotolist __res_buildprotolist
|
|
|
|
#define res_destroyprotolist __res_destroyprotolist
|
|
|
|
#define res_destroyservicelist __res_destroyservicelist
|
|
|
|
#define res_get_nibblesuffix __res_get_nibblesuffix
|
|
|
|
#define res_get_nibblesuffix2 __res_get_nibblesuffix2
|
|
|
|
#endif
|
|
|
|
#define res_ourserver_p __res_ourserver_p
|
2006-05-13 12:43:12 +00:00
|
|
|
#if 0
|
Update the resolver in libc to BIND9's one.
Since, res_sendsigned(3) and the friends use MD5 functions, it is
hard to include them without having MD5 functions in libc. So,
res_sendsigned(3) is not merged into libc.
Since, res_update(3) in BIND9 is not binary compatible with our
res_update(3), res_update(3) is leaved as is, except some
necessary modifications.
The res_update(3) and the friends are not essential part of the
resolver. They are not defined in resolv.h but defined in
res_update.h separately in BIND9. Further, they are not called from
our tree. So, I hide them from our resolv.h, but leave them only
for binary backward compatibility (perhaps, no one calls them).
Since, struct __res_state_ext is not exposed in BIND9, I hide it
from our resolv.h. And, global variable _res_ext is removed. It
breaks binary backward compatibility. But, since it is not used from
outside of our libc, I think it is safe.
Reviewed by: arch@ (no objection)
2006-03-21 16:11:11 +00:00
|
|
|
#define res_protocolname __res_protocolname
|
|
|
|
#define res_protocolnumber __res_protocolnumber
|
2006-05-13 12:43:12 +00:00
|
|
|
#endif
|
Update the resolver in libc to BIND9's one.
Since, res_sendsigned(3) and the friends use MD5 functions, it is
hard to include them without having MD5 functions in libc. So,
res_sendsigned(3) is not merged into libc.
Since, res_update(3) in BIND9 is not binary compatible with our
res_update(3), res_update(3) is leaved as is, except some
necessary modifications.
The res_update(3) and the friends are not essential part of the
resolver. They are not defined in resolv.h but defined in
res_update.h separately in BIND9. Further, they are not called from
our tree. So, I hide them from our resolv.h, but leave them only
for binary backward compatibility (perhaps, no one calls them).
Since, struct __res_state_ext is not exposed in BIND9, I hide it
from our resolv.h. And, global variable _res_ext is removed. It
breaks binary backward compatibility. But, since it is not used from
outside of our libc, I think it is safe.
Reviewed by: arch@ (no objection)
2006-03-21 16:11:11 +00:00
|
|
|
#define res_send_setqhook __res_send_setqhook
|
|
|
|
#define res_send_setrhook __res_send_setrhook
|
2006-05-13 12:43:12 +00:00
|
|
|
#if 0
|
Update the resolver in libc to BIND9's one.
Since, res_sendsigned(3) and the friends use MD5 functions, it is
hard to include them without having MD5 functions in libc. So,
res_sendsigned(3) is not merged into libc.
Since, res_update(3) in BIND9 is not binary compatible with our
res_update(3), res_update(3) is leaved as is, except some
necessary modifications.
The res_update(3) and the friends are not essential part of the
resolver. They are not defined in resolv.h but defined in
res_update.h separately in BIND9. Further, they are not called from
our tree. So, I hide them from our resolv.h, but leave them only
for binary backward compatibility (perhaps, no one calls them).
Since, struct __res_state_ext is not exposed in BIND9, I hide it
from our resolv.h. And, global variable _res_ext is removed. It
breaks binary backward compatibility. But, since it is not used from
outside of our libc, I think it is safe.
Reviewed by: arch@ (no objection)
2006-03-21 16:11:11 +00:00
|
|
|
#define res_servicename __res_servicename
|
|
|
|
#define res_servicenumber __res_servicenumber
|
2006-05-13 12:43:12 +00:00
|
|
|
#endif
|
1994-05-24 09:57:34 +00:00
|
|
|
__BEGIN_DECLS
|
2002-03-23 17:24:55 +00:00
|
|
|
int res_hnok(const char *);
|
|
|
|
int res_ownok(const char *);
|
|
|
|
int res_mailok(const char *);
|
|
|
|
int res_dnok(const char *);
|
|
|
|
int sym_ston(const struct res_sym *, const char *, int *);
|
|
|
|
const char * sym_ntos(const struct res_sym *, int, int *);
|
|
|
|
const char * sym_ntop(const struct res_sym *, int, int *);
|
|
|
|
int b64_ntop(u_char const *, size_t, char *, size_t);
|
|
|
|
int b64_pton(char const *, u_char *, size_t);
|
|
|
|
int loc_aton(const char *, u_char *);
|
|
|
|
const char * loc_ntoa(const u_char *, char *);
|
|
|
|
int dn_skipname(const u_char *, const u_char *);
|
|
|
|
void putlong(u_int32_t, u_char *);
|
|
|
|
void putshort(u_int16_t, u_char *);
|
Update the resolver in libc to BIND9's one.
Since, res_sendsigned(3) and the friends use MD5 functions, it is
hard to include them without having MD5 functions in libc. So,
res_sendsigned(3) is not merged into libc.
Since, res_update(3) in BIND9 is not binary compatible with our
res_update(3), res_update(3) is leaved as is, except some
necessary modifications.
The res_update(3) and the friends are not essential part of the
resolver. They are not defined in resolv.h but defined in
res_update.h separately in BIND9. Further, they are not called from
our tree. So, I hide them from our resolv.h, but leave them only
for binary backward compatibility (perhaps, no one calls them).
Since, struct __res_state_ext is not exposed in BIND9, I hide it
from our resolv.h. And, global variable _res_ext is removed. It
breaks binary backward compatibility. But, since it is not used from
outside of our libc, I think it is safe.
Reviewed by: arch@ (no objection)
2006-03-21 16:11:11 +00:00
|
|
|
#ifndef __ultrix__
|
|
|
|
u_int16_t _getshort(const u_char *);
|
|
|
|
u_int32_t _getlong(const u_char *);
|
|
|
|
#endif
|
2002-03-23 17:24:55 +00:00
|
|
|
const char * p_class(int);
|
|
|
|
const char * p_time(u_int32_t);
|
|
|
|
const char * p_type(int);
|
Update the resolver in libc to BIND9's one.
Since, res_sendsigned(3) and the friends use MD5 functions, it is
hard to include them without having MD5 functions in libc. So,
res_sendsigned(3) is not merged into libc.
Since, res_update(3) in BIND9 is not binary compatible with our
res_update(3), res_update(3) is leaved as is, except some
necessary modifications.
The res_update(3) and the friends are not essential part of the
resolver. They are not defined in resolv.h but defined in
res_update.h separately in BIND9. Further, they are not called from
our tree. So, I hide them from our resolv.h, but leave them only
for binary backward compatibility (perhaps, no one calls them).
Since, struct __res_state_ext is not exposed in BIND9, I hide it
from our resolv.h. And, global variable _res_ext is removed. It
breaks binary backward compatibility. But, since it is not used from
outside of our libc, I think it is safe.
Reviewed by: arch@ (no objection)
2006-03-21 16:11:11 +00:00
|
|
|
const char * p_rcode(int);
|
|
|
|
const char * p_sockun(union res_sockaddr_union, char *, size_t);
|
2002-03-23 17:24:55 +00:00
|
|
|
const u_char * p_cdnname(const u_char *, const u_char *, int, FILE *);
|
|
|
|
const u_char * p_cdname(const u_char *, const u_char *, FILE *);
|
Update the resolver in libc to BIND9's one.
Since, res_sendsigned(3) and the friends use MD5 functions, it is
hard to include them without having MD5 functions in libc. So,
res_sendsigned(3) is not merged into libc.
Since, res_update(3) in BIND9 is not binary compatible with our
res_update(3), res_update(3) is leaved as is, except some
necessary modifications.
The res_update(3) and the friends are not essential part of the
resolver. They are not defined in resolv.h but defined in
res_update.h separately in BIND9. Further, they are not called from
our tree. So, I hide them from our resolv.h, but leave them only
for binary backward compatibility (perhaps, no one calls them).
Since, struct __res_state_ext is not exposed in BIND9, I hide it
from our resolv.h. And, global variable _res_ext is removed. It
breaks binary backward compatibility. But, since it is not used from
outside of our libc, I think it is safe.
Reviewed by: arch@ (no objection)
2006-03-21 16:11:11 +00:00
|
|
|
const u_char * p_fqnname(const u_char *, const u_char *, int, char *, int);
|
2002-03-23 17:24:55 +00:00
|
|
|
const u_char * p_fqname(const u_char *, const u_char *, FILE *);
|
|
|
|
const char * p_option(u_long);
|
|
|
|
char * p_secstodate(u_long);
|
|
|
|
int dn_count_labels(const char *);
|
|
|
|
int dn_comp(const char *, u_char *, int, u_char **, u_char **);
|
|
|
|
int dn_expand(const u_char *, const u_char *, const u_char *,
|
|
|
|
char *, int);
|
2014-08-12 12:36:06 +00:00
|
|
|
void res_rndinit(res_state);
|
2002-03-23 17:24:55 +00:00
|
|
|
u_int res_randomid(void);
|
2014-08-12 12:36:06 +00:00
|
|
|
u_int res_nrandomid(res_state);
|
Update the resolver in libc to BIND9's one.
Since, res_sendsigned(3) and the friends use MD5 functions, it is
hard to include them without having MD5 functions in libc. So,
res_sendsigned(3) is not merged into libc.
Since, res_update(3) in BIND9 is not binary compatible with our
res_update(3), res_update(3) is leaved as is, except some
necessary modifications.
The res_update(3) and the friends are not essential part of the
resolver. They are not defined in resolv.h but defined in
res_update.h separately in BIND9. Further, they are not called from
our tree. So, I hide them from our resolv.h, but leave them only
for binary backward compatibility (perhaps, no one calls them).
Since, struct __res_state_ext is not exposed in BIND9, I hide it
from our resolv.h. And, global variable _res_ext is removed. It
breaks binary backward compatibility. But, since it is not used from
outside of our libc, I think it is safe.
Reviewed by: arch@ (no objection)
2006-03-21 16:11:11 +00:00
|
|
|
int res_nameinquery(const char *, int, int, const u_char *,
|
|
|
|
const u_char *);
|
2002-03-23 17:24:55 +00:00
|
|
|
int res_queriesmatch(const u_char *, const u_char *,
|
|
|
|
const u_char *, const u_char *);
|
|
|
|
const char * p_section(int, int);
|
Update the resolver in libc to BIND9's one.
Since, res_sendsigned(3) and the friends use MD5 functions, it is
hard to include them without having MD5 functions in libc. So,
res_sendsigned(3) is not merged into libc.
Since, res_update(3) in BIND9 is not binary compatible with our
res_update(3), res_update(3) is leaved as is, except some
necessary modifications.
The res_update(3) and the friends are not essential part of the
resolver. They are not defined in resolv.h but defined in
res_update.h separately in BIND9. Further, they are not called from
our tree. So, I hide them from our resolv.h, but leave them only
for binary backward compatibility (perhaps, no one calls them).
Since, struct __res_state_ext is not exposed in BIND9, I hide it
from our resolv.h. And, global variable _res_ext is removed. It
breaks binary backward compatibility. But, since it is not used from
outside of our libc, I think it is safe.
Reviewed by: arch@ (no objection)
2006-03-21 16:11:11 +00:00
|
|
|
/* Things involving a resolver context. */
|
|
|
|
int res_ninit(res_state);
|
|
|
|
int res_nisourserver(const res_state, const struct sockaddr_in *);
|
|
|
|
void fp_resstat(const res_state, FILE *);
|
|
|
|
void res_pquery(const res_state, const u_char *, int, FILE *);
|
|
|
|
const char * res_hostalias(const res_state, const char *, char *, size_t);
|
|
|
|
int res_nquery(res_state, const char *, int, int, u_char *, int);
|
|
|
|
int res_nsearch(res_state, const char *, int, int, u_char *, int);
|
|
|
|
int res_nquerydomain(res_state, const char *, const char *,
|
|
|
|
int, int, u_char *, int);
|
|
|
|
int res_nmkquery(res_state, int, const char *, int, int,
|
|
|
|
const u_char *, int, const u_char *,
|
|
|
|
u_char *, int);
|
|
|
|
int res_nsend(res_state, const u_char *, int, u_char *, int);
|
|
|
|
#if 0
|
|
|
|
int res_nsendsigned(res_state, const u_char *, int,
|
|
|
|
ns_tsig_key *, u_char *, int);
|
|
|
|
int res_findzonecut(res_state, const char *, ns_class, int,
|
|
|
|
char *, size_t, struct in_addr *, int);
|
2006-05-21 11:19:36 +00:00
|
|
|
#endif
|
Update the resolver in libc to BIND9's one.
Since, res_sendsigned(3) and the friends use MD5 functions, it is
hard to include them without having MD5 functions in libc. So,
res_sendsigned(3) is not merged into libc.
Since, res_update(3) in BIND9 is not binary compatible with our
res_update(3), res_update(3) is leaved as is, except some
necessary modifications.
The res_update(3) and the friends are not essential part of the
resolver. They are not defined in resolv.h but defined in
res_update.h separately in BIND9. Further, they are not called from
our tree. So, I hide them from our resolv.h, but leave them only
for binary backward compatibility (perhaps, no one calls them).
Since, struct __res_state_ext is not exposed in BIND9, I hide it
from our resolv.h. And, global variable _res_ext is removed. It
breaks binary backward compatibility. But, since it is not used from
outside of our libc, I think it is safe.
Reviewed by: arch@ (no objection)
2006-03-21 16:11:11 +00:00
|
|
|
int res_findzonecut2(res_state, const char *, ns_class, int,
|
|
|
|
char *, size_t,
|
|
|
|
union res_sockaddr_union *, int);
|
|
|
|
void res_nclose(res_state);
|
|
|
|
int res_nopt(res_state, int, u_char *, int, int);
|
2008-12-14 19:39:53 +00:00
|
|
|
int res_nopt_rdata(res_state, int, u_char *, int, u_char *,
|
|
|
|
u_short, u_short, u_char *);
|
Update the resolver in libc to BIND9's one.
Since, res_sendsigned(3) and the friends use MD5 functions, it is
hard to include them without having MD5 functions in libc. So,
res_sendsigned(3) is not merged into libc.
Since, res_update(3) in BIND9 is not binary compatible with our
res_update(3), res_update(3) is leaved as is, except some
necessary modifications.
The res_update(3) and the friends are not essential part of the
resolver. They are not defined in resolv.h but defined in
res_update.h separately in BIND9. Further, they are not called from
our tree. So, I hide them from our resolv.h, but leave them only
for binary backward compatibility (perhaps, no one calls them).
Since, struct __res_state_ext is not exposed in BIND9, I hide it
from our resolv.h. And, global variable _res_ext is removed. It
breaks binary backward compatibility. But, since it is not used from
outside of our libc, I think it is safe.
Reviewed by: arch@ (no objection)
2006-03-21 16:11:11 +00:00
|
|
|
void res_send_setqhook(res_send_qhook);
|
|
|
|
void res_send_setrhook(res_send_rhook);
|
|
|
|
int __res_vinit(res_state, int);
|
2006-05-13 12:43:12 +00:00
|
|
|
#if 0
|
Update the resolver in libc to BIND9's one.
Since, res_sendsigned(3) and the friends use MD5 functions, it is
hard to include them without having MD5 functions in libc. So,
res_sendsigned(3) is not merged into libc.
Since, res_update(3) in BIND9 is not binary compatible with our
res_update(3), res_update(3) is leaved as is, except some
necessary modifications.
The res_update(3) and the friends are not essential part of the
resolver. They are not defined in resolv.h but defined in
res_update.h separately in BIND9. Further, they are not called from
our tree. So, I hide them from our resolv.h, but leave them only
for binary backward compatibility (perhaps, no one calls them).
Since, struct __res_state_ext is not exposed in BIND9, I hide it
from our resolv.h. And, global variable _res_ext is removed. It
breaks binary backward compatibility. But, since it is not used from
outside of our libc, I think it is safe.
Reviewed by: arch@ (no objection)
2006-03-21 16:11:11 +00:00
|
|
|
void res_destroyservicelist(void);
|
|
|
|
const char * res_servicename(u_int16_t, const char *);
|
|
|
|
const char * res_protocolname(int);
|
|
|
|
void res_destroyprotolist(void);
|
|
|
|
void res_buildprotolist(void);
|
|
|
|
const char * res_get_nibblesuffix(res_state);
|
|
|
|
const char * res_get_nibblesuffix2(res_state);
|
1998-06-11 12:52:45 +00:00
|
|
|
#endif
|
Update the resolver in libc to BIND9's one.
Since, res_sendsigned(3) and the friends use MD5 functions, it is
hard to include them without having MD5 functions in libc. So,
res_sendsigned(3) is not merged into libc.
Since, res_update(3) in BIND9 is not binary compatible with our
res_update(3), res_update(3) is leaved as is, except some
necessary modifications.
The res_update(3) and the friends are not essential part of the
resolver. They are not defined in resolv.h but defined in
res_update.h separately in BIND9. Further, they are not called from
our tree. So, I hide them from our resolv.h, but leave them only
for binary backward compatibility (perhaps, no one calls them).
Since, struct __res_state_ext is not exposed in BIND9, I hide it
from our resolv.h. And, global variable _res_ext is removed. It
breaks binary backward compatibility. But, since it is not used from
outside of our libc, I think it is safe.
Reviewed by: arch@ (no objection)
2006-03-21 16:11:11 +00:00
|
|
|
void res_ndestroy(res_state);
|
|
|
|
u_int16_t res_nametoclass(const char *, int *);
|
|
|
|
u_int16_t res_nametotype(const char *, int *);
|
|
|
|
void res_setservers(res_state, const union res_sockaddr_union *,
|
|
|
|
int);
|
|
|
|
int res_getservers(res_state, union res_sockaddr_union *, int);
|
1994-05-24 09:57:34 +00:00
|
|
|
__END_DECLS
|
|
|
|
|
|
|
|
#endif /* !_RESOLV_H_ */
|
2007-06-03 17:20:27 +00:00
|
|
|
/*! \file */
|