A PTR record stands for “pointer” record, and is commonly also called a “pointer record.”
A PTR record is used in DNS reverse lookups and does the opposite of what an A record does in DNS. A reverse lookup is what occurs when a user has an IP address and they are looking for the DNS name.
Unlike DNS A records, PTR records are stored using the IP address, or in reverse compared to A records with “.in-addr.arpa” tacked on.
For example: An IPv4 address which looks like 192.168.10.2 would be stored as: 18.104.22.168.in-addr.arpa
PTR records are generally used for security and troubleshooting.
For example, it can be used for email security and as an anti spam tool. The incoming mail server will use the PTR record from the domain of the incoming email to make sure the IP address of the domain of the sending email server matches the correct IP address. The sender in this case may also choose to have SPF TXT records to ensure their emails are not sent to the spam filter or blocked altogether.
PTR records may also be used to help check logs. Basic logs may only store IP addresses, not DNS names. PTR records may be used to track down DNS names and clarify source and destination information to make it more human readable.
There are different ways to create PTR records depending on the DNS management tool you’re using. To configure in Micetro:
Like with most DNS records, there are two tools that may be used: nslookup and dig. Nslookup is usually included by default in the terminal or command line of any Windows, Mac, or Linux machine. Dig can be downloaded for use or can be found as a browser based tool, such as the one on menandmice.com.