I've just had a chance to read that post.
1]. I have already done what it suggests in the article i.e. I created a CNAME record and pointed my www record at my-loadbalancer-dns-name
This directs traffic correctly for www
2]. The answer also agrees with my point that assigning a static ip to the load balancer itself to get around the problem is self-defeating and renders the loadbalancer pointless. Therefore as a work around I have had to direct my domain.com traffic directly to the static ip of the server (not the load balancer). But this means that traffic is not loadbalanced and doesnt benefit from the ssl certificate associated with the loadbalancer or any rewrite rules created in the loadbalancer.
But my question was how can I redirect my non-www traffic to my loadbalancer?
i.e. CNAME is only for subdomains. e.g. www.domain.com. What about the main domain? Or put another way how can I point example.com to the load balancer?
It appears to me that only real solution is to use a domain dns tool which supports alias records such as the AWS Route 53 service.
Unfortunately what this seems to mean:
Anyone working with clients who manage their own domains through other providers who do not support alias records (which is the vast bulk of customers) appear to have no solution to this issue.
Unless someone can provide a solution to me which proves otherwise?