"Failed to Connect to Client" errors when configuring DNS

SUMMARY

When configuring a client to use a DNS name instead of an IP address, you may receive "Failed to Connect to Client After 5 Attempts" when backups run.

ISSUE

 

When configuring a protected client by DNS name instead of IP address, you need to ensure that Reverse Lookup Zones have been configured in your environment. 

**WARNING: For advanced users only***

If your environment does not support Reverse Lookup Zones, you may use the following advanced procedure as a work-around.  Warning: Do not execute this procedure when backups are running.

  1. Ensure your DNS servers are configured in Settings > Clients, Networks, and Notifications > Networks > DNS
  2. If the DNS server does not have reverse lookup configured, using an SSH client such as PuTTY, log in to the Unitrends system and run the command vi /usr/bp/bpinit/master.ini. Add this name/value pair to The [Configuration Options] section: ‘DoReverseNameLookup=False’. Write and Quit the file.
  3. Next, run the command vi /etc/httpd/conf/httpd.conf. Change HostnameLookups from Off to On. Write and Quit the file.
  4. Restart networking by running the command service httpd restart.
  5. The Unitrends system should now be able to resolve hostnames to IP addresses.

 

 

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Contact us