b2KIT

DNS Record Builder

Build and validate DNS records (A, AAAA, CNAME, MX, TXT, SRV, CAA) with syntax checking and TTL guidance.

Tested tool guide Tested browser tools Checked August 16, 2026

What DNS Record Builder does and how it behaves

DNS Record Builder prepares a DNS record from the fields required by its selected type and checks those fields for syntax problems. It covers address records, aliases, mail routing, text data, service discovery, and certification authority policy, while also providing TTL guidance. A common source of mistakes is the trailing dot on a domain name. In zone-file notation, that dot marks an absolute name; without it, a DNS system may interpret the name relative to the zone origin.

How the result is produced

1

Type-specific fields

Validation follows the structure of the selected DNS record. A and AAAA records require IPv4 and IPv6 addresses, respectively. CNAME requires an alias target. MX adds a preference value and mail exchanger. SRV uses priority, weight, port, and target. CAA combines flags, a property tag, and a value, while TXT carries textual data.

2

TTL guidance

The TTL specifies how long, in seconds, a resolver may cache a DNS answer. The builder's guidance helps compare shorter caching during planned changes with longer caching for stable records. Changing a TTL does not remove copies already cached under an earlier value; those answers may remain until their original cache lifetime expires.

Good uses

  • Drafting an MX record with an explicit preference before configuring mail delivery for a domain.
  • Checking the priority, weight, port, and target of an SRV record used for service discovery.
  • Preparing a CAA or TXT record for entry into a registrar or managed DNS control panel.

Limits and checks

  • Syntax validation does not confirm that a record has been published, delegated correctly, or returned by authoritative name servers.
  • Relative and absolute names depend on zone context. Review trailing dots and the zone origin before copying generated names into a zone file.
  • A record can be valid by itself but unsuitable beside existing records. In particular, a CNAME owner generally cannot also hold unrelated record data.

Common questions

Can the builder choose the best TTL for my record?

It can provide TTL guidance, but there is no universally correct value. A shorter TTL can let newly querying resolvers receive a later change sooner, while increasing authoritative query frequency. A longer TTL favors caching but can prolong old answers. Data already cached can remain until the TTL attached to that cached answer expires.

Does a valid result mean the DNS record will work?

No. Passing the builder's checks means the entered fields are syntactically plausible for the selected record type. It does not prove that the authoritative zone accepts the entry, that delegation is correct, that caches have expired, or that the named host or service is reachable. Confirm publication with DNS queries after deployment.

References and verification

The behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.

Related Tools