New London Custom URLs

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-22-2018 10:52 AM
My organization is going to need to rebrand in the next few months, and with this rebranding we will be required to update the URL for our instances to a new name. For example, we are currently on abc.service-now.com. We will need to rebrand to 123.service-now.com.
With the new functionality in ServiceNow to allow for custom URLs with the London release, does anyone know how we go about it. I have enabled the plugin, enabled the system properties, and attempted to add in a custom URL only to be presented with this error. Error Message Domain 123.service-now.com is unreachable. Ensure it is up and running before adding it as a custom url.
Obviously, this is just an example of what we're trying to do and we'd have a valid name for the domain. I'm just not sure what step I'm missing.
Is this URL something that has to be registered first? Am I only allowed to do this with the same name of my existing instance (i.e. servicenow.abc.com)? Any help on this would be much appreciated!
Thank you in advance for the assistance
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-19-2019 05:59 AM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-14-2019 11:17 AM
Is this a personal developer instance (PDI) or demo instance? You cannot use the custom URL feature in a PDI
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-29-2018 03:36 AM
Hello Jeff,
Could you please advise how to establish CAA record. If we have SSL certificate, how to set the LetsEncrypt.org. Please provide the steps.
Thank you,
Divya

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-29-2018 05:40 AM
Divya,
There isn't much information on this out there on configuring with LetsEncrypt.org. I believe you need to coordinate this with the Hi team. I suggest you log an incident with Hi to get this configured.
-Jeff