The Complete DNS Lookup Guide: How to Inspect and Troubleshoot Domain Records

Every interaction on the modern web relies on the Domain Name System, often called the internet's phonebook. When a user enters a web domain into their browser, the computer does not immediately know where that server is physically located. Instead, it issues a DNS lookup request to locate the target machine's corresponding public IP address.

When migrating web hosting providers, setting up corporate email services, or configuring security protocols like SPF and DMARC, understanding how to inspect domain records is essential. Misconfigured DNS records can result in total website downtime, email delivery failures, or security vulnerabilities.

This guide explores how different DNS record types function, how to run an online DNS lookup, and how to troubleshoot common domain resolution errors.

Understanding Core DNS Record Types

A domain's DNS configuration consists of individual text instructions called resource records. Each record type serves a specific function in guiding web browsers, mail servers, and automated tools:

• A Records and AAAA Records: The A record maps a domain name directly to a 32-bit IPv4 address. Its modern counterpart, the AAAA record, maps a domain to a 128-bit IPv6 address. These are the primary records used to point web domain names to hosting servers.
• MX Records (Mail Exchange): MX records specify which mail servers are responsible for accepting incoming email messages on behalf of your domain name. Each MX record includes a priority preference number; lower numbers indicate higher priority mail servers.
• TXT Records (Text Records): TXT records allow domain owners to attach human-readable and machine-readable text data to a domain. Modern web security protocols rely heavily on TXT records to publish SPF (Sender Policy Framework), DKIM (DomainKeys Identified Mail), and DMARC policies to prevent email spoofing.
• CNAME Records (Canonical Name): CNAME records create an alias mapping one domain name to another canonical domain name, rather than pointing directly to an IP address. They are frequently used to point subdomains to cloud infrastructure or content delivery networks.
• NS Records (Name Server): NS records specify which authoritative name servers hold the master DNS records for your domain name.

How to Run an Online DNS Lookup

When configuring domain settings, verifying that changes have been updated publicly requires running a DNS check.

Using an online DNS lookup tool allows you to query public authoritative resolvers to view your domain's live active records. Testing via a web utility ensures you bypass local operating system caches, giving you an accurate picture of what global DNS servers are reporting.

Before launching new web services or updating mail configurations, verifying that your MX and TXT records are actively resolving prevents costly communication disruptions. To inspect active A, MX, and TXT records for any domain, run an instant query using our online DNS lookup tool.

Troubleshooting DNS Propagation Delays and Failures

When you update domain records at your domain registrar, changes do not take effect globally instantly. This delay is known as DNS propagation.

DNS propagation delays occur because internet routers and local ISPs cache domain records based on a parameter called Time to Live (TTL). TTL defines how many seconds a DNS server should store a record in memory before fetching a fresh copy from the authoritative name server.

If your web page fails to load after a server migration, verify that your local DNS cache has expired. You can flush your local DNS cache on Windows using the command prompt or test if remote web servers are accessible using our web-based network ping test.

ipconfig /flushdns

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

Frequently Asked Questions