DIAGNOSTICS / SKY FREE TOOLS

DNS Record Lookup

Look up public DNS answers and distinguish missing records from lookup failures.

01 / INPUT

What does DNS actually return?

STEP 01
PTR accepts an IPv4 or IPv6 address; other types accept a domain.
Enter a domain, not a URL or email address.

This check reads public DNS through Sky’s fixed resolver. It does not receive a message or change a record.

Your DNS query is sent to Sky’s server and its fixed public resolver to complete the lookup. It is not added to tool history. Ordinary hosting access logs may still exist.

NEXT / INTERPRET THE EVIDENCE

Use this result with the sending path, receiver response and authorized provider signals—not as a stand-alone placement verdict.

Explore the Signal Lab
GUIDE / UNDERSTAND YOUR RESULT

How to read your DNS Record Lookup result

DNS Record Lookup shows what a public recursive resolver returns for a name and record type at lookup time. Use it to inspect mail routing or reverse DNS, not as a complete email-delivery test.

Reading the result, step by step

  1. Choose the record type

    Select TXT, MX, A, AAAA, CNAME, NS, or PTR. For PTR, enter an IPv4 or IPv6 address. For other types, enter a domain or DNS name, not a URL or email address.

  2. Read the query details

    The result lists Queried name, Record type, Resolver, and Lookup time. PTR results also show Input address. The queried name for PTR is the reverse-DNS name derived from the address.

  3. Interpret records found

    Records found means the query returned answers, shown below the summary. MX lines show a preference number and mail-host name. When there are multiple MX records, lower preference numbers are tried first.

  4. Separate missing data from errors

    No matching record is a warning: the name exists, but this type returned no answer. Name does not exist (NXDOMAIN) is an error. DNS lookup timed out or DNS lookup unavailable means no conclusion can be drawn; try again later.

Common problems and how to fix them

The MX lookup says No matching record.

Usual cause: The name exists but returned no MX answer. The domain may use other routing, or the wrong name or setup may have been checked. SMTP permits an implicit MX pointing to the domain itself when no MX records exist.

Fix: Check the exact recipient domain and the mail provider's DNS instructions. If an MX host is intended, publish the provider-specified records with the DNS operator, then check again.

The result says Name does not exist (NXDOMAIN).

Usual cause: The resolver reports that the queried name does not exist. A misspelling, wrong subdomain, or incorrect DNS delegation can cause this result.

Fix: Confirm the name and intended domain. If correct, ask the DNS host to check the zone and delegation rather than publishing a record under a different name.

A PTR query returns No matching record.

Usual cause: The reverse-DNS zone may have no PTR record, or the query may use an IP other than the actual outbound public address. The IP provider usually controls reverse DNS.

Fix: Confirm the sending IP with the mail administrator or provider. Ask the IP owner to configure its PTR hostname, then query that address again.

A PTR record exists, but forward DNS does not match.

Usual cause: A PTR answer names a host but does not prove it points back to the sending IP. Gmail calls for the hostname's A or AAAA record to resolve to that same public IP. Spamhaus also expects the HELO/EHLO hostname to resolve to the connecting IP.

Fix: Query A for an IPv4 sender or AAAA for IPv6 using the PTR hostname. Ask the IP and DNS operators to align the address records, reverse name, and server HELO/EHLO name.

The result says DNS lookup timed out or DNS lookup unavailable.

Usual cause: The recursive lookup did not complete. This is not evidence that a record is missing; the resolver or network may have a temporary problem.

Fix: Retry later. If it continues, ask the DNS operator to compare the authoritative answer with the public resolver's result.

Example: Follow a PTR answer back to its address

PTR lookup: 192.0.2.10 returns mail.example.com. A lookup: mail.example.com returns 192.0.2.10.

The PTR names a host, and the forward A answer points back to the queried IPv4 address. That is a forward-confirmed reverse DNS match in this example. The tool makes separate queries, so compare the values yourself; this match alone does not verify a message or its placement.

Frequently asked questions

How do I check a PTR record?

Choose PTR and enter the sending server's public IP. The tool converts it to a reverse-DNS name and shows any PTR hostname returned. Confirm the IP first; its owner controls the reverse zone.

What is forward-confirmed reverse DNS?

The IP has a PTR hostname, and that hostname's A or AAAA record resolves to the same IP. Check PTR, then look up the returned hostname's matching address type. A PTR answer alone is not confirmation.

Why does an MX lookup return nothing?

The name may have no MX answer, or the wrong domain may have been queried. SMTP allows an implicit MX to the domain itself when the MX list is empty. Check the domain and provider instructions before changing DNS.

What is the difference between NXDOMAIN and no answer?

No matching record means the name exists but has no answer for this type. NXDOMAIN means the resolver reports that the name does not exist. Timeout or unavailable means the lookup did not complete.