Also, the bit library is also required. If you're using LuaJIT 2.0 with ngx_lua, then the bit library is already available by default.
Note that, this library is bundled and enabled by default in the OpenResty bundle.
IMPORTANT: to be able to generate unique ids, the random generator must be properly seeded using math.randomseed prior to using this module.
Synopsis
lua_package_path"/path/to/lua-resty-dns/lib/?.lua;;";
server {
location= /dns {
content_by_lua_block {
local resolver = require "resty.dns.resolver"local r, err = resolver:new{
nameservers = {"8.8.8.8", {"8.8.4.4", 53} },
retrans = 5, -- 5 retransmissions on receive timeout
timeout = 2000, -- 2 sec
no_random = true, -- always start with first nameserver
}
if not r then
ngx.say("failed to instantiate the resolver: ", err) return end local answers, err, tries = r:query("www.google.com", nil, {}) if not answers then ngx.say("failed to query the DNS server: ", err) ngx.say("retry historie:\n ", table.concat(tries, "\n ")) return end if answers.errcode then ngx.say("server returned error code: ", answers.errcode, ": ", answers.errstr) end for i, ans in ipairs(answers) do ngx.say(ans.name, "", ans.address or ans.cname, " type:", ans.type, " class:", ans.class, " ttl:", ans.ttl) end } }}
Creates a dns.resolver object. Returns nil and a message string on error.
It accepts a opts table argument. The following options are supported:
nameservers
a list of nameservers to be used. Each nameserver entry can be either a single hostname string or a table holding both the hostname string and the port number. The nameserver is picked up by a simple round-robin algorithm for each query method call. This option is required.
retrans
the total number of times of retransmitting the DNS request when receiving a DNS response times out according to the timeout setting. Defaults to 5 times. When trying to retransmit the query, the next nameserver according to the round-robin algorithm will be picked up.
timeout
the time in milliseconds for waiting for the response for a single attempt of request transmission. note that this is ''not'' the maximal total waiting time before giving up, the maximal total waiting time can be calculated by the expression timeout x retrans. The timeout setting can also be changed by calling the set_timeout method. The default timeout setting is 2000 milliseconds, or 2 seconds.
no_recurse
a boolean flag controls whether to disable the "recursion desired" (RD) flag in the UDP request. Defaults to false.
no_random
a boolean flag controls whether to randomly pick the nameserver to query first, if true will always start with the first nameserver listed. Defaults to false.
Performs a DNS standard query to the nameservers specified by the new method,
and returns all the answer records in an array-like Lua table. In case of errors, it will
return nil and a string describing the error instead.
If the server returns a non-zero error code, the fields errcode and errstr will be set accordingly in the Lua table returned.
Each entry in the answers returned table value is also a hash-like Lua table
which usually takes some of the following fields:
name
The resource record name.
type
The current resource record type, possible values are 1 (TYPE_A), 5 (TYPE_CNAME), 28 (TYPE_AAAA), and any other values allowed by RFC 1035.
address
The IPv4 or IPv6 address in their textual representations when the resource record type is either 1 (TYPE_A) or 28 (TYPE_AAAA), respectively. Successive 16-bit zero groups in IPv6 addresses will not be compressed by default, if you want that, you need to call the compress_ipv6_addr static method instead.
section
The identifier of the section that the current answer record belongs to. Possible values are 1 (SECTION_AN), 2 (SECTION_NS), and 3 (SECTION_AR).
cname
The (decoded) record data value for CNAME resource records. Only present for CNAME records.
ttl
The time-to-live (TTL) value in seconds for the current resource record.
class
The current resource record class, possible values are 1 (CLASS_IN) or any other values allowed by RFC 1035.
preference
The preference integer number for MX resource records. Only present for MX type records.
exchange
The exchange domain name for MX resource records. Only present for MX type records.
nsdname
A domain-name which specifies a host which should be authoritative for the specified class and domain. Usually present for NS type records.
rdata
The raw resource data (RDATA) for resource records that are not recognized.
txt
The record value for TXT records. When there is only one character string in this record, then this field takes a single Lua string. Otherwise this field takes a Lua table holding all the strings.
ptrdname
The record value for PTR records.
This method also takes an optional options argument table, which takes the following fields:
qtype
The type of the question. Possible values are 1 (TYPE_A), 5 (TYPE_CNAME), 28 (TYPE_AAAA), or any other QTYPE value specified by RFC 1035 and RFC 3596. Default to 1 (TYPE_A).
authority_section
When set to a true value, the answers return value includes the Authority section of the DNS response. Default to false.
additional_section
When set to a true value, the answers return value includes the Additional section of the DNS response. Default to false.
The optional parameter tries can be provided as an empty table, and will be
returned as a third result. The table will be an array with the error message
for each (if any) failed try.
When data truncation happens, the resolver will automatically retry using the TCP transport mode
to query the current nameserver. All TCP connections are short lived.
Performs a PTR lookup for both IPv4 and IPv6 addresses. This function is basically a wrapper for the query command
which uses the arpa_str command to convert the IP address on the fly.
By default, the underlying ngx_lua module
does error logging when socket errors happen. If you are already doing proper error
handling in your own Lua code, then you are recommended to disable this automatic error logging by turning off ngx_lua's lua_socket_log_errors directive, that is,
This library cannot be used in code contexts like set_by_lua*, log_by_lua*, and
header_filter_by_lua* where the ngx_lua cosocket API is not available.
The resty.dns.resolver object instance cannot be stored in a Lua variable at the Lua module level,
because it will then be shared by all the concurrent requests handled by the same nginx
worker process (see
https://github.com/openresty/lua-nginx-module/#data-sharing-within-an-nginx-worker ) and
result in bad race conditions when concurrent requests are trying to use the same resty.dns.resolver instance.
You should always initiate resty.dns.resolver objects in function local
variables or in the ngx.ctx table. These places all have their own data copies for
each request.
Copyright (C) 2012-2019, by Yichun "agentzh" Zhang (章亦春) [email protected], OpenResty Inc.
All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
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.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.
请发表评论