The following series of articles details information of DNS Records, we are covering each setting in the series, providing basic use and purpose.
What are PTR records, what are they used for, and how do they work?
The PTR record is completely opposite of the A records. The main use of the PTR records is in performing the reverse DNS lookup. The DNS lookup takes place as soon as the user tries to get to the domain name in their browser.
This DNS lookup service links the domain name to the IP address. The reverse DNS lookup, however, is completely the opposite of this procedure. In this query, the user enters the IP address of the domain they are trying to find on the internet. In other words, they reach the domain name through the IP address. The main uses of the PTR records include the anti-spam filters, fixing the issues with email delivery, and logging. Identified by RFC 1035, the PTR records are also used as the pointer that directs users to the canonical name.
What are RRSIG records, what are they used for, and how do they work?
The RRSIG records have a structure and format similar to the SIG record. These records are identified by RFC 4034, these records are mainly known for keeping the DNSSEC signature. RRSIG is considered one of the popular resource records in the DNS. The main use of digital signatures is to authenticate and verify data available in the RRsets.
What are RP Records, what are they used for, and how do they work?
RP stands for the responsible person. These records are mainly used for holding the email of the user who is operating the domain. In simple words, it keeps the email address of the person who has created the domain and is running it. Not only the email address, but the RP records could also be used to fetch and store other personal details of the user, such as their name, address, and contact number.
The RP records play a significant role in the DNS records as they tell you the email address of the person, along with other information. You can only add these records in text format. Note that the @of the email address of the user will be replaced with a. The RP records are identified by RFC 1183.