Route53 redirecting ServiceNow Instance directly to ServiceNow.com

Question

I have a hosted zone set up in AWS route53 (labs.mycompany.com) and a Simple CNAME record inside that hosted zone (servicenow.labs.mycompany.com) and have configured it to redirect to our ServiceNow instance (dev12345.service-now.com) but rather than going to the instance it is redirecting to servicenow.com directly.

I did a DiG and the DNS record appears to be accurate and fine.

I tried a curl and and I'm guessing the redirect is from http to https which I believe is standard, I get SSL errors when trying http which is to be expected.

I can only assume at this point that service now must be doing some kind of domain filtering at the load balancer and the website I'm getting redirected to is just the default target when no patterns match.

How do I work around this so I can redirect our URL directly to our servicenow instance?

Thanks

CarlosGP-AWS · Answer

Hi there,
A CNAME record on its own won't redirect one domain to another, especially if there's HTTPS involved.
When you try to access http://servicenow.labs.mycompany.com or https://servicenow.labs.mycompany.com, the first thing that happens in your local PC is DNS resolution. 
Assuming you have created the CNAME record for servicenow.labs.mycompany.com to dev12345.service-now.com, your local PC will now attempt to resolve dev12345.service-now.com to receive an IP address, as eventually this is what it needs to connect at the IP level.
The connection will then be sent to the IP address of service-now, but the HTTP Host header will still be servicenow.labs.mycompany.com.
So besides creating the CNAME, you also need to make sure service-now is actually expecting this Host header and has an SSL/TLS certificate to reply with.

Hope this clarifies your question.
-Carlos

Ref: https://aws.amazon.com/premiumsupport/knowledge-center/route-53-redirect-to-another-domain/

Route53 redirecting ServiceNow Instance directly to ServiceNow.com

Relevant content