Many network diagnostic tools are already a part of Linux. For example, Nslookup command, Host command, Dig command, Traceroute command, and more. But, sometime in the past, there was a guy called Matt Kimball. He was just not satisfied with the traceroute command in the 90s, so he decided to make a new one – the MTR command.
Reverse DNS – What is it?
Reverse DNS, also known as rDNS, is a DNS lookup that maps an IP address to its domain name. It is absolutely the opposite of Forward DNS lookup, where the domain name links to the IP address where it is hosted.
In the majority of cases, rDNS is an additional service provided by a DNS hosting provider. Once you implement such a service, you should create a Master Reverse zone and add PTR records to it. That way, you are able to provide evidence that your IP address and your domain name have a proper match.
Thanks to the created PTR record, you actually confirm that the IP address is associated with the domain name. As a result, you are minimizing the chance and avoiding fraud. Additionally, you can implement Reverse DNS both with IPv4 address and A record and with IPv6 address and AAAA record.
In case you are just starting managing your DNS, these DNS record types are fundamental. So, let’s explain a little bit more about them.
SOA record
The acronym SOA stands for Start Of Authority, and it is essential to explain this record first. With it, you can show the origin of the authority DNS zone. This DNS record holds inside very important information about the DNS zone. It is a must-have if you want your DNS network to operate normally. The SOA record points to the primary DNS server. In addition, it stores information for the domain administrator and contact information. It also includes parameters such as the domain serial number and how often it should refresh. It is important to note that there should be just one SOA record for a particular DNS zone.
Learn everything about the DNS SOA Record!