Read a DNS record field by field

Enter one explicit presentation-format record. The lab separates its shared fields from type-specific RDATA so you can see what each value controls—and what the record cannot prove.

Parsed record

A record anatomy

Maps an owner name to one IPv4 address.

Normalized presentation

www.example.com. 300 IN A 192.0.2.10

Shared record fields

Owner name: www.example.com.The absolute DNS name that owns this RRset; the final dot anchors it at the root.
TTL: 300 secondsThe cache lifetime carried with this data, not a synchronized global countdown.
Class: INThe Internet DNS class used by ordinary public DNS data.
Type: AMaps an owner name to one IPv4 address.
RDATA: 192.0.2.10The type-specific payload; its internal fields are explained below.

Inside the RDATA

IPv4 address
192.0.2.10
The 32-bit address published by this record.

What this record does not prove

An A record does not configure HTTP, redirects, TLS, or application health.
Other A records at the same owner form the complete RRset and must be reviewed together.

Continue with the A record reference.

Parser boundaries

This reads one explicit zone-file-style presentation record. It is not a complete BIND zone-file parser and does not expand @,$ORIGIN, omitted owners, or omitted TTLs.
Valid local syntax does not prove the record is published, correct, authoritative, reachable, or accepted by a consuming service.
One record may be only one member of an RRset. Review every record with the same owner, class, and type together.
Use an explicitly selected live tool to inspect public evidence after you understand the intended record.