Error: The remote name could not be resolved – Validis Support

The upload cannot reach our servers. Allowlist the URL, then check DNS

Overview

When attempting an upload, the client may be presented with the following error. This occurs when the user cannot connect to our server during the upload (connection may be lost or blocked).

A vConnect dialog reading An unexpected error happened, vConnect is not available or a communication error happened, The remote name could not be resolved, followed by a storage address, with a Close button

The error as the client sees it.

Step 1: Allowlist the URL

Have the client allowlist the appropriate URL for their respective environment, then reattempt the upload.

Region	URL to allowlist
Europe EU, UK2	`https://vclient-provisioner-uk2-validis.azurewebsites.net/` `https://vclient-provisioner-eu-validis.azurewebsites.net/`
North America US3, CA3	`https://vclient-provisioner-us3-validis.azurewebsites.net/` `https://vclient-provisioner-ca3-validis.azurewebsites.net/`
Australia AU2	`https://vclient-provisioner-au2-validis.azurewebsites.net/`
Singapore SG	`https://vclient-provisioner-sg-validis.azurewebsites.net/`

Step 2: Check DNS resolution

If the client is still experiencing the error after allowlisting the URL, have them (or their IT team) run the following command in Windows PowerShell, replacing {your region} with their region code from the table above.

Resolve-DnsName -Name vali{your region}strg.blob.core.windows.net

Please note:

Ensure the command is run on the machine the upload was attempted on
The region variable will be the environment the client attempted the upload on

What a failure looks like

If the chain stops at the privatelink record and goes no further, the response is being blocked.

A Windows PowerShell window running Resolve-DnsName against a Validis blob storage address, returning a single CNAME record pointing to the privatelink address and nothing beyond it

The chain stops at the privatelink record. This is not the expected response.

What a success looks like

Server: xxx.xx.x.xx
Address: xxx.xx.x.xx#xx

Non-authoritative answer:
vali{your region}strg.blob.core.windows.net
canonical name = vali{your region}strg.privatelink.blob.core.windows.net.

vali{your region}strg.privatelink.blob.core.windows.net
canonical name = blob.xxxxxxxxx.store.core.windows.net

Step 3: Add a conditional forward

If the client sees the blocked response above, have them add a conditional forward for vali{your region}strg.blob.core.windows.net to forward to other DNS servers, so that their Internal DNS servers do not block the response.

This is a change inside the client’s own DNS configuration, and it is not specific to Validis. For the background on why this happens, see Error: Private Link CNAME Resolution Externally / DNS resolution.