Cloud Connect Jobs might start failing after upgrading to v8 update#3

After installation of update #3 for v8, tenants might report that their Cloud Connect jobs fail with “Failed to connect to the Veeam Cloud Connect service” error message, while tenant’s job log includes “No such host is known” error message.

Tenant has a service provider added to his Veeam Backup server via FQDN (DNS name) instead of IP address, but this external FQDN can’t be resolved on service provider side backup server.
 
Tenant log (Job logs):
[06.10.2015 06:33:18] <01> Error    Failed to use gate connection point [IP:xx.xxx.68.22, port:6180] to connect to the cloud service
[06.10.2015 06:33:18] <01> Error    No such host is known (System.Net.Sockets.SocketException)
[06.10.2015 06:33:18] <01> Error       at Veeam.Backup.Core.CCloudGateSvcImpl.InvokeRpc(CSocketInvokerClient invokerClient, CSocketInvokerParams invokerParam)
 
Service provider log (Session.log):
[06.10.2015 06:51:09] <15> Error    No such host is known (System.Net.Sockets.SocketException)
[06.10.2015 06:51:09] <15> Error       at System.Net.Dns.InternalGetHostByName(String hostName, Boolean includeIPv6)
[06.10.2015 06:51:09] <15> Error       at System.Net.Dns.GetHostEntry(String hostNameOrAddress)
[06.10.2015 06:51:09] <15> Error       at Veeam.Backup.Common.CIPPort.GetAllIpsAndHostnames()
 

Service Provider should ensure that its DNS server is setup properly to be able to resolve external FQDN. Alternatively, Service Provider can add FQDN to IP address rule to Windows hosts file on Veeam Backup server (%SystemRoot%\system32\drivers\etc\hosts) using external IP of Cloud Gateway server.