MDIG(1)

๐Ÿ’– MDIG(1) โ€” BIND 9 bestie edition ๐Ÿ’–

โœจ NAME โœจ

mdig โ€” DNS pipelined lookup utility. periodt. ๐Ÿ’…

๐Ÿ›ฐ๏ธ SYNOPSIS ๐Ÿ›ฐ๏ธ

mdig <{@server>} [-f filename] [-h] [-v] [ [-4] | [-6] ] [-m] [-b
       address] [-p port#] [-c class] [-t type] [-i] [-x addr] [plusopt...]

mdig {-h}

mdig [@server] {global-opt...} { {local-opt...} {query} ...}

๐Ÿ’ฌ DESCRIPTION ๐Ÿ’ฌ

Okay so bestie, mdig is literally the multiple/pipelined query version of dig <#std-iscman-dig>: instead of waiting for a response after sending each query, it begins by sending all queries. Responses are displayed in the order in which they are received, not in the order the corresponding queries were sent. chaotic? yes. iconic? also yes. ๐Ÿฆ‹

mdig options are a subset of the dig <#std-iscman-dig> options, and are divided into "anywhere options," which can occur anywhere, "global options," which must occur before the query name (or they are ignored with a warning), and "local options," which apply to the next query on the command line. iykyk. โœจ

The @server option is a mandatory global option. It is the name or IP address of the name server to query. (Unlike dig <#std-iscman-dig>, this value is not retrieved from /etc/resolv.conf.) It can be an IPv4 address in dotted-decimal notation, an IPv6 address in colon-delimited notation, or a hostname. When the supplied server argument is a hostname, mdig resolves that name before querying the name server. no cap, it does the lookup first. ๐ŸŒˆ

mdig provides a number of query options which affect the way in which lookups are made and the results displayed. Some of these set or reset flag bits in the query header, some determine which sections of the answer get printed, and others determine the timeout and retry strategies. lots of little dials, bestie. ๐ŸŽ€

Each query option is identified by a keyword preceded by a plus sign (+). Some keywords set or reset an option. These may be preceded by the string no to negate the meaning of that keyword. Other keywords assign values to options like the timeout interval. They have the form +keyword=value. copy that format exactly, fr fr. โญ


๐Ÿ› ๏ธ ANYWHERE OPTIONS ๐Ÿ› ๏ธ

  • -f filename โ€” This option makes mdig operate in batch mode by reading a list of lookup requests to process from the file filename. The file contains a number of queries, one per line. Each entry in the file should be organized in the same way they would be presented as queries to mdig using the command-line interface. one query per line, bestie. ๐Ÿ“
  • -h โ€” This option causes mdig to print detailed help information, with the full list of options, and exit. helpful queen behavior. ๐Ÿซถ
  • -v โ€” This option causes mdig to print the version number and exit. version check, slay. ๐Ÿ’œ

๐ŸŒ GLOBAL OPTIONS ๐ŸŒ

  • -4 โ€” This option forces mdig to only use IPv4 query transport. IPv4 only, no cap. ๐Ÿ’™
  • -6 โ€” This option forces mdig to only use IPv6 query transport. IPv6 only, periodt. ๐Ÿ’œ
  • -b address โ€” This option sets the source IP address of the query to address. This must be a valid address on one of the host's network interfaces or "0.0.0.0" or "::". An optional port may be specified by appending "#<port>". source address glow-up. โœจ
  • -m โ€” This option enables memory usage debugging. memory gossip, basically. ๐Ÿงš
  • -p port# โ€” This option is used when a non-standard port number is to be queried. port# is the port number that mdig sends its queries to, instead of the standard DNS port number 53. This option is used to test a name server that has been configured to listen for queries on a non-standard port number. not the usual 53, bestie. ๐Ÿ”ฅ

โœจ The global query options are โœจ

  • +additional, +noadditional โ€” This option displays [or does not display] the additional section of a reply. The default is to display it. additional section: shown by default. ๐ŸŽ€
  • +all, +noall โ€” This option sets or clears all display flags. all the flags, one little switch. ๐ŸŒˆ
  • +answer, +noanswer โ€” This option displays [or does not display] the answer section of a reply. The default is to display it. answer section: shown by default. ๐Ÿ’š
  • +authority, +noauthority โ€” This option displays [or does not display] the authority section of a reply. The default is to display it. authority section: shown by default. ๐Ÿ’œ
  • +besteffort, +nobesteffort โ€” This option attempts to display [or does not display] the contents of messages which are malformed. The default is to not display malformed answers. malformed answers stay hidden unless you ask. ๐Ÿ’€
  • +burst โ€” This option delays queries until the start of the next second. wait for the next second, then go. โณ
  • +cl, +nocl โ€” This option displays [or does not display] the CLASS when printing the record. CLASS visibility toggle. ๐Ÿฆ‹
  • +comments, +nocomments โ€” This option toggles the display of comment lines in the output. The default is to print comments. comments on by default, bestie. ๐Ÿ’ฌ
  • +continue, +nocontinue โ€” This option toggles continuation on errors (e.g. timeouts). keep going after errors? toggle it. ๐Ÿ“
  • +crypto, +nocrypto โ€” This option toggles the display of cryptographic fields in DNSSEC records. The contents of these fields are unnecessary to debug most DNSSEC validation failures and removing them makes it easier to see the common failures. The default is to display the fields. When omitted, they are replaced by the string [omitted]; in the DNSKEY case, the key ID is displayed as the replacement, e.g., [ key id = value ]. crypto fields: useful sometimes, noisy other times. ๐Ÿ”
  • +multiline, +nomultiline โ€” This option toggles printing of records, like the SOA records, in a verbose multi-line format with human-readable comments. The default is to print each record on a single line, to facilitate machine parsing of the mdig output. one-line default = machine-parseable vibes. ๐Ÿค–
  • +question, +noquestion โ€” This option prints [or does not print] the question section of a query when an answer is returned. The default is to print the question section as a comment. question section defaults to a comment. ๐ŸŽ€
  • +rrcomments, +norrcomments โ€” This option toggles the display of per-record comments in the output (for example, human-readable key information about DNSKEY records). The default is not to print record comments unless multiline mode is active. record comments only by default in multiline mode. ๐Ÿ’œ
  • +short, +noshort โ€” This option provides [or does not provide] a terse answer. The default is to print the answer in a verbose form. short mode is a whole vibe, but verbose is the default. โœจ
  • +split=W โ€” This option splits long hex- or base64-formatted fields in resource records into chunks of W characters (where W is rounded up to the nearest multiple of 4). +nosplit or +split=0 causes fields not to be split. The default is 56 characters, or 44 characters when multiline mode is active. chunky fields, controlled by W. ๐Ÿงš
  • +tcp, +notcp โ€” This option uses [or does not use] TCP when querying name servers. The default behavior is to use UDP. UDP is the default, bestie. ๐ŸŒŠ
  • +ttlid, +nottlid โ€” This option displays [or does not display] the TTL when printing the record. TTL visibility toggle. ๐Ÿ’š
  • +ttlunits, +nottlunits โ€” This option displays [or does not display] the TTL in friendly human-readable time units of "s", "m", "h", "d", and "w", representing seconds, minutes, hours, days, and weeks. This implies +ttlid. friendly TTL units: seconds, minutes, hours, days, weeks. ๐Ÿ“
  • +vc, +novc โ€” This option uses [or does not use] TCP when querying name servers. This alternate syntax to +tcp is provided for backwards compatibility. The vc stands for "virtual circuit". old-school syntax, still valid. ๐Ÿ’œ

๐Ÿ’… LOCAL OPTIONS ๐Ÿ’…

okay so these ones are the ones that actually shape your query, bestie โ€” not the whole run, just the one thing you're asking for. let's go ๐ŸŽ€

  • -c class โ€” sets the query class to class. it can be literally any valid query class that BIND 9 supports. default is IN, iykyk.
  • -t type โ€” sets the query type to type. again, any valid query type BIND 9 supports is fair game. default is A... unless you threw in -x, in which case it flips to PTR because that's a reverse lookup, obviously ๐Ÿฆ‹
  • -x addr โ€” reverse lookups (mapping addresses โ†’ names) get so much simpler with this. addr is either an IPv4 address in dotted-decimal notation, or a colon-delimited IPv6 address. mdig goes and does the lookup for you on a query name like 11.12.13.10.in-addr.arpa and sets the query type and class to PTR and IN respectively. no cap, it just handles it. and by default, IPv6 addresses get looked up using nibble format under the IP6.ARPA domain. โœจ

the local query options ๐Ÿซถ

these are the + ones. yes there are a lot. yes you should read them all. periodt.

  • +aaflag, +noaaflag โ€” this is literally just a synonym for +aaonly, +noaaonly. same thing, different font ๐Ÿ’€
  • +aaonly, +noaaonly โ€” this sets the aa flag in the query.
  • +adflag, +noadflag โ€” this sets [or does not set] the AD (authentic data) bit in the query. what that does: it requests the server to tell you whether all of the answer and authority sections have been validated as secure, according to the security policy of the server. so AD=1 means everything was validated as secure and the answer is not from an OPT-OUT range. AD=0 means some part of the answer was insecure or not validated. ๐Ÿ‘‘ this bit is set by default.
  • +bufsize=B โ€” sets the UDP message buffer size that gets advertised using EDNS0 to B bytes. max is 65535, min is 0. values outside that range get rounded up or down appropriately (it handles it, don't worry). any value other than zero causes an EDNS query to be sent. ๐Ÿ”ฅ
  • +cdflag, +nocdflag โ€” sets [or does not set] the CD (checking disabled) bit in the query. this is you asking the server to not perform DNSSEC validation of responses. bold of you, but ok.
  • +cookie=####, +nocookie โ€” sends [or does not send] a COOKIE EDNS option, with an optional value. replaying a COOKIE from a previous response lets the server identify a previous client (๐Ÿ‘€ hello again). default is +nocookie.
  • +dnssec, +nodnssec โ€” requests that DNSSEC records be sent by setting the DNSSEC OK (DO) bit in the OPT record in the additional section of the query. say yes to DNSSEC bestie ๐Ÿ’œ
  • +edns[=#], +noedns โ€” specifies [or does not specify] the EDNS version to query with. valid values are 0 to 255. setting the EDNS version causes an EDNS query to be sent. +noedns clears the remembered EDNS version. EDNS is set to 0 by default.
  • +ednsflags[=#], +noednsflags โ€” sets the must-be-zero EDNS flag bits (Z bits) to whatever value you give. decimal, hex, and octal encodings are all accepted. setting a named flag (e.g. DO) is silently ignored. by default, no Z bits are set. ๐Ÿ™ˆ
  • +ednsopt[=code[:value]], +noednsopt โ€” specifies [or does not specify] an EDNS option with code point code and an optional payload of value as a hexadecimal string. +noednsopt clears the EDNS options to be sent.
  • +expire, +noexpire โ€” toggles sending of an EDNS Expire option.
  • +nsid, +nonsid โ€” toggles inclusion of an EDNS name server ID request when sending a query.
  • +recurse, +norecurse โ€” toggles the setting of the RD (recursion desired) bit in the query. this bit is set by default, which means mdig normally sends recursive queries. ๐ŸŒ€
  • +retry=T โ€” sets the number of times to retry UDP queries to server to T instead of the default, 2. and heads up: unlike +tries, this does not include the initial query. don't get it twisted ๐Ÿ’…
  • +subnet=addr[/prefix-length], +nosubnet โ€” sends [or does not send] an EDNS Client Subnet option with the specified IP address or network prefix.

and then there's this specific little move:

  • mdig +subnet=0.0.0.0/0, or simply mdig +subnet=0 โ€” this sends an EDNS client-subnet option with an empty address and a source prefix-length of zero, which signals to a resolver that the client's address information must not be used when resolving this query. stealth mode basically ๐Ÿฅท
  • +timeout=T โ€” sets the timeout for a query to T seconds. default timeout is 5 seconds for UDP transport and 10 for TCP. and if you try to set T to less than 1, you get a query timeout of 1 second applied. them's the rules.
  • +tries=T โ€” sets the number of times to try UDP queries to server to T instead of the default, 3. if T is less than or equal to zero, the number of tries is silently rounded up to 1. silently. it's not gonna argue with you, it's just gonna do it. ๐Ÿ’€
  • +udptimeout=T โ€” sets the timeout between UDP query retries to T.
  • +unknownformat, +nounknownformat โ€” prints [or does not print] all RDATA in unknown RR-type presentation format (see RFC 3597, https://datatracker.ietf.org/doc/html/rfc3597.html). the default is to print RDATA for known types in the type's presentation format. ๐ŸŒธ
  • +yaml, +noyaml โ€” toggles printing of the responses in a detailed YAML format. for the girlies who like their output structured โœจ
  • +zflag, +nozflag โ€” sets [or does not set] the last unassigned DNS header flag in a DNS query. this flag is off by default. it's the mystery flag, it's giving main character energy that nobody's assigned yet ๐ŸŽ€

๐ŸŒˆ SEE ALSO ๐ŸŒˆ


๐Ÿ‘‘ Author ๐Ÿ‘‘

Internet Systems Consortium โ€” icons, honestly.

2026, Internet Systems Consortium


and that's the whole page bestie, you ate that ๐Ÿ’– this was MDIG(1) from BIND 9.20.30, dated 2026-10-12 โ€” go forth and query slayfully ๐Ÿฆ‹โญ

๐Ÿ“ฆ where this page comes from