Skip to main content
Book Consultation →
Propagation and records100% FreeInstant

DNS Record Validation: Validate Your Domain DNS

This DNS record validation tool checks a domain for common setup mistakes. It looks at delegation, name servers, address records, CNAME conflicts, mail servers and SPF, then lists what passed and what needs fixing.

By Debmedia Technologies LLP · Kolkata, India · Updated

What Is DNS Record Validation?

DNS record validation means checking that the records you publish are complete, consistent and follow DNS rules. A record can exist and still be wrong, for example a mail server name that does not resolve or a CNAME that clashes with other data.

Small mistakes like these often cause hard-to-trace problems: a website that works only on some networks, email that bounces, or a domain that suddenly stops resolving after a provider change. A validation report finds them before your visitors do.

How to Use This Tool

  1. Enter the domain you want to review, such as example.com.
  2. Choose a resolver. Google is a good default.
  3. Press Validate DNS. The tool runs several lookups at once.
  4. Read the list from top to bottom and fix anything marked as an error first.

What the Validation Covers

CheckWhy it matters
DelegationThe domain must have name servers, or nothing can resolve it.
Name server countTwo or more servers keep the domain online if one fails.
Name server addressesEvery name server needs an IP address that can be found.
Address recordsShows whether the name points to a public IP address. Private addresses do not work on the internet.
CNAME conflictsA CNAME cannot sit next to other records at the same name.
Mail serversEach MX target must resolve to an address and must not be an IP or a CNAME.
SPF countOnly one SPF record is allowed per domain.
www recordReminds you if visitors typing www will find nothing.

Common Problems and How to Fix Them

CNAME at the root of the domain

Many providers ask for a CNAME on the bare domain, but the root also needs SOA, NS and often MX records. Use an A record instead, or ask your DNS host for an ALIAS or flattened record.

MX record pointing to an IP address

MX records must name a host, not an address. Create an A record such as mail.example.com and point the MX record to that name.

Two SPF records

Receivers treat two SPF records as an error. Combine them into one record and test it with the SPF analyzer.

Only one name server

A single name server is a single point of failure. Add a second one, preferably on a different network. See RFC 1912, common DNS operational and configuration errors for more background.

What to Do After Validation

Once your records pass, test how fast the changes spread with the propagation tester. If you want a deeper review that also queries every authoritative server, run the full health report.

Validation reads live DNS, so run it again after each change. A clean report today does not guarantee a clean report after your next edit, and it only covers the records the tool can look up without knowing your private service names.

Frequently Asked Questions

It checks that the domain is delegated, has at least two name servers, resolves to valid addresses, has no CNAME conflicts, has working mail servers and has a single SPF record.
A CNAME says the name is an alias of another name, so no other data may exist at that name. Mixing them breaks lookups and is a very common cause of mail and website errors.
No. Errors are real faults that should be fixed. Warnings and notes point to things that are often fine but worth reviewing, such as a missing www record.
Validation reviews the records you publish. The DNS health checker also tests each authoritative server, such as response, serial numbers and open recursion.

Disclaimer: results come from live requests and can change as records and servers change. We cannot guarantee that every answer matches what every visitor sees.