How to Check DNS Records for a Domain

1. Open the DNS checker. Go to enterno.io/en/dns.
2. Enter a domain. Without www. or scheme (https://). Example: enterno.io or subdomain.example.com.
3. Pick record types. Default: all. You can specify individual ones: A, MX, TXT for a quick check.
4. Click "Check". Result: a table of every found record with TTL and MX priority.
5. Check propagation. For DNS change monitoring, use the DNS Propagation Checker — from 15+ global resolvers.

Open tool →

DNS (Domain Name System) records are essential components of the internet's infrastructure, facilitating the translation of human-friendly domain names into machine-readable IP addresses. Here’s a breakdown of the most common DNS record types:

• A Record: Maps a domain name to its corresponding IPv4 address. For example, example.com A 192.0.2.1.
• AAAA Record: Similar to A records but for IPv6 addresses. For example, example.com AAAA 2001:db8::1.
• MX Record: Specifies the mail servers for receiving emails. For instance, example.com MX 10 mail.example.com.
• NS Record: Indicates the authoritative name servers for a domain. For example, example.com NS ns1.example.com.
• TXT Record: Allows for arbitrary text data to be associated with a domain, often used for verification and policy purposes. Example: example.com TXT "v=spf1 include:_spf.example.com ~all".
• SOA Record: Provides information about the zone, such as the primary name server and the email of the domain administrator. Example: example.com SOA ns1.example.com admin.example.com 2023031501 7200 3600 1209600 86400.
• CAA Record: Specifies which certificate authorities are allowed to issue certificates for the domain. For example, example.com CAA 0 issue "letsencrypt.org".

Understanding these records is crucial for effective domain management and troubleshooting DNS-related issues.

For those who prefer command line interfaces, several tools can help you check DNS records effectively. Here are some practical commands for different operating systems:

• Linux/MacOS: Use the dig command. For example, to check the A record:
dig example.com A
• To check MX records:
dig example.com MX
• For a more detailed overview including all record types:
dig example.com ANY

Windows: Use the nslookup command. To check an A record:

For MX records:

To check all records:

These commands provide quick access to DNS information directly from your terminal, making it easier to diagnose issues or gather data.

DNS issues can manifest in various ways, affecting website accessibility and email delivery. Here are some common problems and how to troubleshoot them:

• Domain Not Resolving: If a domain isn't resolving, check the NS records to ensure that they point to the correct name servers. Use dig example.com NS to verify.
• Incorrect IP Address: If your domain resolves to the wrong IP address, check the A and AAAA records. Use dig example.com A or dig example.com AAAA to confirm the records.
• Email Not Delivering: If emails are bouncing back, verify the MX records. Ensure they are set correctly by running dig example.com MX. Also, check the SPF records in the TXT records to ensure they're configured properly.
• Propagation Delays: After making DNS changes, remember that it can take time for changes to propagate. Check the TTL (Time to Live) settings in the SOA record using dig example.com SOA.

By systematically checking these records and configurations, you can diagnose and resolve most common DNS issues efficiently.