DNS Lookup

Look up DNS records for any domain.

DNS resolution

Query public DNS records for any domain using the resolver below.

Enter Domain

Understanding DNS

What Is the Domain Name System (DNS)?

The Domain Name System (DNS) is a hierarchical, distributed naming system that translates human-readable domain names (like example.com) into machine-readable IP addresses (like 93.184.216.34). Often called the "phonebook of the internet," DNS is fundamental to how the internet operates.

When you type a URL into your browser:

Your device queries a DNS resolver (usually provided by your ISP)
The resolver checks its cache for a recent answer
If not cached, it queries root name servers, then TLD servers, then authoritative name servers
The IP address is returned to your device
Your browser connects to that IP address to load the website

This entire process typically happens in milliseconds, invisible to the user.

DNS Record Types Explained

A Record (Address Record)

Maps a domain name to an IPv4 address (32-bit). This is the most fundamental DNS record type. Example: example.com · 93.184.216.34

AAAA Record (IPv6 Address Record)

Maps a domain name to an IPv6 address (128-bit). Similar to A records but for the newer IP protocol. Example: example.com · 2606:2800:220:1:248:1893:25c8:1946

MX Record (Mail Exchange)

Specifies the mail servers responsible for receiving email for the domain. Includes a priority value - lower numbers have higher priority. Essential for email delivery.

TXT Record (Text Record)

Holds arbitrary text data. Commonly used for domain verification (proving ownership), SPF records (email authentication), DKIM keys (email signing), and DMARC policies.

NS Record (Name Server)

Specifies the authoritative name servers for the domain. These servers hold the definitive DNS records for the domain and respond to queries about it.

CNAME Record (Canonical Name)

Creates an alias that points to another domain name (the canonical name). Example: www.example.com · example.com. Cannot coexist with other records for the same name.

SOA Record (Start of Authority)

Contains administrative information about the zone, including the primary name server, email of the domain administrator, zone serial number, and timing parameters for zone transfers.

PTR Record (Pointer Record)

Used for reverse DNS lookups - translating an IP address back to a domain name. Important for email deliverability and security verification.

Understanding TTL (Time to Live)

TTL is a value in DNS records that indicates how long (in seconds) a DNS resolver should cache the record before requesting a fresh copy from the authoritative server.

Low TTL (60-300 seconds): Changes propagate quickly. Useful during migrations or when IP addresses change frequently. Increases load on name servers.
High TTL (3600-86400 seconds): Reduces DNS query load and improves performance. Changes take longer to propagate. Suitable for stable configurations.

When changing DNS records, it's common to first lower the TTL, wait for the old TTL to expire, make the change, then restore the original TTL.

How DNS Affects Website Access

DNS plays a critical role in website availability and performance:

Availability: If DNS resolution fails, users cannot reach your website even if the server is running. DNS outages effectively take websites offline.
Performance: DNS lookup time adds to page load time. Using geographically distributed DNS servers and appropriate caching reduces this latency.
Load balancing: Multiple A records for the same domain can distribute traffic across servers. More sophisticated setups use DNS-based load balancing services.
Failover: DNS can route traffic to backup servers when primary servers fail, though propagation delays limit response time.

DNS and Email Delivery

DNS records are crucial for email to work correctly:

MX Records: Tell sending servers which mail servers accept email for your domain and in what priority order.
SPF (via TXT): Specifies which IP addresses are authorized to send email on behalf of your domain. Helps prevent email spoofing.
DKIM (via TXT): Publishes public keys used to verify email signatures, proving messages weren't tampered with in transit.
DMARC (via TXT): Defines how receivers should handle emails that fail SPF or DKIM checks and where to send reports.
PTR Records: Reverse DNS that maps your mail server's IP back to a hostname. Many receiving servers check this and may reject email if it's missing or mismatched.

Why People Perform DNS Lookups

Troubleshooting: Diagnosing why a website or email isn't working correctly
SEO analysis: Understanding a site's infrastructure, CDN usage, and hosting provider
Security research: Investigating domains for malicious activity or verifying legitimacy
Competitive intelligence: Identifying what services and infrastructure competitors use
Domain verification: Confirming DNS changes have propagated after updates
Email deliverability: Checking SPF, DKIM, and DMARC records to diagnose email issues

Frequently Asked Questions

Why are my DNS changes not showing up?

DNS changes take time to propagate due to caching. The previous TTL value determines how long old records are cached by DNS resolvers worldwide. Propagation can take anywhere from a few minutes to 48 hours, depending on the original TTL. You can try flushing your local DNS cache, using a different DNS resolver (like 8.8.8.8 or 1.1.1.1), or checking propagation status with online tools.

What is the difference between DNS and a domain registrar?

A domain registrar is the company where you purchase and register domain names (like GoDaddy, Namecheap, or Cloudflare). DNS is the technical system that translates those domain names to IP addresses. While registrars often provide DNS hosting, you can use separate DNS providers. The registrar controls who owns the domain; DNS controls where the domain points.

Can I have multiple A records for the same domain?

Yes, you can have multiple A records pointing to different IP addresses. This is called DNS round-robin and provides basic load distribution. DNS resolvers will return all records, and clients typically try them in order or randomly. However, this is not true load balancing as it doesn't account for server health or load. For production systems, dedicated load balancers are recommended.

What happens if DNS servers go down?

If all authoritative DNS servers for a domain become unreachable, new DNS queries will fail, effectively making the website inaccessible to new visitors. Cached records will continue to work until they expire (based on TTL). This is why most domains have multiple NS records pointing to different name servers, often in different geographic locations. Redundancy is essential for critical domains.

How do DNS blocking and filtering work?

DNS blocking works by configuring DNS resolvers to return false or empty results for specific domains. When a blocked domain is queried, the resolver returns an error or a different IP (like a block page). ISPs, governments, and organizations use this for content filtering. Users can bypass DNS-based blocking by using alternative DNS resolvers or DNS-over-HTTPS (DoH), though other blocking methods may still apply.

What is DNSSEC and why does it matter?

DNSSEC (DNS Security Extensions) adds cryptographic signatures to DNS records, allowing resolvers to verify that responses haven't been tampered with. Without DNSSEC, attackers can potentially poison DNS caches or intercept queries to redirect users to malicious sites. DNSSEC provides authentication and integrity but not encryption - it proves records are authentic but doesn't hide what domains you're looking up.

Need Proxies for Web Scraping?

Access any website from any location with our residential proxies.

Get Started Now