Network

Reverse DNS Lookup Guide: Read PTR Records and Fix Missing or Mismatched Names

·

A reverse DNS lookup asks which PTR names DNS publishes for an IP address. Enter one address in ToolMellow, choose Cloudflare or Google Public DNS, and read the returned status, hostnames and TTL values. The result can help you investigate an unfamiliar name in a log or check a reverse-DNS change.

The useful question is whether the expected DNS data is present and consistent. A PTR result does not identify a visitor, enumerate websites or prove that a service works. This guide explains how to read the query name and answer separately, when to ask the address provider for a change, and how to check forward DNS yourself.

Reverse DNS lookup

Enter an address and request its PTR records

Paste a bare IPv4 or IPv6 literal into IP address. Cloudflare is selected initially; choose Google Public DNS for that resolver’s view. Select Look up address. The page shows the normalized address, address family and scope, followed by the generated reverse-DNS name. For an address classified as public, it also shows DNS status and any returned PTR names with TTL values.

The field does not discover your current address automatically. Use What Is My IP if you need the address observed by this website, or DNS Checker if you are starting with a hostname. Changing the address or provider clears the old result and error. Choosing a provider alone does not send another query; submit again to obtain its answer.

  • Use one address without a URL, port, CIDR prefix or zone identifier.
  • Read DNS status together with the PTR list; an empty list can have several causes.
  • Keep the normalized address, provider, check time and status with any troubleshooting note.

RFC 1035: PTR records, reverse names, DNS responses and TTLRFC 3596: IPv6 reverse lookup under ip6.arpa

Supply a literal within the input limit

The input limit is 80 UTF-16 code units, checked before surrounding whitespace is trimmed. Valid literal characters are ASCII, but padding still uses the allowance. IPv4 requires four decimal octets without leading zeroes. URLs, hostnames, address lists, brackets, network suffixes such as /64 and zone identifiers such as %eth0 are rejected. An unbracketed IPv6 address ending in :80 can be a valid literal; its final digits are not automatically a port.

IPv6 spelling is normalized, so 2001:0DB8:0:0:0:0:0:1 becomes 2001:db8::1. IPv4-mapped forms such as ::ffff:192.0.2.1 and ::ffff:c000:201 become 192.0.2.1, with IPv4 family and reverse-name rules. Other IPv6 forms are not all converted into IPv4. These documentation addresses illustrate parsing and naming; the tool does not send them to a public resolver.

Node.js: Literal IP parsing and IPv4 leading-zero restrictionsRFC 4291: IPv6 text and IPv4-mapped address formsIANA: IPv4 special-purpose address registryIANA: IPv6 special-purpose address registry

Separate the reverse query name from the returned hostname

The reverse query name identifies where DNS looks for a PTR record. IPv4 reverses the four octets and appends in-addr.arpa: 192.0.2.1 produces 1.2.0.192.in-addr.arpa. That name can be generated whether or not any record exists. Seeing it on the page does not establish a successful reverse lookup.

IPv6 uses ip6.arpa. Expand the address to 32 hexadecimal digits, reverse each individual digit, separate them with dots and append the suffix. Reversing whole hextets is incorrect. The table uses reserved examples and a fictional hostname; it does not report a live lookup. A final dot in a returned DNS name marks an absolute name, rather than being part of a website address.

Separate the reverse query name from the returned hostname
ValueRoleHow to interpret it
192.0.2.1Illustrative input addressA documentation address; no public query is made here.
1.2.0.192.in-addr.arpaGenerated IPv4 reverse nameThis is the name queried for PTR, not the resulting hostname.
32 reversed hexadecimal digits + ip6.arpaIPv6 reverse-name constructionReverse individual digits, including expanded zeroes.
ptr.example.Fictional PTR targetA returned target would be DNS data to investigate, not identity proof.

RFC 1035: PTR records, reverse names, DNS responses and TTLRFC 3596: IPv6 reverse lookup under ip6.arpa

Read every PTR row without assuming there must be only one

