Solved!
Go to SolutionGetting like Reverse DNS lookup failed
Hi,
I am getting an error like Reverse DNS lookup failed for address 192.168.1.3
66135:save: NSR directive file (/opt/lgtonmc/cores/gstd/.nsr) parsed
66135:save: NSR directive file (/opt/lgtonmc/cores/gsttclsh/.nsr) parsed ,
But it has taken a backup and still it is showing the backup is failed , Fromt he details i can see it has been taken about 300GB of data , but still the error is coming, Kindly let me know what is exactly meant by Reverse DNS lookup failed .
Rajesh
I am getting an error like Reverse DNS lookup failed for address 192.168.1.3
66135:save: NSR directive file (/opt/lgtonmc/cores/gstd/.nsr) parsed
66135:save: NSR directive file (/opt/lgtonmc/cores/gsttclsh/.nsr) parsed ,
But it has taken a backup and still it is showing the backup is failed , Fromt he details i can see it has been taken about 300GB of data , but still the error is coming, Kindly let me know what is exactly meant by Reverse DNS lookup failed .
Rajesh
amediratta
2 Intern
•
2014 Posts
1842
1
Posted January 5th, 2009 03:00
Are you using multiple NIC cards? Is this IP for your Client's NIC card?
IKP1
198 Posts
1842
0
Posted January 5th, 2009 10:00
NetWorker is sensitive to server/client name resolution.
On both the client and the server, verify that each IP address can be resolved either by using the local host files or via DNS.
So for example, if your client has two IP addresses, then the server should be able to resolve both of these addresses to names.
This is one of the most common issues I see with NetWorker, and by name resolution, I mean both forward and reverse - so that if you have an address of 192.168.1.2 with name fred.smith.inc then a lookup of 192.168.1.2 should return fred.smith.inc and the reverse should be true - lookup of fred.smith.inc should return 192.168.1.2.
Whilst most none Windows DNS environments have forward and reverse fully configured, I have found that a lot of Windows users forget to fully configure the reverse lookups.
HtH
IKP