DNS lookup

Domain Name System Resolution and Infrastructure Auditing

The DNS Lookup tool queries global recursive and authoritative nameservers to resolve and display active Domain Name System (DNS) resource records. Operating in accordance with RFC 1035, the tool queries essential record types including A (IPv4 host addresses), AAAA (IPv6 addresses), CNAME (canonical aliases), MX (mail exchange servers), TXT (SPF, DKIM, DMARC, and domain verification strings), NS (authoritative nameservers), and SOA (start of authority). Rapid DNS queries help network engineers and webmasters verify migration propagation, diagnose email deliverability failures, and audit infrastructure redundancy.

Worked Example: Full Zone Resolution

Executing a multi-record query against byoviral.com illustrates how distinct records govern separate digital services:

Target Domain: byoviral.com

Returned record breakdown:

• A Records: The IPv4 addresses browsers connect to, each with a Time to Live (TTL) such as 300 seconds. For a site behind a CDN such as Cloudflare these are the CDN's edge addresses, not the origin server.
• NS Records: The authoritative nameservers for the zone. A domain using Cloudflare DNS, for example, lists two *.ns.cloudflare.com hosts.
• MX Records: Designates mail server hostnames and priority weights, ensuring inbound business correspondence routes to proper mailboxes.
• TXT Records: Returns security policies including SPF records (v=spf1 ...) that declare authorized mail sending servers to prevent domain spoofing.

Frequent DNS Configuration Mistakes

DNS errors can cause catastrophic service outages and silent email delivery failures:

• CNAME at the zone apex: RFC specifications prohibit a CNAME record from coexisting with other record types on the same host label. Placing a CNAME on the apex root domain (domain.com) breaks MX, NS, and SOA records. Use ALIAS, ANAME, or direct A records at the apex instead.
• Excessively high TTL values before migrations: Setting a high TTL (such as 86,400 seconds / 24 hours) means client resolvers cache old IP addresses for a full day after a server move. Lower TTL values to 300 seconds several days before planned server migrations.
• Multiple SPF TXT records: Publishing more than one SPF TXT record on a single domain invalidates SPF evaluation under RFC 7208, causing email providers like Gmail and Microsoft 365 to flag transactional emails as spam. Combine all rules into a single SPF record.
• Missing glue records: When nameservers share the same domain name they serve (e.g., ns1.domain.com for domain.com), missing glue records at the registrar level cause cyclic dependency failures that make the domain unreachable.

Connected Infrastructure Diagnostics

To view registrar information, lifecycle status codes, and domain expiration deadlines, inspect the domain with our WHOIS Lookup. To verify reverse PTR mapping from a server IP back to a verified hostname, use the Reverse IP Lookup. To confirm website availability across global edge nodes, check the Website Status Checker.