Testing if you have properly set a Reverse DNS zone and PTR records inside it is a straightforward task with the built-in tool Dig command. You can see if the IP address matches the domain name with a simple DNS lookup. So let’s get into it.
So, in a traditional Forward DNS lookup, you type a domain name, and you are searching for the IP address so you can access its content. However, the Reverse DNS lookup has another purpose. You start with the IP address, and you look at who is behind it.
Here is a list of the different DNS record types you could add to your Reverse DNS zone.
The PTR record, or also known as a pointer record, has a very precise and important function. Its goal is to link the IP address to the domain name. In addition, there is a piece of good news, and it is able to perform successfully both with IPv4 addresses and IPv6 addresses. Moreover, this type of DNS record is an essential piece required for you to have Reverse DNS. It is able to exist only in the Reverse DNS zone. So, it would be best if you did not place it in the Forward DNS zone.
Reverse DNS zone – Do you really need to create one?Reverse DNS zone – Do you really need to create one?
For people approaching the DNS (domain name system), the Forward DNS zone is a must-stop. But what happens when it’s about going in the opposite direction? Well, there are essential differences between the Forward and Reverse DNS zones. Let’s check out if you really need to create a Reverse DNS one!
What does rDNS mean?
Reverse DNS, or simply for short rDNS, is a service normally included in your managed DNS plan. With it, you are able to perform reverse DNS lookups. For that purpose, it allows you to make a Reverse DNS zone and add inside it multiple PTR records. They serve you to prove that the IP addresses are associated with the domain name.