dnsget(1)
π dnsget(1) β the DNS lookup bestie π
General Commands Manual Β· section 1, babes β¨
πΈ NAME πΈ
dnsget β your lil DNS lookup utility π¦
β¨ SYNOPSYS β¨
dnsget [-v|-q] [-c class] [-t type] [-o opt,opt,...] name...
(no cap, that's the whole vibe)
π DESCRIPTION π
Okay so dnsget is a simple command-line tool that does DNS lookups, basically the same energy as host(1) and dig(1). She's useable for both interactive/debugging scenarious and in scripts β she does it all, main character behavior honestly. The program is implemented using the udns(3) library π«Ά
By default, dnsget produces a human-readable output, similar to
alias.example.com. CNAME www.example.com.
www.example.com. A 192.168.1.1
www.example.com. MX 10 mx.example.com.
which is just sufficient to see how a given name resolves. Literally it's giving "here's the tea, no extras" πββοΈ
Output format is controllable with -v and -q options β the former increases verbosity level up to printing the whole DNS contents of all packets sent and received, which is suitable for debugging DNS problems π, while the latter reduces the level, making output more quiet, up to bare result with no error messages, which is good for scripts π€«
π OPTIONS π
The following options are recognized by dnsget:
-vβ produce more detailed output. More-v's means more details will be produced. With single-v,dnsgetwill print contents of all received DNS packets (in a readable format), while with-vv, it will output all outgoing DNS packets too. She's yapping (affectionate) π¬-qβ the opposite for-vβ produce less detailed output. With single-q,dnsgetwill only show (decoded) data from final DNS resource records (RR), while-qqalso suppresses error messages. Quiet queen π€-ttype β request record(s) of the given type type. By default,dnsgetwill ask for IPv4 address (A) record, or forPTRrecord if the argument in question is an IPv4 or IPv6 address. Recognized types includeA,AAAA,MX,TXT,CNAME,PTR,NS,SOA,ANYand others.-cclass β request DNS record(s) of the given class class. By defaultdnsgetusesINclass. Valid classes includeIN,CH,HS,ANY.-aβ (compatibility option). Equivalent to setting query type toANYand increasing verbosity level (-v). She's old-school but she still slays β¨-Cβ (planned) π-xβ (planned) π-oopt,opt,...β (may be specified several times). Set resolver options (in a formoption:value) as if they were set in$RES_OPTIONSenvironment variable, or set query flags:timeout:secβ Set initial query timeout to sec.attempts:numβ (re)try every query num times before failing.udpbuf:bytesβ set DNS UDP buffer size to bytes bytes. Valid values are from512to65535. If bytes is greather than512, EDNS0 (RFC 2671) extensions will be used.port:numβ Use given UDP port number num instead of the default port53(domain).aaβ set AA (auth only) query bit.nordβ do not set RD (recursion desired) query bit (set by default).dnssecordoβ set DNSSEC OK (DO) query flag (dnsgetdoes not verify DNSSEC signatures, only displays them; this is set in EDNS RR).cdβ set CD (checking disabled) query bit.
-nnameserver β Use the given nameserver(s) (may be specified more than once) instead of the default. Using this option has the same same effect as$NSCACHEIPor$NAMESERVERSenvironment variables, with the only difference that only IPv4 addresses are recognized for now, and it is possible to specify names (which will be resolved using default settings) instead of IP addresses.-hβ print short help and exit. π
π RETURN VALUE π
When all names where resovled successefully, dnsget exits with zero exit status β
. If at least one name was not found, dnsget will exit with return code 100 π. If some other error occurred during name resolution, it will exit with code 99 π. In case of usage or initialization error, dnsget will return 1 π
fr fr bestie, check those exit codes in your scripts β 0 is the slay, everything else is a cry for help π
π SEE ALSO π
host(1) dig(1) resolv.conf(5) udns(3).
User Utilities Β· Jan 2014 Β· dnsget(1) π¦
okay that's the whole page, ily, go resolve some names and eat, periodt πβ¨π
π¦ where this page comes from
- alpine 3.22: udns-doc 0.6-r0 Β· LGPL-2.1-or-later
- alpine 3.23: udns-doc 0.6-r0 Β· LGPL-2.1-or-later
- alpine 3.24: udns-doc 0.6-r0 Β· LGPL-2.1-or-later
- arch rolling: udns 0.7-1 Β· LGPL-2.1-or-later
- debian trixie: udns-utils 0.6-1
- epel 10: udns 0.6-1.el10_0 Β· LGPL-2.1-or-later
- epel 9: udns 0.5-1.el9 Β· LGPLv2+
- fedora 43: udns 0.6-3.fc43 Β· LGPL-2.1-or-later
- fedora 43: udns 0.6-3.fc43 Β· LGPL-2.1-or-later
- fedora 44: udns 0.6-4.fc44 Β· LGPL-2.1-or-later
- fedora 44: udns 0.6-4.fc44 Β· LGPL-2.1-or-later
- nixos 26.05: udns 0.6
- nixpkgs unstable: udns 0.6
- opensuse-leap 16.0: udns 0.6-bp160.1.12 Β· LGPL-2.1-or-later
- opensuse-leap 16.0: udns 0.6-bp160.1.12 Β· LGPL-2.1-or-later
- opensuse-leap 16.0: udns 0.6-bp160.1.12 Β· LGPL-2.1-or-later
- opensuse-leap 16.0: udns 0.6-bp160.1.12 Β· LGPL-2.1-or-later
- ubuntu noble: udns-utils 0.5-1
- ubuntu questing: udns-utils 0.6-1
- ubuntu resolute: udns-utils 0.6-1build1
- ubuntu stonking: udns-utils 0.6-1build1
- Copyright (C) 2005-2014 Michael Tokarev <mjt+udns@tls.msk.ru>
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms