Ask the Community
Groups
"Failed to Connect to Client" errors when configuring DNS - Connect IT Community | Kaseya
<main> <article class="userContent"> <h2 data-id="summary"><strong>SUMMARY</strong></h2> <p>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.</p> <h2 data-id="issue"><strong>ISSUE</strong></h2> <p></p> <h3 data-id="n-a"> </h3> <p>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. </p> <h3 data-id="warning-for-advanced-users-only"><b>**WARNING: For advanced users only***</b></h3> <p>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.</p> <ol><li>Ensure your DNS servers are configured in Settings > Clients, Networks, and Notifications > Networks > DNS</li> <li>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.</li> <li>Next, run the command vi /etc/httpd/conf/httpd.conf. Change HostnameLookups from Off to On. Write and Quit the file.</li> <li>Restart networking by running the command service httpd restart.</li> <li>The Unitrends system should now be able to resolve hostnames to IP addresses.</li> </ol><h3 data-id="n-a-1"> </h3> <p> </p> <p> </p> </article> </main>