Fake DNS Record Generator

How to use

1. 1️⃣
   Choose your options above
2. 2️⃣
   Click Generate
3. 3️⃣
   Copy your result

Detailed instructions

1. Enter your target domain in the Domain field (e.g., acme-internal.io) to set the zone origin for all records.
2. Set the Number of Records to match your testing needs — use 8 for quick parser tests, higher counts for stress tests.
3. Click Generate to produce the zone file entries with varied record types, TTLs, and realistic rdata values.
4. Copy the output and paste it directly into your parser, test fixture file, documentation block, or zone import tool.
5. Re-click Generate to produce a fresh set with different hostnames and IPs each time you need non-duplicate test data.

Use Cases

• •Testing a Go or Python BIND zone-file parser against all four record types with realistic rdata
• •Populating README examples for a Terraform Route 53 or Cloudflare provider module
• •Mocking AWS Route 53 API responses in Postman collections or Jest integration tests
• •Generating per-session lab data for DNS administration workshops so every student cohort gets a fresh zone
• •Adding believable DNS output samples to runbooks and Confluence pages without redacting production records

Tips

• →For parser edge-case testing, generate two batches and concatenate them — this creates repeated subdomains with different TTLs, which parsers often handle incorrectly.
• →Use a .internal TLD (e.g., corp.internal) as your domain when generating records for private network documentation so readers immediately know the data is non-public.
• →If your test suite checks MX priority handling, generate 10+ records — the varied priority values across multiple MX entries will reveal ordering bugs in your code.
• →Pair the generated SPF TXT records with a DMARC checker tool to verify your security scanner correctly parses both policy types from the same zone.
• →When writing Terraform or Pulumi examples, generate 5 records and use one of each type — A, CNAME, MX, TXT — to show the full range of your DNS module's capabilities.
• →Avoid using the default example.com domain in committed documentation; swap it for a domain you own or a clearly fake TLD like .example to prevent confusion.

FAQ