Skip to content

Main content

DNS NXDOMAIN NODATA Header Distinction Tool

Headers distinguish NXDOMAIN from NOERROR with an empty answer; NODATA still requires message-level context.

Loading tool…

Description

Classify RCODE 3 as nxdomain; RCODE zero becomes noerror-empty-answer or noerror-answer according to answerCount.

A DNS response code and an empty answer section describe only part of a response. Establishing the reason an answer is absent can require authority data and query context.

Classify RCODE 3 as nxdomain; RCODE zero becomes noerror-empty-answer or noerror-answer according to answerCount.

When to use this tool

Use DNS NXDOMAIN NODATA Header Distinction when you need a cautious classification using only supplied DNS header facts.

How to use the tool and how it works

  1. Enter rcode, answerCount, authoritative. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read headerClass, nodataProven, authoritative. Inspect nodataProven, authoritative before interpreting the associated values.

Classify RCODE 3 as nxdomain; RCODE zero becomes noerror-empty-answer or noerror-answer according to answerCount. Other codes become other-error. Copy authoritative and always return nodataProven false.1

Input fieldMeaning and unitsAccepted input
rcodeRcodeRequired. Safe integer; minimum 0; maximum 15.
answerCountAnswer CountRequired. Safe integer; minimum 0; maximum 65535.
authoritativeAuthoritativeRequired. Boolean.
Output fieldInterpretationReturned shape
headerClassHeader ClassRequired. Text; maximum UTF-16 length 8192.
nodataProvenNodata ProvenRequired. Boolean.
authoritativeAuthoritativeRequired. Boolean.
json
{
  "input": {
    "rcode": 3,
    "answerCount": 0,
    "authoritative": true
  },
  "output": {
    "headerClass": "nxdomain",
    "nodataProven": false,
    "authoritative": true
  }
}

Limitations and assumptions

  • An empty answer alone cannot establish NODATA; authority records and response context are not analyzed.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
  • Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.

Alternative or Complementary methods

Inspect the complete response, authority section, and original query before assigning a negative-answer meaning.

References

  1. Calculation and input contract: network/dns-nxdomain-nodata-header-distinction — tool.io

Similar or alternative tools