Start a Conversation

Unsolved

This post is more than 5 years old

1300

October 29th, 2009 00:00

Reverse DNS lookup failed

I have 2 solaris machines configured as cluster.
while running backups I am getting reverse DNS lookup failed for the address 192.168.24.2.

I went through forums and found that we need to provide multiple IPs in the networker server host file in order to resolve the DNS.

However in my case this IP is used as heart beat and assigned on both the nodes. So How can I diffrentiate between them.

Kindly help me out to get rid of this issue.

2 Intern

 • 

14.3K Posts

October 30th, 2009 05:00

heartbeat address belongs to physical machine thus it is unique to single side with its IP and hostname. In most cases I have seen warning for HB address, but has no impact on backup thus you could ignore it. If this causes failure in your case, it may indicate an issue with routing.

December 30th, 2009 01:00

What I did in this case I added the HB IP in the client's host file with a dummy alias and it stopped sending me reverse DNS lookup failed.

No Events found!

Top