Going to chime in here, and maybe I didn’t understand it correctly but here goes:
When vbr installs and is installing components on other servers (lets say remote proxy or repository) the communication is configured to use the hostname of the VBR server (even when the vbr server is on windows and windows is ad joined.
Ofcourse you can add a dns A record for this but if the remote servers are not adding the dns suffix a DNS server cannot resolve the address as the dns request is not a FQDN but just a host name (barring that the remote servers arent using dns searchzones)
Wouldn’t it be “better” that there would be an option to configure a FQDN for veeam products (the enterprise manager exhibits the same “flaw” btw.
When vbr installs and is installing components on other servers (lets say remote proxy or repository) the communication is configured to use the hostname of the VBR server (even when the vbr server is on windows and windows is ad joined.
Ofcourse you can add a dns A record for this but if the remote servers are not adding the dns suffix a DNS server cannot resolve the address as the dns request is not a FQDN but just a host name (barring that the remote servers arent using dns searchzones)
Wouldn’t it be “better” that there would be an option to configure a FQDN for veeam products (the enterprise manager exhibits the same “flaw” btw.
Statistics: Posted by mjr.epicfail — May 19, 2025 6:43 am
