My DNS domain for numeet.com (just a spare domain) was pointed to Route 53, and resolution of numeet.com and www.numeet.com is working fine.
However, a subdomain called learn.numeet.com is not working, despite a CNAME.
The main A record points to an elastic load balancer where a couple of servers are dealing with web traffic (once SSL is terminated on the ELB)
The CNAME resolves to a specific IP address of one of the above servers (the only one that has Moodle installed). That server has a vhost setup and an elastic IP address to the subnet on the server and HTTP is fully open (and already working with the ELB).
However, when 2 days after setting this up I try to got to http://learn.numeet.com, the DNS still does not resolve.
On the EC2 instance, I can run dig learn.numeet.com, and that resolves to the IP address fine. However, even from the EC2 server, ping learn.numeet.com doesn't work.
Is there a problem with Route 53 having multiple routes to the server (www.numeet.com via ELB and learn.numeet.com via Elastic IP) ?
What am I missing?