Skip to main content

​
Getting Started

DNS Checker is designed to be simple and straightforward to use.

Open DNS Checker

Start checking DNS records now

​
Basic DNS Query

Perform a simple DNS lookup in three easy steps:
1

Enter Domain Name

Type the domain you want to query (e.g., example.com)
2

Select Record Type

Choose the DNS record type (A, AAAA, MX, CNAME, TXT, etc.)
3

Click Check

Hit the “Check DNS” button to query all resolvers

​
Understanding Results

DNS Checker displays results from multiple resolvers:
Reading Results Each result shows: - Resolver name (Google DNS, Cloudflare, etc.) - Record value(s) found - Time-To-Live (TTL) - Query response time

​
Common DNS Record Types

IPv4 Address RecordMaps a domain name to an IPv4 address.Example:
example.com → 93.184.216.34
When to use: Checking where a domain points to
IPv6 Address RecordMaps a domain name to an IPv6 address.Example:
example.com → 2606:2800:220:1:248:1893:25c8:1946
When to use: Verifying IPv6 connectivity
Mail Exchange RecordSpecifies mail servers for a domain.Example:
example.com → 10 mail.example.com
When to use: Troubleshooting email delivery issues
Canonical Name RecordAliases one domain to another.Example:
www.example.com → example.com
When to use: Verifying subdomain redirects or CDN setup
Text RecordStores text information, often for verification or email authentication.Example:
example.com → "v=spf1 include:_spf.google.com ~all"
When to use: Checking SPF, DKIM, DMARC, or domain verification
Nameserver RecordSpecifies authoritative nameservers for a domain.Example:
example.com → ns1.example.com, ns2.example.com
When to use: Verifying nameserver delegation

​
Use Case Examples

​
1. Verifying DNS Propagation

Scenario: You just changed your DNS records and want to verify propagation.
1

Query Original Record

Check the old DNS value across all resolvers
2

Make DNS Change

Update your DNS records at your registrar
3

Monitor Propagation

Re-query every few minutes to see which resolvers have updated
4

Verify Completion

Once all resolvers show the new value, propagation is complete
DNS propagation can take anywhere from a few minutes to 48 hours depending on TTL values.

​
2. Troubleshooting Email Issues

Scenario: Emails aren’t being delivered to your domain.
1

Check MX Records

Query MX records to verify mail server configuration
2

Verify SPF Record

Check TXT records for SPF configuration
3

Check DMARC

Look for_dmarc.yourdomain.com TXT record
4

Validate DKIM

Check for DKIM TXT records if applicable

​
3. Debugging Website Connectivity

Scenario: Your website isn’t accessible.
1

Check A Records

Verify A record points to correct IP address
2

Check AAAA Records

If using IPv6, verify AAAA records
3

Verify NS Records

Ensure nameservers are correct
4

Compare Resolvers

Check if issue is resolver-specific or global

​
Understanding TTL

Time-To-Live (TTL) determines how long DNS records are cached:
Short TTL (300-600s): - Faster propagation of changes - More DNS queries (higher load) - Good during migrations - Useful for testing
Long TTL (3600s-86400s): - Slower propagation of changes - Fewer DNS queries (less load) - Better for stable infrastructure - Standard for production
Lower the TTL 24-48 hours before making DNS changes to ensure faster propagation.

​
Tips for Effective DNS Checking

Best Practices: - Check multiple record types - Compare all resolvers - Note TTL values - Document current values before changes - Wait for TTL to expire before expecting changes
Common Mistakes: - Not waiting for TTL expiry - Only checking one resolver - Forgetting about browser DNS cache - Not verifying subdomain records - Ignoring trailing dots in domain names

​
Advanced Queries

​
Querying Subdomains

www.example.com
blog.example.com
api.example.com

​
Checking Email Records

# MX Records
example.com (type: MX)

# SPF Record
example.com (type: TXT, look for "v=spf1")

# DMARC Record
_dmarc.example.com (type: TXT)

# DKIM Record
default._domainkey.example.com (type: TXT)

​
Reverse DNS Lookup

# PTR Record (use IP address)
34.216.184.93 (reverse lookup)

​
Troubleshooting

Possible causes:
  • Domain doesn’t exist
  • Record type doesn’t exist for domain
  • DNS not yet propagated
  • Typo in domain name
Solution: Double-check domain spelling and try a different record type
Possible causes:
  • DNS propagation in progress
  • Resolver-specific caching
  • Geolocation-based DNS
Solution: Wait for TTL to expire and re-query
Possible causes:
  • Network connectivity issues
  • DNS resolver temporarily unavailable
  • Firewall blocking DNS queries
Solution: Try again or use a different network

​
Frequently Asked Questions

Typically 5 minutes to 48 hours, depending on TTL values. Most changes propagate within a few hours.
This usually indicates DNS propagation is in progress. Different resolvers cache records based on their own TTL expiry.
DNS Checker queries from the server location. For geographic diversity, the multiple resolvers provide global coverage as they have servers worldwide.
No, DNS Checker doesn’t log or store your queries. All queries are performed in real-time and results are not saved.

​
Next Steps

Explore Features

Learn about all DNS Checker capabilities

Start Checking

Try DNS Checker now