DNS Lookup Tool

Query DNS Records from Domain Names in Real-Time

Free online DNS lookup tool. Simply enter a domain name to instantly query DNS records including A records (IPv4), AAAA records (IPv6), MX records (mail servers), TXT records, NS records (nameservers), CNAME records, and SOA records. Perfect for DNS configuration verification, troubleshooting, mail server validation, and nameserver change confirmation.

How to Use

Query DNS records in 3 simple steps:

Step 1: Enter Domain Name
Enter the domain name you want to query (e.g., example.com). You can search both root domains (without www) and subdomains (www.example.com, mail.example.com, etc.).
Step 2: Select Record Types
Select the DNS record types you want to query. Choose from A (IPv4 address), AAAA (IPv6 address), MX (mail server), TXT (text information), NS (nameserver), CNAME (alias), and SOA (authority info). Main record types are selected by default.
Step 3: Perform Lookup
Click the 'DNS Lookup' button to retrieve and display DNS information for the selected record types in real-time. You can view each record's value and TTL (Time To Live).

All DNS lookups are performed in real-time. Entered domain names are not stored on the server.

DNS Lookup Tool

Domain Name

Record Types to Query

A (IPv4)

AAAA (IPv6)

MX (Mail)

TXT (Text)

NS (Nameserver)

CNAME (Alias)

SOA (Authority)

Practical Use Cases

DNS Lookup tool can be utilized in various scenarios:

1. Email Configuration Troubleshooting

When email sending/receiving fails, you can check MX records to verify mail server configuration is correct. You can also check the priority of multiple MX records and understand email delivery routes. Useful for checking SPF records (within TXT records) and DKIM configurations. Example: Query MX records for example.com to verify 'mail.example.com' is correctly configured.

2. Domain Transfer and DNS Migration Verification

When migrating a domain to a new hosting service, you can verify A, AAAA, and NS records to confirm DNS has switched correctly. Also useful for checking DNS propagation status to servers worldwide. By viewing TTL values, you can predict how long it will take for DNS changes to fully propagate.

3. Subdomain Configuration Verification

When creating new subdomains (blog.example.com, shop.example.com, etc.), you can verify A or CNAME records are correctly configured. Also useful for validating CDN settings or CNAME configurations to load balancers. Convenient for verifying when different IP addresses or servers are specified for each subdomain.

4. Nameserver Change Validation

When changing domain nameservers, you can query NS records to confirm the switch to new nameservers is successful. You can verify that registrar nameserver settings match DNS query results, allowing early detection of configuration errors. You can also check nameserver redundancy.

5. Security and Authentication Settings Verification

Query TXT records to verify email security settings like SPF (Sender Policy Framework for mail server authentication), DKIM (email signatures), and DMARC (email authentication policy). Also useful for verifying Google Search Console or Google Workspace authentication TXT records, and SSL certificate CAA (Certification Authority Authorization) records.

What is DNS Lookup?

DNS Lookup is the process of resolving domain names to IP addresses or other DNS information. It's a fundamental mechanism for identifying servers from domain names on the Internet.

Types of DNS Records and Their Roles

DNS has multiple record types, each serving different purposes. **A records** convert domain names to IPv4 addresses (e.g., 192.0.2.1). **AAAA records** convert to IPv6 addresses (e.g., 2001:db8::1). **MX records** specify mail delivery destination servers with priority values. **TXT records** store arbitrary text information, used for authentication info like SPF, DKIM, DMARC, and domain ownership verification. **NS records** specify authoritative name servers for the domain. **CNAME records** define domain aliases. **SOA records** hold zone authority information (administrator, serial number, refresh interval, etc.).

Meaning of TTL (Time To Live)

TTL indicates how long (in seconds) a DNS record should be cached. For example, if TTL=3600, DNS resolvers cache that record for 3600 seconds (1 hour) without re-querying. Longer TTLs reduce DNS queries and improve performance, but slow down DNS change propagation. Before DNS migrations or server changes, setting short TTLs (e.g., 300 seconds = 5 minutes) speeds up change propagation. Conversely, stable services can set longer TTLs (e.g., 86400 seconds = 24 hours) to reduce DNS server load.

How DNS Lookup Works and Security