DNS permits multiple PTR records at the same name. ToolMellow displays each PTR answer row that passes its response checks, with the returned TTL in seconds. It does not choose a preferred hostname or discover all services using the address. A single name can be a provider’s default label, while several names still do not form a complete inventory of hosted websites.

RFC 2181 distinguishes a PTR target from aliases encountered while finding that record: the PTR target must be a canonical name rather than a CNAME alias. The tool displays the returned data; it does not perform a separate target-validation or forward-resolution check. A displayed hostname may be stale or misleading, so verify the specific property your task depends on.

RFC 2181: Multiple PTR records and canonical targetsRFC 1035: PTR records, reverse names, DNS responses and TTL

Use DNS status to explain an empty PTR list

NXDOMAIN reports that a DNS name, possibly a final alias target, does not exist in the response. It does not say that the IP is unassigned or the host is offline. NODATA means the requested type is absent from a successful DNS response; it is not a separate DNS response code. ToolMellow assigns that label to code-zero replies with no PTR answer and an SOA authority record.

For the remaining code-zero replies without PTR, the parser checks for a CNAME answer before an NS authority record, then falls back to EMPTY_ANSWER. The table’s interpretation labels describe the accepted response, not a complete diagnosis of the reverse zone. The page displays PTR rows, but does not expose the authority section, a full alias trace or a DNSSEC-validation indicator.

Use DNS status to explain an empty PTR list
StatusMeaning hereNext step
NOERROR with PTR rowsThe accepted DNS reply contains PTR answers.Inspect each name and separately check forward DNS if needed.
NXDOMAINThe response reports a nonexistent DNS name.Check the address and ask the reverse-zone operator if a record is expected.
NODATACode zero, no PTR answer and an SOA authority record.Investigate a missing requested record rather than a network timeout.
ALIAS_ONLYCode zero, no PTR or SOA, but a CNAME answer.Investigate alias resolution; a CNAME can be part of valid delegation.
REFERRAL / EMPTY_ANSWERWithout an earlier match, NS authority gives REFERRAL; otherwise EMPTY_ANSWER.Ask the DNS operator to inspect the relevant response and delegation.
SERVFAIL / REFUSEDThe DNS provider reports failure or refusal.Compare providers or retry later; do not infer that no PTR exists.
HTTP_ERROR / TIMEOUT / MALFORMED_RESPONSE / UPSTREAM_ERRORThe request or response could not produce usable DNS results.Check the error and retry later; missing DNS data has not been established.

RFC 1035: PTR records, reverse names, DNS responses and TTLRFC 2308: Negative answers and DNS cachingCloudflare: DNS over HTTPS JSON requestsGoogle Public DNS: DNS over HTTPS JSON API

Ask the address provider or delegated reverse-zone operator for changes

Forward DNS and reverse DNS have separate authority. Editing an A or AAAA record for a domain does not automatically create the address’s PTR record. Reverse-zone control follows the address-space delegation. Depending on the allocation and service arrangement, the responsible party may be an ISP, a hosting provider or an organization that manages delegated reverse DNS.

If you need a different PTR name, use your address provider’s supported reverse-DNS process or contact the administrator of the delegated zone. Provide the exact address and intended fully qualified hostname, and check the hostname’s forward records separately. Hosting a reverse zone at a DNS service is useful only when the parent delegation leads to it. ToolMellow reads records; it cannot publish a PTR, grant delegation or change an account setting.

ARIN: Reverse DNS authority and delegation managementCloudflare: Reverse zones and PTR records

Recognize legitimate aliases in classless reverse delegation

An IPv4 allocation smaller than an octet boundary may use classless reverse delegation. RFC 2317 describes parent-zone CNAME records pointing into a delegated child zone that holds the PTR records. This allows the address provider and customer to divide DNS administration without changing how a normal reverse query begins.

An alias on that path is different from making the PTR target itself a CNAME. An ALIAS_ONLY result says that this accepted reply did not include the PTR under the parser’s rules; it does not prove that classless delegation is invalid. The selected recursive provider may follow aliases internally. ToolMellow does not launch its own follow-up chain, so an operator may need a separate DNS trace to locate a missing or incorrect link.

