Free · live registry data · no login

DNS Record Generator

Build correct A, CNAME, MX, TXT and SRV records from a form.

How it works

Build a correct DNS record from a form, ready to paste

DNS panels disagree about trailing dots, whether to type the full hostname or just the subdomain, and how to split long TXT values. This generator takes the pieces (type, host, value, TTL and, where needed, priority, weight and port) and produces the exact zone-file line plus the field-by-field values most registrar panels ask for. It validates IPs, hostnames, SRV and CAA syntax before you paste anything, and explains any mistake it finds.

Or start from an example

Results appear here after you click Generate record.

How this works

  1. 1

    Normalise the host

    @, bare subdomains and fully-qualified names are all accepted and reduced to the same record name.

  2. 2

    Validate the value

    IPs, hostnames, SRV targets and CAA tags are checked against the rules for that record type.

  3. 3

    Emit both formats

    You get a zone-file line with trailing dots plus the separate fields a web panel asks for.

Frequently asked questions

Should I type the full hostname or just the subdomain in my DNS panel?
It depends on the panel. Cloudflare, Namecheap and GoDaddy want just the subdomain (www) and add your domain automatically; zone-file editors want the full name with a trailing dot (www.example.com.). We show both so you can pick the matching one.
What is the trailing dot for?
In zone files a trailing dot marks a name as fully qualified. Without it, the server appends your zone name, turning mail.example.com into mail.example.com.example.com, a classic cause of broken MX and CNAME records. Web panels usually hide this and add it for you.
What TTL should I use for a new record?
Start at 300 to 600 seconds while you confirm it works, so mistakes are quick to fix. Once stable, 3600 (one hour) is a good default; 86400 (one day) is fine for records that rarely change such as MX or NS.
How do MX priority and SRV weight work?
MX priority is a preference: the lowest number is tried first and the others are backups. SRV has both priority (same idea) and weight, which splits traffic among targets of equal priority in proportion to their weights. Port tells clients which TCP/UDP port the service listens on.
Why does the generator refuse a CNAME on my root domain?
The DNS standard forbids a CNAME at a name that has other records, and the zone root always has SOA and NS records. Providers work around it with ALIAS, ANAME or CNAME flattening, so look for one of those options or use the platform's A record IPs.

Every MailShrine domain includes WHOIS privacy, transfer lock, Anycast DNS with DNSSEC and two business mailboxes.

Register a domainDNS records explainedPoint a domain to a server IPMore tools in this category