Please Whitelist This Site?

I know everyone hates ads. But please understand that I am providing premium content for free that takes hundreds of hours of time to research and write. I don't want to go to a pay-only model like some sites, but when more and more people block ads, I end up working for free. And I have a family to support, just like you. :)

If you like The TCP/IP Guide, please consider the download version. It's priced very economically and you can read all of it in a convenient format without ads.

If you want to use this site for free, I'd be grateful if you could add the site to the whitelist for Adblock. To do so, just open the Adblock menu and select "Disable on tcpipguide.com". Or go to the Tools menu and select "Adblock Plus Preferences...". Then click "Add Filter..." at the bottom, and add this string: "@@||tcpipguide.com^$document". Then just click OK.

Thanks for your understanding!

Sincerely, Charles Kozierok
Author and Publisher, The TCP/IP Guide


NOTE: Using software to mass-download the site degrades the server and is prohibited.
If you want to read The TCP/IP Guide offline, please consider licensing it. Thank you.

The Book is Here... and Now On Sale!

Get The TCP/IP Guide for your own computer.
The TCP/IP Guide

Custom Search







Table Of Contents  The TCP/IP Guide
 9  TCP/IP Application Layer Protocols, Services and Applications (OSI Layers 5, 6 and 7)
      9  Name Systems and TCP/IP Name Registration and Name Resolution
           9  TCP/IP Name Systems: Host Tables and Domain Name System (DNS)
                9  TCP/IP Domain Name System (DNS)
                     9  DNS Name Servers and Name Resolution
                          9  DNS Resolution Concepts and Resolver Operations

Previous Topic/Section
DNS Name Resolution Process
Previous Page
Pages in Current Topic/Section
1
234
Next Page
DNS Electronic Mail Support and Mail Exchange (MX) Resource Records
Next Topic/Section

DNS Reverse Name Resolution Using the IN-ADDR.ARPA Domain
(Page 1 of 4)

If most people had to boil down the core job of the Domain Name System to one function, they would probably say it was converting the names of objects into the numeric IP addresses associated with them. Well, they would if they knew much about DNS. For this reason, DNS is sometimes compared to a telephone book, or to telephone “411” service. There are certain problems with this analogy, but at the highest level it is valid. In both cases we take a name, consult a database (of one type or another), and produce from it a number that matches that name.

The Need for Reverse Name Resolution

In the real world, there are sometimes situations where you don't want to find the phone number that goes with a name, but rather, you have a phone number and want to know what person it belongs to. For example, this might happen if your telephone records the number of incoming calls but you don't have Caller ID to display the name associated with a number. You might also find a phone number on a piece of paper and not remember whose number it is.

Similarly, in the networking world, there are many situations where we have an IP address and want to know what name goes with it. For example, a World Wide Web server records the IP address of each device that connects to it in its server logs, but these numbers are generally meaningless to humans, who prefer to see the names that go with them.

A more serious example might be a hacker trying to break into your computer; by converting the IP address into a name you might be able to find out what part of the world he is from, what ISP he is using, and so forth. There are also many reasons why a network administrator might want to find out the name that goes with an address, for setup or troubleshooting purposes.

The Original Method: Inverse Querying

DNS originally included a feature called inverse querying that would allow this type of “opposite” resolution. A resolver could send a query which, instead of having a name filled in and a space for the server to fill in the IP address, had the IP address and a space for the name. The server would check its resource records and return the name to the resolver.

This works fine in theory, and even in practice if the internetwork is very small. However, remember that due to the distributed nature of DNS information, the biggest part of the job of resolution is in fact finding the right server. Now, in the case of regular resolution, we can easily find the right server by traversing the hierarchy of servers. This is possible because the servers are connected together following a hierarchy of names.

DNS servers are not, however, arranged based on IP address. This means that to use inverse queries, we have to use the right name server for the IP address we want to resolve into a name, with no easy way to find out what it is. Sure, we could try sending the inverse query to the authoritative DNS server for every zone in the hierarchy. If you tried, it would probably take you longer than it took to write this Guide. So let's not go there. The end result of all of this is that inverse queries were never popular except for local server troubleshooting. They were formally removed from DNS in November 2002 through the publishing of RFC 3425.


Previous Topic/Section
DNS Name Resolution Process
Previous Page
Pages in Current Topic/Section
1
234
Next Page
DNS Electronic Mail Support and Mail Exchange (MX) Resource Records
Next Topic/Section

If you find The TCP/IP Guide useful, please consider making a small Paypal donation to help the site, using one of the buttons below. You can also donate a custom amount using the far right button (not less than $1 please, or PayPal gets most/all of your money!) In lieu of a larger donation, you may wish to consider purchasing a download license of The TCP/IP Guide. Thanks for your support!
Donate $2
Donate $5
Donate $10
Donate $20
Donate $30
Donate: $



Home - Table Of Contents - Contact Us

The TCP/IP Guide (http://www.TCPIPGuide.com)
Version 3.0 - Version Date: September 20, 2005

Copyright 2001-2005 Charles M. Kozierok. All Rights Reserved.
Not responsible for any loss resulting from the use of this site.