Examples:
What is DNS?
The Domain Name System (DNS) is often called the "phonebook of the internet." It translates human-readable domain names (like google.com) into IP addresses (like 142.250.80.46) that computers use to identify each other on the network. Without DNS, you would need to memorize numerical IP addresses for every website you want to visit.
When you type a domain name into your browser, a DNS query is sent to resolve that name into an IP address. This process happens in milliseconds and involves multiple DNS servers working together to find the correct address. Our DNS lookup tool lets you see all the DNS records associated with any domain.
Types of DNS Records
A Record
Maps a domain name to an IPv4 address. This is the most fundamental DNS record type, directing web traffic to the correct server.
AAAA Record
Maps a domain to an IPv6 address. As IPv6 adoption grows, more domains are adding AAAA records alongside their A records.
MX Record
Specifies the mail servers responsible for receiving email for the domain. Priority values determine which server to try first.
NS Record
Identifies the authoritative name servers for a domain. These servers hold the official DNS records for the domain.
CNAME Record
Creates an alias from one domain to another. Commonly used for subdomains like "www" to point to the main domain.
TXT Record
Stores text information for various purposes including SPF (email authentication), DKIM, domain verification, and custom data.
Why Use DNS Lookup?
Troubleshoot Email Issues
Check MX records to verify email routing, diagnose delivery problems, and ensure mail servers are correctly configured for your domain.
Verify Domain Configuration
Confirm that DNS records are set up correctly after making changes, ensuring your website, email, and other services are properly configured.
Check DNS Propagation
After making DNS changes, use lookup tools to verify that updates have propagated across DNS servers worldwide.
Security Analysis
Examine TXT records for SPF, DKIM, and DMARC configurations that protect against email spoofing and phishing attacks.
Migration Planning
Document existing DNS records before migrating domains to a new registrar or hosting provider to ensure nothing is lost.
Competitive Research
Discover what hosting providers, CDNs, and email services competitors use by examining their DNS records.
Frequently Asked Questions
How long does DNS propagation take?
DNS propagation typically takes anywhere from a few minutes to 48 hours, though it usually completes within 24 hours. The time depends on several factors:
- TTL (Time To Live): This value tells DNS servers how long to cache records. Lower TTL values mean faster propagation.
- ISP caching: Your Internet Service Provider may cache DNS records for varying periods.
- Geographic distribution: Updates spread across global DNS servers at different rates.
Before making critical DNS changes, consider lowering your TTL values 24-48 hours in advance to speed up propagation.
What is the difference between A and CNAME records?
A records directly map a domain name to an IP address. They're used at the root domain level (like example.com) and are essential for directing traffic to your server.
CNAME records create an alias that points one domain to another domain name (not an IP). They're commonly used for subdomains (like www.example.com pointing to example.com).
Key differences:
- A records point to IP addresses; CNAMEs point to domain names
- Root domains (@) cannot use CNAMEs (use A or ALIAS records instead)
- CNAMEs require an additional DNS lookup, slightly increasing latency
- CNAMEs are useful when IP addresses may change (like with CDN services)
Why is my website not working after changing DNS?
Common reasons your website might not work after DNS changes:
- Propagation not complete: DNS changes haven't spread to all servers yet. Wait 24-48 hours.
- Browser cache: Try clearing your browser cache or using incognito mode.
- Local DNS cache: Flush your computer's DNS cache (ipconfig /flushdns on Windows, sudo dscacheutil -flushcache on Mac).
- Incorrect record: Double-check that you entered the correct IP address and removed any trailing periods.
- SSL certificate: If switching servers, the new server may need SSL certificates configured.
Use our DNS lookup tool to verify what records are currently being served for your domain.
What are SPF, DKIM, and DMARC records?
These are email authentication protocols stored in TXT records that help prevent email spoofing:
- SPF (Sender Policy Framework): Specifies which mail servers are authorized to send email for your domain. Receiving servers check SPF records to verify sender legitimacy.
- DKIM (DomainKeys Identified Mail): Adds a digital signature to outgoing emails, allowing recipients to verify the message wasn't altered in transit.
- DMARC (Domain-based Message Authentication): Tells receiving servers what to do with emails that fail SPF or DKIM checks (reject, quarantine, or accept).
Implementing all three significantly improves email deliverability and protects your domain from being used in phishing attacks.
Can I have multiple A records for one domain?
Yes, you can have multiple A records pointing to different IP addresses for the same domain. This is called "round-robin DNS" and is commonly used for:
- Load balancing: Distribute traffic across multiple servers
- Redundancy: If one server fails, traffic goes to others
- Geographic distribution: Direct users to nearby servers
DNS servers typically rotate through the available IPs, providing basic load distribution. However, for more sophisticated load balancing, consider using a CDN or dedicated load balancer.