I found that I could resolve the FQND from the proxy but not the short name, once I added the shrort name to the host file on the proxies the problem went away.
Thanks very much This fixed my issue as well. Good find on the shortname. I found that on my proxy fqdn resolved fine with my Windows AD DC/DNS server, but not the shortname, unlike a windows client. Weird that I had no issue for months without this addition to /etc/hosts, but now problem solved.
Sandeep_Sinha
307 Posts
0
July 16th, 2012 04:00
Hello,
Is this happening for a VM client or all the VM clients ?
Please check if Avamar proxy server can resolve the FQDN of Avamar server and vCenter
If not, please make entries of Avamar server and vCenter in the hosts file of the Avamar proxy
Thanks.
8Ii368jqR011781
2 Posts
1
January 29th, 2013 12:00
I found that I could resolve the FQND from the proxy but not the short name, once I added the shrort name to the host file on the proxies the problem went away.
SMUniversity-VN
1 Message
0
February 20th, 2014 16:00
Thanks very much This fixed my issue as well. Good find on the shortname. I found that on my proxy fqdn resolved fine with my Windows AD DC/DNS server, but not the shortname, unlike a windows client. Weird that I had no issue for months without this addition to /etc/hosts, but now problem solved.
Peter Weijers
1 Message
0
August 13th, 2021 04:00
Hello,
We had the same issue in Linux. In /etc/resolv.conf the lines 'search' and 'domain' were missing, so the shortname could not be resolved