Solving rDNS Not Forward Confirmed and x.x.x.x.in-addr.arpa Looks Like Generic Errors

In this article, we will discuss the process of testing reverse DNS (rDNS) using a tool and the steps to take when the rDNS test result shows that the IP address is resolved but the in-addr.arpa domain is unresolved, indicating that rDNS is not forward confirmed.

Understanding rDNS

Reverse DNS (rDNS) is a process that maps an IP address to a domain name. This is the opposite of the more commonly known forward DNS, which maps a domain name to an IP address. rDNS is important for network troubleshooting, email delivery, and security.

Testing rDNS

To test rDNS, you can use various tools such as dig, nslookup, or host. For this article, we will use the FCrDNS tool, which is a Perl script that tests reverse DNS and provides a detailed report.

Testing with FCrDNS

To test rDNS using FCrDNS, follow these steps:

1. Install the FCrDNS tool:

   cpan install FCrDNS
   

2. Run the tool with your IP address as an argument:

   perl FCrDNS.pl x.x.x.x
   

Replace x.x.x.x with your IP address.

Interpreting the Results

The FCrDNS tool will provide a detailed report about the rDNS of the given IP address. If the IP address is resolved and the in-addr.arpa domain is unresolved, it means that rDNS is not forward confirmed.

Here is an example of the output:

FCrDNS test result for x.x.x.x

x.x.x.x resolved x.x.x.x.in-addr.arpa; x.x.x.x.in-addr.arpa unresolved; rDNS NOT forward confirmed.

Generic...

Troubleshooting rDNS Not Forward Confirmed

If rDNS is not forward confirmed, it means that the DNS server responsible for the IP address's reverse zone does not have the corresponding PTR record. To resolve this issue, you should create or update the PTR record for the IP address in the corresponding in-addr.arpa domain.

Here are the steps to create or update the PTR record:

1. Determine the reverse zone for your IP address. The reverse zone is based on the last octet of the IP address. For example, if your IP address is 192.168.1.1, the reverse zone would be 1.168.192.in-addr.arpa.

2. Log in to your DNS server and create or update the PTR record. The PTR record should have the IP address as the data and the hostname as the name. For example:

   example.com. IN PTR ipv4.example.com.
   

   Replace example.com with your domain name, ipv4 with a meaningful name for the PTR record, and example.com with the domain name for which the PTR record belongs.

3. Save the changes and allow the DNS server to propagate the changes.

4. Test the rDNS again using the FCrDNS tool to ensure that the issue is resolved.

Conclusion

In this article, we discussed the process of testing rDNS using the FCrDNS tool and the steps to take when rDNS is not forward confirmed. We covered the importance of rDNS, how to test it, and how to troubleshoot the issue when it occurs.

References

1. Reverse DNS (rDNS) Explained
2. FCrDNS Tool
3. How to Create a PTR Record
4. Reverse DNS Lookup