How does reverse DNS lookup work?

You have an IP address like, and you want to know which domains point to it. I always used to Google “reverse IP”, then use a web service like this one. I assumed these services must have some giant database of all public DNS records in order to invert the query.

That’s not how it works! You can do the same “reverse IP” query yourself using a tool like dig:

$ dig +short PTR

And sure enough, if we ask for the IP for, we get

$ dig +short A

This works because DNS has a PTR record type, which is like the inverse of the A record type. Where there is a record IN A, there is an equivalent inverse record IN PTR

Notice the weird notation All IP addresses A.B.C.D are assigned a “domain” This hack seems to be necessary because the “left-hand side” of DNS record types are supposed to be domains, not IP addresses.

Because this PTR query is on a separate set of PTR records, and not on the canonical set of A records, there is no guarantee that it will give you an inverse. The PTR records can be inconsistent with the A records.

How does dig look up the “domain” The same as for any other domain name! Traverse the domain name from the root, beginning by asking the root nameservers. We get results like these:

arpa.			          IN	NS		    IN	NS		  IN	NS	  IN	NS	IN	NS

The IP address space is hierarchical, just like the domain name space. But the most-significant digit is on the left of the IP address, unlike the most-significant part of the domain name, which is on the right. This is the reason that the IP address A.B.C.D is reversed when placed into its “domain”

The owner of the IP address space 8.8.*.*, i.e., is in control of the domain Apparently Google is the owner of 8.8.4.*, i.e. We can explore these ownerships with other tools, but that’s another blog post.

Tagged #reverse-dns, #dns, #networking, #posix, #programming.

Similar posts

More by Jim

Want to build a fantastic product using LLMs? I work at Granola where we're building the future IDE for knowledge work. Come and work with us! Read more or get in touch!

This page copyright James Fisher 2018. Content is not associated with my employer. Found an error? Edit this page.