Free DNS Lookup — Check DNS Records Online

What Is a DNS Lookup?

A DNS lookup is the fundamental process by which a human-readable domain name, like miip.link, is translated into a numeric IP address that computers can understand, like 104.21.50.120. This translation system is essential for the Internet to function — without it, we would have to memorize numeric IP addresses for every website we want to visit.

DNS (Domain Name System) works like a giant, distributed phone book for the Internet. When you type a web address into your browser, your device needs to know which server to connect to, and DNS provides that information. A DNS lookup tool lets you examine these records directly, which is invaluable for system administrators, web developers, and anyone who needs to verify a domain's DNS configuration.

Performing a DNS lookup is one of the first diagnostic tasks when a website isn't working properly, when setting up new email services, or when migrating a domain to a new hosting provider. With miip.link's DNS lookup tool, you can check any domain quickly and for free without installing additional software.

DNS Record Types

The DNS system contains several record types, each with a specific function. Understanding these records is essential for properly managing any domain and troubleshooting connectivity issues. Here are the most important types:

A Record (Address)

The A record is the most basic and essential DNS type. It maps a domain name to a 32-bit IPv4 address. For example, the A record for miip.link might point to 104.21.50.120. Every domain must have at least one A record to be accessible via IPv4. It's possible to have multiple A records for the same domain, which is used for load balancing by distributing traffic across multiple servers.

AAAA Record (IPv6)

The AAAA record serves the same function as the A record, but for 128-bit IPv6 addresses. As IPv4 addresses become exhausted, IPv6 becomes increasingly important. An AAAA record allows a domain to be accessible via IPv6 connections, which is essential for future compatibility and for networks that only support IPv6.

CNAME Record (Canonical Name)

The CNAME record creates an alias by pointing a subdomain to another domain. It's useful when multiple services point to the same server. For example, www.miip.link can be a CNAME pointing to miip.link, so if the IP address changes, you only need to update the main A record. CNAME records cannot coexist with other records on the same subdomain.

MX Record (Mail Exchange)

MX records direct incoming email to the correct mail servers. Each MX record includes a numeric priority: lower values have higher priority. For example, an MX record with priority 10 is tried first, and if it fails, the one with priority 20 is tried. This provides redundancy and ensures email delivery.

TXT Record (Text)

TXT records store arbitrary text and have become essential tools for email security and domain verification. The most common uses include SPF (Sender Policy Framework) to prevent spam, DKIM (DomainKeys Identified Mail) to digitally sign emails, and DMARC for authentication policies. They are also used to verify domain ownership with services like Google Search Console.

NS (Name Server) and SOA (Start of Authority) Records

NS records indicate which name servers are authoritative for a domain. When you perform a DNS lookup, these servers have the definitive answer. The SOA record contains administrative information about the DNS zone: the primary server, the administrator's email, the serial number, refresh and expiration times. The SOA serial number is incremented each time the DNS zone is modified, which is crucial for secondary servers to know when to update their data.

How to Use the DNS Lookup Tool

miip.link's DNS lookup tool is designed to be simple and efficient. Follow these steps to look up DNS records for any domain:

• Step 1: Enter the domain name you want to look up in the text field, for example google.com or miip.link.
• Step 2: Select the DNS record type you want to query: A, AAAA, CNAME, MX, TXT, NS or SOA.
• Step 3: Click the "Look Up DNS" button and you'll get the results instantly.

The tool queries DNS servers in real time, showing up-to-date results without relying on intermediate caches. This is especially useful when you've just modified DNS records and need to verify that the changes are already visible. You can also use the tool directly from the miip.link home page in the Network Tools section.

Common DNS Errors and How to Fix Them

DNS problems are one of the most frequent causes of website inaccessibility. Here are the most common errors and how to resolve them:

• Domain doesn't resolve (NXDOMAIN): The domain doesn't exist in DNS or the records were deleted. Verify that the domain is registered and that its NS records point to the correct name servers.
• A record points to wrong IP: The domain resolves to an incorrect IP address. Use the DNS lookup tool to check the A record and compare it with your server's expected IP.
• Incomplete propagation: DNS changes aren't visible everywhere. This is normal after a change; propagation can take up to 48 hours. Query from different DNS servers to check progress.
• Mail server not receiving messages: Verify that MX records point to valid mail servers and that SPF and DKIM records are properly configured.
• SSL certificate error: If the CNAME points to a domain different from the certificate, the browser will show a security error. Make sure the CNAME and SSL certificate are compatible.

DNS Propagation: How Long Does It Take?

DNS propagation is the time it takes for changes in DNS records to become visible to all Internet users. This process is not instantaneous due to the distributed and hierarchical nature of the DNS system. When you modify a DNS record at your provider, the update must propagate through multiple cache levels in the Internet infrastructure.

The main factor determining propagation speed is the TTL (Time To Live) configured on each record. TTL tells intermediate DNS servers how long to cache the response before querying again. A TTL of 3600 seconds (1 hour) means servers can cache the response for up to one hour. For planned changes, a good practice is to lower the TTL to a low value (like 300 seconds) 24-48 hours before the change, make the modification, and then restore the TTL to its normal value.

In practice, most changes propagate within 1-4 hours, although some DNS providers like Cloudflare propagate changes almost instantly. Changes to name servers (NS records) can take up to 48 hours because NS records typically have high TTLs by design. Use miip.link's DNS lookup tool to monitor propagation progress by querying from different servers.

DNS Caching: Understanding Cache Memory

DNS caching exists at multiple levels of the Internet infrastructure and is what makes web browsing fast. Without caching, every visit to any website would require a full DNS query, adding significant latency. The cache levels include:

• Browser cache: Browsers store DNS responses locally. Chrome stores up to 1000 entries with TTL of up to 60 seconds. You can clear this cache with chrome://net-internals/#dns.
• Operating system cache: Your computer maintains its own DNS cache. On macOS, clear it with sudo dscacheutil -flushcache and on Windows with ipconfig /flushdns.
• DNS resolver cache: Your ISP or DNS provider (like Cloudflare 1.1.1.1 or Google 8.8.8.8) maintains a massive cache. These resolvers typically honor the configured TTLs.
• TLD server cache: Top-level domain servers (.com, .net, etc.) also maintain caches with generally long TTLs.

When a DNS change doesn't seem to have propagated, the culprit is usually one of these cache levels. Using miip.link's DNS lookup tool lets you query authoritative servers directly, bypassing intermediate caches and showing the most recent data available.