Common doubts when creating Custom URL - Support and Troubleshooting

Common doubts when creating Custom URL Summary .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Some questions (not covered in KB0820070 ) like the ones below might show up and it's not always possible to test it on a sub-prod environment:

1. Does the existing URL still function after activating the custom URL? 2. Can we use a custom URL on each instance i.e. vityl.agilitihealth.com(PROD), vityldev.agilitihealth.com(DEV), vityldev2.agilitihealth.com(DEV2), vitylqa.agilitihealth.com(QA) * Will those sub-prod instances require configuration after each clone down, or is it excluded? 3. Will the custom URL affect the default SMTP account, or will additional SMTP accounts need to be created? 4. Will the custom URL for the Service Portal require the /sp at the end of the URL as it does today or is it a completely different URL? 5. Steps for updating the CNAME record with the ISP?

Release .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } newyork p9 onwards

Instructions .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } 1.Yes existing URL will keep working. 2.Yes, you can use a different custom URL on each instance. During a clone you would need to preserve custom URL table, otherwise close records would be updated. 3.It should not affect your default SMTP account. Note that custom url setup is a change on the DNS, it works like a redirection to the instance 4."/sp" string won't be needed, but if you need to access service portal after configuring custom URL then you will use /sp as usual. 5. SP normally configure the CNAME record on your behalf. If this does not happen you would need to add a CNAME record for each host at your ISP. This is done specifically for Reverse DNS zones to ensure requests are properly routed for resolution:

a. Make a note of the IP address and your desired CNAME for each host in your new reverse DNS zone. b. Contact your ISP and request that they append a CNAME record for each host in your Dyn Managed DNS zone to your account with them. c. Test the Reverse DNS path by running: dig -x +trace