DNS RECORD ATLAS / RESOLVER LEDGER

Read returned DNS record sets through one resolver path

Submit a name and one record selection. The browser sends both to the server, which uses Node dns.promises with its configured resolver and returns the records that call supplies.

Open DNS Lookup

Resolver ledger

ENTERED NAME + SELECTED TYPE

SERVER → NODE DNS.PROMISES → CONFIGURED RESOLVER

RETURNED TYPE + VALUE ROWS

A lookup records what this resolver call returns; it is not an authoritative-zone query.

The selectable record atlas

Each choice maps to a resolver method. ALL is a defined collection of seven forward record calls, while PTR remains a separate, explicit choice.

  • A — IPv4 address

    Returned IPv4 addresses.

  • AAAA — IPv6 address

    Returned IPv6 addresses.

  • MX — Mail exchange

    Exchange name with its returned priority.

  • TXT — Text

    Returned text segments joined with spaces.

  • NS — Name server

    Returned name-server host names.

  • CNAME — Canonical name

    Returned canonical-name targets.

  • SOA — Start of authority

    nsname, hostmaster, and serial in one value.

  • PTR — Pointer

    Requested only when PTR is selected.

  • ALL — Defined record set

    Calls A, AAAA, MX, TXT, NS, CNAME, and SOA; it does not call PTR.

One submitted selection, one resolver route

The editor trims the entered name, sends it with the chosen type to trpc.dns.lookup, then renders the returned rows or its status message.

  1. 1. Enter the name

    The server contract accepts a string from 1 to 255 characters. The input is sent as a name; the page does not establish ownership or control of it.

  2. 2. Choose a record type

    Select A, AAAA, MX, TXT, NS, CNAME, SOA, PTR, or ALL. The selection determines the resolver calls, not a zone-wide inspection.

  3. 3. Read returned rows

    Every returned row has a type and a value. MX rows additionally show priority. A returned list may contain only the types that produced rows.

How returned values are normalised for the ledger

The page presents the shape emitted by the server function. It does not add TTL fields or infer missing DNS data.

MX priority

Only MX rows include the resolver-provided priority beside the exchange value.

TXT segments

For a TXT response with segments, the server joins those segments with a space.

SOA value

The displayed SOA value combines nsname, hostmaster, and serial in that order.

No TTL field

The current server response does not supply TTL, so the ledger does not treat TTL as a returned field.

Read absence and mixed ALL results without diagnosis

A record type can produce no rows for this resolver call. In an ALL selection, errors from individual record calls are skipped so rows from other calls can still be returned.

  • An empty returned list leads to the editor’s “no records” notice.
  • An exception reaching the editor leads to its general failed-lookup notice.
  • Neither notice identifies a cause, checks a zone, or describes DNS conditions elsewhere.

Scope of this resolver ledger

The screen documents one server-side resolver path and the fields it returns. It is not an authority, DNSSEC, propagation, ownership, completeness, or service-status assessment.

  • 1–255 — characters accepted by the server name contract
  • 9 — selectable choices, including ALL
  • 7 — record calls in ALL: A through SOA, excluding PTR
  • 0 — TTL fields supplied by the current server function

Continue with adjacent network and webmaster tools

These editors address separate questions. Their request paths and returned fields are independent of the DNS resolver ledger.

  • SSL Checker

    Inspect the certificate data returned for a submitted host.

  • Ping Test

    Record browser HTTP request timings for a public target.

  • What Is My IP

    View address information returned to this browser by its lookup path.

Questions about this DNS lookup

Does ALL include PTR?

No. ALL calls A, AAAA, MX, TXT, NS, CNAME, and SOA. PTR is called only when PTR itself is selected.

Why can ALL show only some record types?

Each included record call is attempted separately. A call that errors is skipped, and rows from other calls can still be returned.

Why is there no TTL beside a value?

The server function currently returns type and value rows, plus priority only for MX. It does not return TTL.

What does no records mean here?

It means the server returned an empty list for this lookup path. The notice does not determine why records were absent or describe a DNS zone.