DNS Record Lookup

Instantly check A, MX, NS, CNAME, and TXT records for any domain. Debug DNS configuration issues in seconds.

Prevent DNS-Related Downtime

DNS issues can happen anytime. ObserveOne checks your website uptime every minute and alerts you the moment it goes down.

Monitor Uptime Free
No credit card required

Side-by-side breakdowns, no fluff.

About DNS Records

DNS (Domain Name System) translates human-readable domain names into IP addresses. Using the correct DNS records is crucial for website uptime and email deliverability.

A Records

Points a domain to an IPv4 address. The most fundamental record for hosting.

MX Records

Controls where your emails are delivered. Misconfigured MX records result in lost emails.

TXT Records

Used for verification (SPF, DKIM, Google Site Verification) and security.

CNAME Records

Aliases one domain to another. Commonly used for subdomains (www).

AAAA Records

Points a domain to an IPv6 address, the modern counterpart to an A record, which uses IPv4.

NS Records

Delegates the zone to the authoritative nameservers that hold the real records for the domain.

SOA Records

Holds zone metadata, including the primary nameserver and a serial number that tracks each change to the zone.

TTL and Propagation

Every record carries a TTL, the number of seconds a resolver is allowed to cache it before fetching a fresh copy. When you edit a record, existing resolvers keep serving the old value until their cached copy expires, so a change only appears everywhere once the previous TTL has elapsed across every resolver. Lowering the TTL ahead of a planned change speeds up how quickly the update spreads.

Frequently Asked Questions

How long does DNS propagation take?

Up to the record's TTL. A resolver keeps serving the old value until its cached copy expires, so a change can appear within minutes or take as long as 48 hours across every resolver.

What is TTL?

Time to live, the number of seconds a resolver is allowed to cache a record before fetching it again. A low TTL means changes spread quickly; a high TTL reduces query load but slows updates.

What is the difference between an A record and a CNAME?

An A record maps a name straight to an IPv4 address. A CNAME maps one name to another name, letting the target's records resolve the final address. A CNAME cannot coexist with other records on the same name.

What does an NS record do?

It delegates a zone to its authoritative nameservers, telling resolvers which servers hold the real records for the domain.