Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Iv been reading a few articles abour Reverse DNS and PTR records but i still cant understand the logic behind the in.addr.arpa.
What is the puprose of the relevant domain? Since this is an ip-to-domain resolution, why is there a domain fit to the ip address? Wouldnt a table with the delegated ip ranges be enough?
The purpose is to restrict spam, they want to be sure you are who you claim to be before accepting your mail. For instance, mail sent from infected Windows computers obviously does not have a valid PTR record.
I suspect the actual in.addr.arpa name is necessary for DNS servers to operate on PTR records using normal zone lookups, rather than creating a separate protocol for PTR lookups.
In any case, valid PTR records are provided by your isp. I know verizon automatically created PTR records for my static FIOS ip's (and if I put an infected computer on my network it could certainly send spam with valid PTR records).
I understood the whole PTR thing when i realized that in.addr.arpa is an actual domain/zone and as @Doug G stated, the same protocol is used to reverse the resolve. Hence why configuring a PTR zone in bind9 you have to reverse the ip address.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.