1 .\" dnsget.1: dnsget manpage
3 .\" Copyright (C) 2005-2014 Michael Tokarev <mjt+udns@tls.msk.ru>
4 .\" This file is part of UDNS library, an async DNS stub resolver.
6 .\" This library is free software; you can redistribute it and/or
7 .\" modify it under the terms of the GNU Lesser General Public
8 .\" License as published by the Free Software Foundation; either
9 .\" version 2.1 of the License, or (at your option) any later version.
11 .\" This library is distributed in the hope that it will be useful,
12 .\" but WITHOUT ANY WARRANTY; without even the implied warranty of
13 .\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
14 .\" Lesser General Public License for more details.
16 .\" You should have received a copy of the GNU Lesser General Public
17 .\" License along with this library, in file named COPYING.LGPL; if not,
18 .\" write to the Free Software Foundation, Inc., 59 Temple Place,
19 .\" Suite 330, Boston, MA 02111-1307 USA
21 .TH dnsget 1 "Jan 2014" "User Utilities"
24 dnsget \- DNS lookup utility
28 .RB [\| \-v \||\| \-q \|]
39 is a simple command-line to perform DNS lookups, similar to
43 It is useable for both interactive/debugging scenarious and
45 The program is implemented using
52 produces a human-readable output, similar to
55 alias.example.com. CNAME www.example.com.
56 www.example.com. A 192.168.1.1
57 www.example.com. MX 10 mx.example.com.
60 which is just sufficient to see how a given name resolves.
61 Output format is controllable with
65 options -- the former increases verbosity level up to printing
66 the whole DNS contents of all packets sent and received, which
67 is suitable for debugging DNS problems, while the latter reduces
68 the level, making output more quiet, up to bare result with no
69 error messages, which is good for scripts.
73 The following options are recognized by
78 produce more detailed output. More
80 means more details will be produced. With single
82 will print contents of all received DNS packets (in a readable format),
85 it will output all outgoing DNS packets too.
89 the opposite for \fB\-v\fR -- produce less detailed output.
92 will only show (decoded) data from final DNS resource records (RR),
95 also suppresses error messages.
99 request record(s) of the given type \fItype\fR. By default,
101 will ask for IPv4 address (A) record, or for PTR record if the
102 argument in question is an IPv4 or IPv6 address. Recognized
103 types include A, AAAA, MX, TXT, CNAME, PTR, NS, SOA, ANY and
108 request DNS record(s) of the given class \fIclass\fR. By
111 uses IN class. Valid classes include IN, CH, HS, ANY.
115 (compatibility option). Equivalent to setting query type to
117 and increasing verbosity level
129 \fB\-o \fIopt\fR,\fIopt\fR,...
130 (may be specified several times).
131 Set resolver options (in a form \fIoption\fR:\fIvalue\fR) as if they
134 environment variable, or set query flags:
137 \fBtimeout\fR:\fIsec\fR
138 Set initial query timeout to \fIsec\fR.
140 \fBattempts\fR:\fInum\fR
141 (re)try every query \fInum\fR times before failing.
143 \fBudpbuf\fR:\fIbytes\fR
144 set DNS UDP buffer size to \fIbytes\fR bytes. Valid values
145 are from 512 to 65535. If \fIbytes\fR is greather than 512,
146 EDNS0 (RFC 2671) extensions will be used.
149 Use given UDP port number \fInum\fR instead of the default port 53 (domain).
152 set AA (auth only) query bit.
155 do not set RD (recursion desired) query bit (set by default).
157 \fBdnssec\fR or \fBdo\fR
158 set DNSSEC OK (DO) query flag (\fBdnsget\fR does not verify DNSSEC signatures,
159 only displays them; this is set in EDNS RR).
162 set CD (checking disabled) query bit.
166 \fB\-n \fInameserver\fR
167 Use the given nameserver(s) (may be specified more than once)
168 instead of the default. Using this option has the same same effect as
172 environment variables, with the only difference that only IPv4 addresses
173 are recognized for now, and it is possible to specify names (which will
174 be resolved using default settings) instead of IP addresses.
178 print short help and exit.
181 When all names where resovled successefully,
183 exits with zero exit status. If at least one name was not found,
185 will exit with return code 100. If some other error occured during
186 name resolution, it will exit with code 99. In case of usage or
187 initialization error,