dnsviz-query(1)

πŸ“¦
version 0.11.1 Β· 5 versions
, in debian trixie, fedora 43, fedora 44, nixos 26.05, ubuntu resolute, ubuntu stonking

πŸ’– dnsviz-query(1) πŸ’–

okay so bestie, welcome to the General Commands Manual entry for dnsviz-query β€” she's a little DNS detective and she's about to tell you everything. pull up a chair, grab a boba, let's go πŸ§‹βœ¨


✨ NAME ✨

dnsviz-query β€” assess a DNS query πŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

dnsviz query [ @server ] [ -b address ] [ -c class ] [ -q name ] [ -t
type ] [ -x addr ] [ -4 ] [ -6 ] [ name ] [ type ] [ class ] [
queryopt... ]

dnsviz query [ -h ]

dnsviz query [ global-queryopt... ] [ query... ]

🌸 DESCRIPTION 🌸

so what she does is: you hand her names and types on the command line, she fires off queries for them at DNS servers, processes the output, and presents it to you. that's the whole vibe. 🫢

here's the tea though: dnsviz-query adopts a subset of the command-line options used by ISC's dig(1), but underneath she's using dnsviz-probe(1) and dnsviz-print(1) to actually issue queries and assess the results. she's meant to be a shortcut β€” a lil fast lane for quickly assessing DNS queries and diagnosing problems β€” by invoking dnsviz-probe(1) and dnsviz-print(1) with their most commonly used options and with a usage that's familiar, similar to (but not equal to) dig(1). iykyk 😌

but if you want a more detailed analysis β€” like, the kind that reveals the actual nature of errors β€” the user should go straight to dnsviz-probe(1), dnsviz-grok(1), dnsviz-print(1), and dnsviz-graph(1) directly. those are the big sisters fr fr.

by default, diagnostic queries are sent to recursive servers. and if no servers are specified with @, then the first server in /etc/resolv.conf is selected. ⚠️ note that unlike dig(1), dnsviz-query(1) only tries one server. one. single. server. no backup bestie, no second chances.

if +trace is used, the behavior changes β€” the root authoritative servers are first queried, and referrals are followed downwards to the name(s) in question. like following a trail of breadcrumbs down the DNS tree 🌈

and to simplify usage, there's a default root trusted key if none is specified on the command line with +trusted-key. so convenient, she ate πŸ’…


πŸ’œ OPTIONS πŸ’œ

  • -x address β€” specify an IPv4 or IPv6 address for a reverse DNS (i.e., PTR) lookup. πŸ”„
  • -b address β€” specify a source IPv4 or IPv6 address for queries, rather than detecting it. you can use this option more than once to supply both an IPv4 and an IPv6 address. 🫢

using this option is sometimes necessary when you're on a dual-homed machine and it's desirable to use the non-default interface for queries.

  • -q name β€” specify a query name.
  • -t type β€” specify a query type.
  • -c class β€” specify a query class (currently, only IN is supported; all other classes are ignored πŸ™ˆ).
  • -4 β€” use IPv4 only. if this is specified, then queries over IPv6 are not attempted β€” unless -6 is also specified.
  • -6 β€” use IPv6 only. if this is specified, then queries over IPv4 are not attempted β€” unless -4 is also specified.

πŸŽ€ QUERY OPTIONS πŸŽ€

  • +[no]trace β€” query authoritative servers, beginning at the DNS root, and follow referrals downwards. the default is to query a recursive server instead. 🌳
  • +trusted-key=filename β€” specify a file that contains trusted keys for processing diagnostic queries.

the format of this file is master zone file format, and it should contain DNSKEY records that correspond to one more trusted keys for one or more DNS zones. πŸ”‘


πŸ”₯ EXIT CODES πŸ”₯

the exit codes are:

  • 0 β€” program terminated normally. slay, everything's fine ✨
  • 1 β€” program execution was interrupted, or an unknown error occurred. πŸ’€

🌈 SEE ALSO 🌈

dnsviz(1), dnsviz-probe(1), dnsviz-grok(1), dnsviz-graph(1), dnsviz-print(1)


and that's the whole page bestie!! πŸ’– this version is 0.11.1, dated 21 April 2025 β€” go forth and diagnose, you absolute icon πŸ‘‘βœ¨πŸ¦‹

πŸ“¦ where this page comes from