DNS Lookup follows a hierarchical structure: local resolver → root DNS server → TLD (Top-Level Domain) DNS server → authoritative DNS server. This tool sends DNS queries directly to specified domains and retrieves the latest information from authoritative servers. It doesn't complete in the browser alone; it uses server-side APIs like dns_get_record() to fetch DNS information in real-time. For domains supporting DNSSEC (DNS Security Extensions), signature verification prevents spoofed DNS responses. DNS Lookup tools are essential for verifying DNS configuration accuracy, troubleshooting, security auditing, and domain migration work.

Frequently Asked Questions

What is DNS Lookup?

DNS Lookup is the query process that converts domain names (like example.com) to IP addresses and other DNS information. This tool allows you to easily check various DNS records including A (IPv4), AAAA (IPv6), MX (mail), TXT, NS (nameserver), CNAME, and SOA. Used for DNS configuration verification, troubleshooting, and domain information investigation.

What's the difference between A records and AAAA records?

A records convert domain names to IPv4 addresses (e.g., 192.0.2.1). IPv4 is a 32-bit address system with about 4.3 billion addresses. AAAA records (quad-A) convert domain names to IPv6 addresses (e.g., 2001:db8::1). IPv6 is a 128-bit address system with virtually infinite address space, solving IPv4 address exhaustion. Modern websites often have both record types to support dual-stack environments.

What are MX records? How do they relate to email sending?

MX records (Mail Exchange Records) specify mail servers that receive email for that domain. You can set multiple MX records, each with a priority value. Lower numbers indicate higher priority, and mail is delivered first to high-priority servers. Example: if example.com has two MX records '10 mail1.example.com' and '20 mail2.example.com', mail1 is used preferentially, and if mail1 is down, it falls back to mail2. When email isn't being delivered, checking MX records is the first troubleshooting step.

What are TXT records used for?

TXT records store arbitrary text information about a domain. Main uses include: **SPF (Sender Policy Framework)**: validating mail sender server legitimacy, **DKIM (DomainKeys Identified Mail)**: email digital signatures, **DMARC (Domain-based Message Authentication, Reporting & Conformance)**: email authentication policy, **Domain ownership verification**: for Google Search Console, Google Workspace, SSL certificate issuance authentication, **Other configuration info**: site authentication tokens, service integration info, etc. Example SPF record: 'v=spf1 include:_spf.example.com ~all'

What's the relationship between NS records and nameservers?

NS records (Name Server Records) specify authoritative DNS servers (nameservers) for that domain. When registering a domain, setting nameservers at the registrar makes those nameservers manage DNS information. Typically, multiple nameservers (e.g., ns1.example.com, ns2.example.com) are set for redundancy. During domain transfers or hosting changes, NS records must be changed to new nameservers. After changes, propagation to DNS servers worldwide can take up to 48 hours.

When should CNAME records be used?

CNAME records (Canonical Name Records) define domain aliases. For example, if 'www.example.com' is set as a CNAME for 'example.com', www-prefixed access is handled correctly. Main uses: **Subdomain forwarding**: blog.example.com → hosting-provider.com, **CDN configuration**: cdn.example.com → cdn-provider.net, **Load balancers**: api.example.com → lb.cloud-provider.com. Cautions: CNAMEs cannot be set for root domains (example.com), only subdomains (www.example.com, etc.). Also, you cannot coexist CNAME with other records (A, MX, etc.) at the same name.

How long does it take for DNS query results to propagate?

Time for DNS changes to propagate worldwide is primarily determined by TTL (Time To Live). If TTL is 3600 seconds (1 hour), DNS resolvers cache old information for up to 1 hour. Setting short TTLs before DNS changes (e.g., 300 seconds = 5 minutes) speeds up post-change propagation. Typically, DNS changes propagate in minutes to hours, but some ISPs may take up to 48 hours. This tool allows you to immediately verify changes are correctly configured by querying authoritative DNS servers in real-time.

How does the DNS Lookup tool work?

This tool retrieves DNS information through these steps: 1) User specifies domain name and record types, 2) Browser sends request to PHP backend, 3) Server executes DNS queries using PHP functions like dns_get_record(), 4) Retrieves latest DNS information from authoritative DNS servers, 5) Formats results and returns to browser, 6) JavaScript displays results in user-friendly format. It doesn't complete in the browser; DNS queries are executed server-side for accurate, up-to-date information. Entered domain names are not logged, protecting privacy.