DNS Record Guide & Validator
Learn what A, AAAA, CNAME, MX, TXT and other DNS records do — and check your syntax as you write them
A combined reference and validator for the DNS records every domain owner ends up configuring: A, AAAA, CNAME, MX, TXT, SRV, and NS. Read what each record type is for and how it's structured, then test your own values for syntax problems — invalid IP addresses, malformed domain patterns, and more — in real time.
도구를 불러오는 중…
🔒 Everything runs 100% in your browser. Your files and input are never uploaded to any server.
How to use
- Click a record type in the Guide tab to see what it's used for and a sample BIND-format entry.
- Switch to the Validator tab and fill in the record type, TTL, host, and target value.
- Get instant syntax feedback on whether your input matches the record's standard format, then copy it as a ready-to-use BIND record.
FAQ
- What's the main difference between an A record and a CNAME record?
- An A record maps a domain straight to a physical IP address, while a CNAME record points a domain at another domain name (an alias), which is then resolved in turn.
- What does the TTL value mean, and how should I set it?
- TTL (Time To Live) is how long, in seconds, DNS caching servers will hold onto that record before re-querying it. A shorter TTL means changes propagate around the world faster, at the cost of more lookup traffic; a longer TTL is more efficient for lookups but means changes — like migrating servers — take longer to fully propagate. If you know a migration is coming, it's safest to lower the TTL (e.g., to 300 seconds) ahead of time.
- What does the TTL value mean, and how should I set it?
- TTL (Time To Live) is how long, in seconds, DNS caching servers will hold onto that record before re-querying it. A shorter TTL means changes propagate around the world faster, at the cost of more lookup traffic; a longer TTL is more efficient for lookups but means changes — like migrating servers — take longer to fully propagate. If you know a migration is coming, it's safest to lower the TTL (e.g., to 300 seconds) ahead of time.