So, you have heard that there is a network command that works on any OS, and you would like to try it out, right? Then, you came to the right place! Here we have 5 popular examples of the Nslookup command that will show you its capability. After seeing them, you can decide if you should integrate them into your network toolset.
Tag: Reverse DNS lookup
The DNS PTR record is a not-so-popular type. However, in this ocean of DNS records, there are a few of them that you absolutely should know. One of them is exactly the PTR record. You’ve come to the perfect page if you’re wondering why it’s so essential.
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.
What do we need?
- Linux computer, or a Mac with Homebrew and Dig command installed.
- The built-in tool that is called Dig command.
- The IP address that you want to check.
What is the Dig command?
The Dig command is a built-in command that you can find on any Linux distribution and serves for various DNS lookups, including a Reverse DNS lookup.
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.
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.