RFC 2317: Classless IPv4 reverse delegationRFC 2181: Multiple PTR records and canonical targets

Check whether each returned name points back to the address

Forward-confirmed reverse DNS compares two directions. First obtain a PTR hostname for the address. Then query that hostname’s A records for IPv4 or AAAA records for IPv6 and check whether the original normalized address is among the answers. Use DNS Checker for this second step; this reverse-lookup workspace does not perform it automatically.

Record the provider and time for both observations, and repeat the comparison for each returned name that matters to your task. A name can have several forward addresses, so compare the address values rather than requiring a one-row answer or identical IPv6 spelling. Agreement supports DNS consistency at the observed time. It does not authenticate a person, prove address ownership or establish that a service accepts connections.

RFC 1912: Informational DNS operational guidanceRFC 4291: IPv6 text and IPv4-mapped address formsRFC 1035: PTR records, reverse names, DNS responses and TTL

Keep mail and log conclusions within the evidence

Reverse names can make logs easier to read and can be relevant when investigating a mail-server configuration. RFC 1912 gives operational advice to keep forward and reverse mappings consistent; it is an Informational document, not a guarantee that any particular receiver will deliver a message. A PTR check alone does not assess mail authentication, reputation, filtering or the rest of a delivery path.

Treat a hostname in a log as a DNS label associated with an address, not a verified user identity or location. An address may represent shared hosting, a gateway or infrastructure used by many people. If a system rejects a connection or message, preserve its actual error and check that system’s stated requirements alongside DNS. Do not change an unrelated domain record solely because a public PTR result looks unfamiliar.

RFC 1912: Informational DNS operational guidanceRFC 1035: PTR records, reverse names, DNS responses and TTL

Allow for positive and negative caches when checking a change

A PTR row’s TTL is the lifetime supplied in the DNS response, in seconds. At a recursive provider it can be the remaining cache lifetime. It is not record age, lookup latency, an address lease or a promise that all resolvers will refresh together. The number shown by ToolMellow does not count down automatically. To obtain a new observation, submit another lookup.

Missing-name and missing-type answers can also be cached under negative-caching rules. The workspace does not display a negative-cache TTL, so an empty result gives no visible countdown for a newly added PTR to appear. Cloudflare and Google may hold different cached data or encounter different upstream conditions. Compare the same address, provider and check time, and ask the operator to verify authoritative data when a change still looks wrong.

RFC 1035: PTR records, reverse names, DNS responses and TTLRFC 2308: Negative answers and DNS caching

Use the appropriate resolver for private or special-use addresses

Every submitted address is sent to ToolMellow’s server for parsing and classification. Only addresses classified as public have their generated reverse name sent to the selected public resolver. Other scopes show a private-or-special-use notice instead of the DNS status and PTR block. The generated reverse name still appears. That notice means the public query was withheld, not that a private network has no PTR record.

The scope policy is deliberately conservative rather than a complete mirror of every IANA exception. For example, the IPv6 parent range 2001::/23 is excluded even though some more-specific assignments have different registry properties. A public label means eligible for this lookup, not reachable. For a router, corporate network or VPN’s private DNS, use that network’s appropriate local resolver; this website does not query it.

IANA: IPv4 special-purpose address registryIANA: IPv6 special-purpose address registry

Distinguish invalid input, request failures and cancellation

The address and provider controls are disabled while the request runs. The provider timeout is eight seconds; the browser request deadline is twelve seconds. Cancel stops the current wait and restores the controls. It cannot undo a query already received by ToolMellow or the provider. There is no automatic retry, and a later submission is a new request.

An invalid-input response asks for an IPv4 or IPv6 address. Other HTTP failures, including temporary service or request-limit failures, use the generic lookup-failed message. Some accepted failure statuses also show that alert alongside the address details. Check the status when present, correct the input if needed and pause before retrying a recurring failure. Editing the address or changing provider clears the old error.

