|
|
|
.\"
|
|
|
|
.\" Copyright 1998 by the Massachusetts Institute of Technology.
|
|
|
|
.\" SPDX-License-Identifier: MIT
|
|
|
|
.\"
|
|
|
|
.TH ARES_SEARCH 3 "24 July 1998"
|
|
|
|
.SH NAME
|
|
|
|
ares_search \- Initiate a DNS query with domain search
|
|
|
|
.SH SYNOPSIS
|
|
|
|
.nf
|
|
|
|
#include <ares.h>
|
|
|
|
|
|
|
|
typedef void (*ares_callback)(void *\fIarg\fP, int \fIstatus\fP,
|
|
|
|
int \fItimeouts\fP, unsigned char *\fIabuf\fP,
|
|
|
|
int \fIalen\fP)
|
|
|
|
|
`ares_channel` -> `ares_channel_t *`: don't bury the pointer (#595)
`ares_channel` is defined as `typedef struct ares_channeldata *ares_channel;`. The problem with this, is it embeds the pointer into the typedef, which means an `ares_channel` can never be declared as `const` as if you write `const ares_channel channel`, that expands to `struct ares_channeldata * const ares_channel` and not `const struct ares_channeldata *channel`.
We will now typedef `ares_channel_t` as `typedef struct ares_channeldata ares_channel_t;`, so if you write `const ares_channel_t *channel`, it properly expands to `const struct ares_channeldata *channel`.
We are maintaining the old typedef for API compatibility with existing integrations, and due to typedef expansion this should not even cause any compiler warnings for existing code. There are no ABI implications with this change. I could be convinced to keep existing public functions as `ares_channel` if a sufficient argument exists, but internally we really need make this change for modern best practices.
This change will allow us to internally use `const ares_channel_t *` where appropriate. Whether or not we decide to change any public interfaces to use `const` may require further discussion on if there might be ABI implications (I don't think so, but I'm also not 100% sure what a compiler internally does with `const` when emitting machine code ... I think more likely ABI implications would occur going the opposite direction).
FYI, This PR was done via a combination of sed and clang-format, the only manual code change was the addition of the new typedef, and a couple doc fixes :)
Fix By: Brad House (@bradh352)
1 year ago
|
|
|
void ares_search(ares_channel_t *\fIchannel\fP, const char *\fIname\fP,
|
|
|
|
int \fIdnsclass\fP, int \fItype\fP,
|
|
|
|
ares_callback \fIcallback\fP, void *\fIarg\fP)
|
|
|
|
.fi
|
|
|
|
.SH DESCRIPTION
|
|
|
|
The
|
|
|
|
.B ares_search
|
|
|
|
function initiates a series of single-question DNS queries on the name
|
|
|
|
service channel identified by
|
|
|
|
.IR channel ,
|
|
|
|
using the channel's search domains as well as a host alias file given
|
|
|
|
by the HOSTALIAS environment variable. The parameter
|
|
|
|
.I name
|
|
|
|
gives the alias name or the base of the query name as a NUL-terminated
|
|
|
|
C string of period-separated labels; if it ends with a period, the
|
|
|
|
channel's search domains will not be used. Periods and backslashes
|
|
|
|
within a label must be escaped with a backslash. The parameters
|
|
|
|
.I dnsclass
|
|
|
|
and
|
|
|
|
.I type
|
|
|
|
give the class and type of the query using the values defined in
|
|
|
|
.BR <arpa/nameser.h> .
|
|
|
|
When the query sequence is complete or has failed, the ares library
|
|
|
|
will invoke
|
|
|
|
.IR callback .
|
|
|
|
Completion or failure of the query sequence may happen immediately, or
|
|
|
|
may happen during a later call to
|
|
|
|
.BR ares_process (3)
|
|
|
|
or
|
|
|
|
.BR ares_destroy (3).
|
|
|
|
.PP
|
|
|
|
If this is called from a thread other than which the main program event loop is
|
|
|
|
running, care needs to be taken to ensure any file descriptor lists are updated
|
|
|
|
immediately within the eventloop. When the associated callback is called,
|
|
|
|
it is called with a channel lock so care must be taken to ensure any processing
|
|
|
|
is minimal to prevent DNS channel stalls.
|
|
|
|
.PP
|
|
|
|
The callback argument
|
|
|
|
.I arg
|
|
|
|
is copied from the
|
|
|
|
.B ares_search
|
|
|
|
argument
|
|
|
|
.IR arg .
|
|
|
|
The callback argument
|
|
|
|
.I status
|
|
|
|
indicates whether the query sequence ended with a successful query
|
|
|
|
and, if not, how the query sequence failed. It may have any of the
|
|
|
|
following values:
|
|
|
|
.TP 19
|
|
|
|
.B ARES_SUCCESS
|
|
|
|
A query completed successfully.
|
|
|
|
.TP 19
|
|
|
|
.B ARES_ENODATA
|
|
|
|
No query completed successfully; when the query was tried without a
|
|
|
|
search domain appended, a response was returned with no answers.
|
|
|
|
.TP 19
|
|
|
|
.B ARES_EFORMERR
|
|
|
|
A query completed but the server claimed that the query was
|
|
|
|
malformatted.
|
|
|
|
.TP 19
|
|
|
|
.B ARES_ESERVFAIL
|
|
|
|
No query completed successfully; when the query was tried without a
|
|
|
|
search domain appended, the server claimed to have experienced a
|
|
|
|
failure. (This code can only occur if the
|
|
|
|
.B ARES_FLAG_NOCHECKRESP
|
|
|
|
flag was specified at channel initialization time; otherwise, such
|
|
|
|
responses are ignored at the
|
|
|
|
.BR ares_send (3)
|
|
|
|
level.)
|
|
|
|
.TP 19
|
|
|
|
.B ARES_ENOTFOUND
|
|
|
|
No query completed successfully; when the query was tried without a
|
|
|
|
search domain appended, the server reported that the queried-for
|
|
|
|
domain name was not found.
|
|
|
|
.TP 19
|
|
|
|
.B ARES_ENOTIMP
|
|
|
|
A query completed but the server does not implement the operation
|
|
|
|
requested by the query. (This code can only occur if the
|
|
|
|
.B ARES_FLAG_NOCHECKRESP
|
|
|
|
flag was specified at channel initialization time; otherwise, such
|
|
|
|
responses are ignored at the
|
|
|
|
.BR ares_send (3)
|
|
|
|
level.)
|
|
|
|
.TP 19
|
|
|
|
.B ARES_EREFUSED
|
|
|
|
A query completed but the server refused the query. (This code can
|
|
|
|
only occur returned if the
|
|
|
|
.B ARES_FLAG_NOCHECKRESP
|
|
|
|
flag was specified at channel initialization time; otherwise, such
|
|
|
|
responses are ignored at the
|
|
|
|
.BR ares_send (3)
|
|
|
|
level.)
|
|
|
|
.TP 19
|
|
|
|
.B ARES_TIMEOUT
|
|
|
|
No name servers responded to a query within the timeout period.
|
|
|
|
.TP 19
|
|
|
|
.B ARES_ECONNREFUSED
|
|
|
|
No name servers could be contacted.
|
|
|
|
.TP 19
|
|
|
|
.B ARES_ENOMEM
|
|
|
|
Memory was exhausted.
|
|
|
|
.TP 19
|
|
|
|
.B ARES_ECANCELLED
|
|
|
|
The query was cancelled.
|
|
|
|
.TP 19
|
|
|
|
.B ARES_EDESTRUCTION
|
|
|
|
The name service channel
|
|
|
|
.I channel
|
|
|
|
is being destroyed; the query will not be completed.
|
Add flag to not use a default local named server on channel initialization (#713)
Hello, I work on an application for Microsoft which uses c-ares to
perform DNS lookups. We have made some minor changes to the library over
time, and would like to contribute these back to the project in case
they are useful more widely. This PR adds a new channel init flag,
described below.
Please let me know if I can include any more information to make this PR
better/easier for you to review. Thanks!
**Summary**
When initializing a channel with `ares_init_options()`, if there are no
nameservers available (because `ARES_OPT_SERVERS` is not used and
`/etc/resolv.conf` is either empty or not available) then a default
local named server will be added to the channel.
However in some applications a local named server will never be
available. In this case, all subsequent queries on the channel will
fail.
If we know this ahead of time, then it may be preferred to fail channel
initialization directly rather than wait for the queries to fail. This
gives better visibility, since we know that the failure is due to
missing servers rather than something going wrong with the queries.
This PR adds a new flag `ARES_FLAG_NO_DFLT_SVR`, to indicate that a
default local named server should not be added to a channel in this
scenario. Instead, a new error `ARES_EINITNOSERVER` is returned and
initialization fails.
**Testing**
I have added 2 new FV tests:
- `ContainerNoDfltSvrEmptyInit` to test that initialization fails when
no nameservers are available and the flag is set.
- `ContainerNoDfltSvrFullInit` to test that initialization still
succeeds when the flag is set but other nameservers are available.
Existing FVs are all passing.
**Documentation**
I have had a go at manually updating the docs to describe the new
flag/error, but couldn't see any contributing guidance about testing
this. Please let me know if you'd like anything more here.
---------
Fix By: Oliver Welsh (@oliverwelsh)
9 months ago
|
|
|
.TP 19
|
|
|
|
.B ARES_ENOSERVER
|
|
|
|
No query completed successfully; no DNS servers were configured on the channel.
|
|
|
|
.PP
|
|
|
|
The callback argument
|
|
|
|
.I timeouts
|
|
|
|
reports how many times a query timed out during the execution of the
|
|
|
|
given request.
|
|
|
|
.PP
|
|
|
|
If a query completed successfully, the callback argument
|
|
|
|
.I abuf
|
|
|
|
points to a result buffer of length
|
|
|
|
.IR alen .
|
|
|
|
If the query did not complete successfully,
|
|
|
|
.I abuf
|
|
|
|
will usually be NULL and
|
|
|
|
.I alen
|
|
|
|
will usually be 0, but in some cases an unsuccessful query result may
|
|
|
|
be placed in
|
|
|
|
.IR abuf .
|
|
|
|
.SH SEE ALSO
|
|
|
|
.BR ares_process (3),
|
|
|
|
.BR ares_dns_record (3)
|
|
|
|
.SH AUTHOR
|
|
|
|
Greg Hudson, MIT Information Systems
|
|
|
|
.br
|
|
|
|
Copyright 1998 by the Massachusetts Institute of Technology.
|