What needs to be set up (technically) to make the URL tag of a company work for a custom URL?

DNS: wildcard registration, for example:

-*.dev.retailvista.net

-*.test.retailvista.net

Once that is done, everything will point to the correct IP address and therefore to the correct server, both yyy.retailvista.net and

xxx.yyy.test.retailvista.net

Verify this by pinging the URL you want to create. It should ping to the same server as 'the old URL', e.g. test.retailvista.net

IIS Root website

It starts with the correct root application: RetailVistaRoot. If this is not present, there can be no direct access to the correct URL.

This only needs to be placed once at the root level of the RetailVista website within IIS. Once this is done, it will work for all instances thereafter. This has already been done for test.retailvista.net (2023/07/28).

IIS Bindings

Adding bindings, first the general one, 1 subdomain deep:  *.test.retailvista.net. Once this is done, global.test.retailvista.net will also work instead of test.retailvista.net/global.

Then, for each instance where custom URLs are to be used, a wildcard needs to be added, e.g. *.global.test.retailvista.net for the 'global' instance.

Once this is done, [companyUrlTag].[instance].test.retailvista.net will automatically redirect to

[companyUrlTag].test.retailvista.net/[instance] allowing for direct login without specifying the company.