Distinguish invalid input, request failures and cancellation
ObservationCheckAction
Look up address is disabledBlank input or a request already runningEnter one literal, or wait for or cancel the active request.
IPv4 or IPv6 input errorURL syntax, port, leading zeroes, prefix, zone or excess lengthUse one bare address within 80 UTF-16 units before trimming.
No PTR record was returnedRead the accompanying DNS statusSeparate negative DNS data from a failed or incomplete lookup.
Old or different hostnamePossible cached answer or authoritative configurationCompare a fresh observation and ask the reverse-zone operator to check.
Changing provider clears the viewControl changes reset the previous observationSelect Look up address to query the newly selected provider.

Cloudflare: DNS over HTTPS JSON requestsGoogle Public DNS: DNS over HTTPS JSON API

Understand the request path and record only what you observed

ToolMellow receives the entered address. For eligible addresses, Cloudflare or Google receives its reverse-DNS name, which encodes the address. The provider request comes from ToolMellow’s server using DNS over HTTPS, not from your local resolver. Encryption protects the transport; it does not hide the query from those services or establish a retention policy. The page also loads normal site assets and analytics.

No account is required, and the workspace has no saved lookup history, dedicated result-copy button or export. A new action or page reload can clear the visible result. If you need an investigation record, save the displayed address, query name, provider, time, status and relevant PTR/TTL values yourself. An absent history control does not prove that servers or providers retain no request data.

Cloudflare: DNS over HTTPS JSON requestsGoogle Public DNS: DNS over HTTPS JSON API

Frequently asked questions

What does a reverse DNS lookup return?

It requests PTR records for an address and displays the accepted DNS status, returned PTR names and TTL values. It also shows normalized address details and the generated query name. Nonpublic scopes receive a notice instead of a public-resolver query.

Is the reverse DNS name the hostname found for my address?

No. The generated in-addr.arpa or ip6.arpa name is where DNS looks for PTR records. A returned PTR target is separate data. The query name can be constructed even when no PTR exists.

Can one address have more than one PTR record?

Yes. DNS permits multiple PTR records at one name. The tool shows the returned PTR rows, without selecting a preferred name or claiming that the list contains every website on the address.

Who can add or change my PTR record?

The operator with authority over the address’s reverse zone can do so. This may be your address provider or a delegated administrator. Editing the domain’s ordinary A or AAAA record alone does not create reverse authority.

Does a CNAME mean reverse DNS is broken?

No. Classless IPv4 reverse delegation can use CNAME records on the path to the PTR. The PTR target itself should be a canonical name, not a CNAME alias. ALIAS_ONLY describes the received reply and needs further investigation.

How do I check forward-confirmed reverse DNS?

Take a returned PTR hostname to DNS Checker. Query A for IPv4 or AAAA for IPv6 and see whether the original normalized address is among the results. Reverse DNS Lookup does not perform this second step automatically.

Why is no PTR shown for a private address?

The address still reaches ToolMellow for classification, but nonpublic scopes are not forwarded to the public resolver. A private network may have its own PTR records. Use its appropriate local resolver to investigate them.

Does NXDOMAIN mean the IP address is offline?

No. It concerns a nonexistent DNS name or final alias target in the response. It does not establish whether an address is assigned, reachable or serving an application.

Why do I still see the old PTR after a change?

The provider may have cached the old answer, or the authoritative change or delegation may need checking. Negative answers can also be cached. The tool shows PTR TTL values but no negative-cache countdown.

Can a correct PTR guarantee email delivery?

No. PTR and forward-DNS agreement are only part of a possible configuration investigation. A receiver’s authentication, reputation and delivery rules require separate checks against its actual requirements.

Does Cancel erase a submitted lookup?

No. Cancel stops waiting and restores the controls. ToolMellow or the provider may already have received the query. It does not delete received data or promise anything about retention.

Can I use reverse DNS to locate someone or list every hosted website?

No. A PTR name is operator-maintained DNS data, not verified personal identity or location. It does not enumerate all websites or services using an address. The tool includes no geolocation, WHOIS or network scan.

Sources and further reading

Put it into practice.

Related guides