- 최신
- 최다 투표
- 가장 많은 댓글
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/
관련 콘텐츠
- AWS 공식업데이트됨 2년 전
- AWS 공식업데이트됨 일 년 전
- AWS 공식업데이트됨 일 년 전