DNS Lookup

Discover how DNS records are used and explore the different record types that power every domain on the internet.

What are DNS records?

The Domain Name System (DNS) is the backbone of the internet. DNS records determine how each domain is understood by computers — translating human-readable domain names into the IP addresses that servers actually use. When you enter a domain in a browser, a DNS resolver checks its cache first, then queries authoritative name servers until the domain resolves to an IP address.

Forward DNS lookup

Resolves a domain name into its corresponding IP address — the most common type of DNS query performed by browsers and applications.

Reverse DNS lookup

Does the opposite — takes an IP address and returns its associated domain name. Commonly used for email validation and identifying server owners.

Types of DNS records

MX record

Whenever a domain is involved in email activities, such as sending and receiving, the domain must have its MX record configured.

CNAME record

The canonical name record acts as an alias and points to another DNS record. Use it to map a subdomain like www.example.com to its root domain.

A record

Using a domain name instead of an IP address is possible only with the help of the A record. It associates a hostname with its IPv4 address.

AAAA record

When a domain or subdomain points to an IPv6 address, the quad-A record is used. It works like an A record but for the newer IPv6 addressing scheme.

NS record

An NS record identifies which name servers are authoritative for a domain. If a domain has more than one name server, NS lists them all.

SRV record

The service record specifies the hostname, port, and other details for specific services like instant messaging or VoIP associated with a domain.

SOA record

The start of authority record gives a complete picture of a domain's DNS zone file, including the primary name server and administrative details.

TXT record

Text records store arbitrary information about a domain. Authentication standards like SPF, DKIM, and DMARC are defined using TXT records.

Reverse IP record

A reverse lookup maps an IP address back to its domain name. This helps identify and validate legitimate email senders and flag spammers.

Frequently Asked Questions

Do I need DNS records?

DNS records are what connect domain names to the servers that host your website, handle your email, and run your services. Without them, visitors would need to remember raw IP addresses to reach any site — which is impractical. Every functioning domain on the internet relies on at least a basic set of DNS records.

Can I delete DNS records?

DNS records can be removed from your zone file through your domain registrar or DNS provider. However, deletions are typically permanent and cannot be undone, so it is important to be certain before removing any record. Deleting the wrong record can take your website, email, or other services offline until the record is recreated and propagates.

What is a DNS cache?

A DNS cache is a temporary store of recent DNS lookup results, maintained by your browser, operating system, and internet service provider. Caching speeds up browsing by avoiding repeated lookups for the same domain. Occasionally, a cache can hold outdated or incorrect information — in those cases, flushing the DNS cache forces a fresh lookup and can resolve connectivity issues.

How long do DNS changes take to propagate?

DNS changes propagate at a rate determined by the TTL (Time to Live) value set on the record before it was changed. A TTL of 3600 seconds means resolvers worldwide can cache the old value for up to one hour before fetching the new one. In practice, most users see changes within minutes to a few hours, though full global propagation can take up to 48 hours in some cases. Reducing the TTL before making planned changes is a common best practice to minimize the propagation window.

What is the difference between authoritative and recursive DNS?

An authoritative DNS server holds the actual DNS records for a domain and provides definitive answers to queries about that domain. A recursive DNS resolver (used by your ISP or public DNS services like Google's 8.8.8.8) acts on behalf of clients — querying authoritative servers and caching results to answer future requests faster. When you look up a domain, your device contacts a recursive resolver, which in turn queries the appropriate authoritative servers to find the answer.