DNS configuration workflow
DNS records: zone-file syntax, TXT bytes and publication checks
Generating a record is a syntax step, not a DNS change. Your zone, provider and delegated nameservers determine what can be published and what resolvers receive.
Content updated: · Maintainer and corrections
Keep owner names, targets and TTL explicit
A and AAAA supply address data; CNAME supplies an alias target; MX and SRV add their own ordered fields. They are not interchangeable. Review absolute names, label and wire-length limits, the supported IDN contract and the exact output syntax.
A TTL is a cache lifetime, not a deadline by which every resolver must change. A generated CNAME cannot establish that an existing zone has no conflicting records. Delegation, apex restrictions, DNSSEC and provider-specific flattening require separate checks.
TXT length is measured in bytes
A DNS TXT record can contain multiple character strings, each at most 255 octets. A Unicode character can use several UTF-8 bytes. Zone-file quoting and decimal byte escapes differ from JSON and HTML escaping; never split a multibyte character blindly.
Providers may accept text without the quotes required in a zone file, or handle multiple strings differently. Check the destination's expected format rather than pasting zone-file markup into any form. The builder does not publish, query or verify ownership, delivery or propagation.
Data provenance