A MID Server is set up with a URL parameter and will connect to the instance using that URL. This KB explains which URL should be used after activating Custom URLs.
Release or Environment
Since the London release, there is a Custom URLs plugin, that can be used on instances with a dedicated VIP, to create custom URLs to access the instance.
This can lead to several URLs that the instance could be accessed using:
|The initial domain name for Acme that came with the ServiceNow instance.|
|A custom URL that associates with your ServiceNow instance. This URL is referred to as an alias (CNAME) of the initial domain name.|
|A secondary custom URL that associates to a service portal on your instance. Your instance can support multiple custom URLs to the same service portal.|
We recommend that the initial URL https://<instance name>.service-now.com is used. This is the URL that would be used even without the Custom URLs activated. This will allow the MID Server to connect regardless of what additional URLs are added or changed in the future, because this initial URL will always work.
Although a Custom URL could be used with a MID Server, it will depend on a CNAME record in your own DNS, which will point to the initial URL. There is no need to add that additional potential point of failure, so just use the initial URL. A secondary custom URL is not to be used, as MID Servers have nothing to do with Service Portals.
|Note: If you need to configure Firewall rules to allow the MID Servers to access the instance, you may need to remember which URL the MID Servers are set up to connect to.|