An "in-addr.arpa address" is a reverse DNS record, stored in a strange format. If we are considering ip 1.2.3.4, then "4.3.2.1.in-addr.arpa" is the reverse DNS record. It's used when you want to find out the host name of something you have an ip address for (for example, "dig -x " will give you that). But why is it stored backwards?
Well, if you wanted to get really geeky about it, it's the ip addresses that you are used to seeing that are backwards. Think about it this way: when you see mail.xyz.com, what's the least specific part of that? It's the ".com", because there are millions of ".com" machines. The "xyz.com" may have multiple machines, but "mail.zyz.com" nails it down to one.
Well, maybe more than one, because of round-robin DNS, or multiple MX records, but that's not important for this discussion.
Now look at the ip address - let's pretend that it's 192.168.4.5. What's the least specific part of that? The "192", of course. So in names, the least specific part comes last, but in IP addresses, it comes first. Therefore, from a geek point of view, at least one of them is "backwards".
When DNS is used to find something on the internet, it always starts at the least specific. We ask ".com" to tell us who is responsible for "xyz.com" and we ask that DNS server where to find "mail". Likewise, if we are working from an address to find a name, we want to work the same way: go to the least specific first. Ask the machine responsible for 192 addresses to tell us where 192.168 is, etc. (except, of course, that 192.168 is one of the private address ranges so that doesn't really work) That's why in-addr.arpa records are stored in the same way as the names are: most specific to least.
Of course if the convention for addresses had been to present them like we present names, then you'd say " This machine is 34.2.168.192", and the in-addr.arpa address might be what we are used to seeing..
Have you tried Searching this site?
Unix/Linux/Mac OS X support by phone, email or on-site: Support Rates
This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more. We appreciate comments and article submissions.
Many of the products and books I review are things I purchased for my own use. Some were given to me specifically for the purpose of reviewing them. I resell or can earn commissions from the sale of some of these items. Links within these pages may be affiliate links that pay me for referring you to them. That's mostly insignificant amounts of money; whenever it is not I have made my relationship plain. I also may own stock in companies mentioned here. If you have any question, please do feel free to contact me.
Specific links that take you to pages that allow you to purchase the item I reviewed are very likely to pay me a commission. Many of the books I review were given to me by the publishers specifically for the purpose of writing a review. These gifts and referral fees do not affect my opinions; I often give bad reviews anyway.
We use Google third-party advertising companies to serve ads when you visit our website. These companies may use information (not including your name, address, email address, or telephone number) about your visits to this and other websites in order to provide advertisements about goods and services of interest to you. If you would like more information about this practice and to know your choices about not having this information used by these companies, click here.
Click here to add your comments
Fri Feb 25 15:11:30 2005: Subject: Thanks anonymous
Very very well explaned thank you ever so much.
Don't miss responses! Subscribe to Comments by RSS or by Email
Click here to add your comments
If you want a picture to show with your comment, go get a Gravatar