Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8367467
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 9, 20262026-06-09T13:09:56+00:00 2026-06-09T13:09:56+00:00

I am using Amazon EC2 ELB and following their recommendation of using CNAME to

  • 0

I am using Amazon EC2 ELB and following their recommendation of using CNAME to refer to the public DNS of the ELB:

$ nslookup qa.mydomain.com
Server:     192.168.1.1
Address:    192.168.1.1#53

Non-authoritative answer:
qa.mydomain.com canonical name = mydomain-20530xxxx.us-west-1.elb.amazonaws.com.
Name:   mydomain-20530xxxx.us-west-1.elb.amazonaws.com
Address: 50.18.xxx.yyy

I purchased a wildcard SSL cert to protect all my subdomains. So the cert was issued for *.mydomain.com. However, when I visit qa.mydomain.com, all browsers are screaming security. The message on Google Chrome, when I try to access https://qa.mydomain.com is:

Chrome says: You attempted to reach mydomain-20530xxxx.us-west-1.elb.amazonaws.com, but instead you actually reached a server identifying itself as *.mydomain.com. This may be caused by a misconfiguration on the server or by something more serious..

Am I going about it the wrong way? Is the use of CNAME essentially incompatible with PKI/SSL? What are my options?

Thanks.

PS: Here is the report from performing dig on the address: qa.mydomain.com. Obviously, the actual domain name and results have been masked for security.

$ dig qa.mydomain.com

; <<>> DiG 9.8.1-P1 <<>> qa.mydomain.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 961
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;qa.mydomain.com.       IN  A

;; ANSWER SECTION:
qa.mydomain.com.    1670    IN  CNAME   mydomain-205300xxxx.us-west-1.elb.amazonaws.com.
mydomain-205300xxxx.us-west-1.elb.amazonaws.com. 60 IN A 50.18.xxx.yyy

;; Query time: 105 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Thu Aug  9 14:05:31 2012
;; MSG SIZE  rcvd: 121
  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-09T13:09:58+00:00Added an answer on June 9, 2026 at 1:09 pm

    Whether the IP address resolution comes from a CNAME or an A DNS entry has no influence on the certificate name verification.

    What matters is that the name, as you request it in the URL, matches one of the entries in the certificate.

    In short, if the certificate has Subject Alternative Name entries, one of them must match the host name you request; if there are no SAN DNS entries, the Common Name (CN) of the Subject DN must match the host name.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I am trying to ssh to amazon ec2 instance from shell using the following
I was looking at using Amazon's EC2 service after reading this article: http://www.ibm.com/developerworks/java/library/j-javadev2-4/index.html But
We are using a dedicated Amazon Ubuntu ec2 instance as Cron server, which executed
We're using Amazon EC2, and we want to put an ELB (load balancer) to
I'm considering using Amazon EC2 for a web app with a SQL Server back
I've setup my site on Amazon EC2 server. I am using Route 53 and
We are using openfire server 3.7.1 on Amazon Ec2 linux instance for a chat
I have a few web servers behind an Amazon EC2 load balancer. I'm using
We're looking to move to amazon cloud using EC2 and RDS. I'm looking at
Using EC2 instances (along with Amazon Auto Scaling and Elastic Load Balancing) I have

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.