Breaking one raw DNS line into its four parts
The raw line 'example.com. 300 IN A 1.2.3.4' parses into name example.com., type A, TTL 300 seconds, and rdata 1.2.3.4 -- the standard whitespace-separated fields of a zone-file-style DNS record.
The trailing dot after 'example.com.' is significant, not a typo -- it denotes a fully-qualified domain name (FQDN) in DNS zone file notation, distinguishing it from a relative name that would be interpreted relative to the zone's origin.
The record type (A here) determines how to interpret rdata -- an A record's rdata is an IPv4 address, while other types (CNAME, MX, TXT) would have differently-structured rdata that this same four-field breakdown still separates out, just with different meaning in that last field.
What this parser doesn't do
First-line tokenizer. Not a live DNS lookup and not a full zone file parser. This parses exactly one line of text you paste in -- it doesn't query live DNS servers to see what a domain actually resolves to right now, and it doesn't parse a complete multi-record zone file with its own directives ($ORIGIN, $TTL) and comments.
TTL (300 seconds here, or 5 minutes) controls how long resolvers cache this record before re-querying -- a low TTL like this one is common right before a planned DNS change, since it lets a subsequent update propagate faster once made.
Real zone files can express the same information in more compact or varied formats (omitting the class 'IN' when it's the default, using tabs instead of single spaces) that a simple whitespace tokenizer might not handle identically to a full-featured zone parser.
Related DNS and record tools
For calculating how long a TTL-based cache will actually persist from a given point in time, the DNS TTL Countdown Calculator handles that specific timing question.
If the domain's certificate validity (a common companion check when troubleshooting a domain's setup) is also in question, the SSL/TLS Certificate Expiry Calculator covers that separately.
Frequently Asked Questions (FAQ)
Why does 'example.com.' have a trailing period?
The trailing dot marks it as a fully-qualified domain name (FQDN) in standard DNS zone file notation -- it explicitly anchors the name to the DNS root, distinguishing it from a name that would otherwise be interpreted as relative to the zone's origin.
What does TTL 300 actually mean for this record?
It means DNS resolvers that look up this record are instructed to cache it for 300 seconds (5 minutes) before querying again for a fresh answer. A short TTL like this is common when a change to the record is planned soon, since it limits how long outdated cached answers persist.
Does this tool perform a live DNS lookup on the domain?
No. First-line tokenizer. Not a live DNS lookup and not a full zone file parser. It only parses the text of one raw DNS record line you paste in. It doesn't query any DNS server to check what the domain currently resolves to in reality.
Can I paste an entire zone file into this tool?
It's built to parse a single record line, not a full multi-record zone file with its own directives and comments. For a complete zone file, you'd need a dedicated zone-file parser or process it one line at a time through this tool.
What would change if the record type were CNAME or MX instead of A?
The same four-field breakdown (name, type, TTL, rdata) would still apply, but the rdata field's meaning changes with type -- a CNAME's rdata is another hostname, an MX record's rdata includes a priority and mail server hostname, while an A record's rdata is simply an IPv4 address.
