Currently my domain name adthrone.com is pointed to ec2 instance ip 5x.xx.xx.xx
That domain result is HTTP
So I created a load balancer with this link https://adthrone-loadbalancer-1188159040.us-west-2.elb.amazonaws.com/
Now, Is that even possible to change the DNS pointing of
5x.xx.xx.xx
to this
https://adthrone-loadbalancer-1188159040.us-west-2.elb.amazonaws.com/
I tried to contact my DNS Provider BlueHost. But they seems do not want to change it. Because on my bluehost screen. If I manually change it. From EC2 IP to Load Balancer there is an error that the link is not applicable.
The load balancer is working fine, it has only mixed content that needed to fix. But the issue is that possible to change the DNS pointing from IP to Link?
Use a CNAME record instead. You can put adthrone-loadbalancer-1188159040.us-west-2.elb.amazonaws.com in the value field of the CNAME record.
Related
I'm new to AWS EC2 hosting, I have created an instance that has a 'cPanel-WHM for Linux' security group name; by using amazon Route 53 I have set a hosted zone, which I use to link with my domain from NameCheap. My domain from Namecheap is pointing to this hosted zone which has an A record pointing to the IP address of my instance. I have logged in to Cpanel direct by using an IP address with port:2087 and adding an index.php file that contains some simple code to display the welcome note. but whenever I go to this domain I get the default CGI page
"cgi-sys/defaultwebpage.cgi"
I have checked my DNS propagation and I have seen the DNS is propagated. I have tried several times, I thought there was a place I mess with instance settings but ended up with the same problem. Is anyone have any idea what is going on? Thanks in advance
Good evening, I am currently trying to set up a load balancer for my server, I successfully set everything up, however when I go to google domains to set ip record I get the following error "mysite.com unexpectedly closed the connection."
http://prntscr.com/npm04o
http://prntscr.com/npm0ot
Also when i type the ip manually in the browser I get the same error. However when I set my ip record to a VM machine ip that comes from my instance group the load balancer ip starts to redirect to my site. I would like to get the load balancer ip to work with my google domain records.
Picture of configuration
http://prntscr.com/npm3ye
I think you are connecting to the load balancer using HTTPS. You do not have a front-end configured for HTTPS. Specify http:// and try again. If this is not the case, then go to Stackdriver and check the logs for your HTTP(s) Load Balancer.
Note: You have not provided enough information in your question. You need to provide the frontent, backend and healthcheck configurations.
Once you have everything working, your DNS resource record TTL should be longer than 1 minute - clients will constantly have to resolve your DNS names. Using a CNAME instead of A record adds another lookup. Use an A record instead.
My website is setup on ECS behind a load balancer. I want my A Record to point to the load balancer, but Elastic Load Balancer's can't have static/elastic IP's assigned to them.
The DNS of a load balancer may be something like my-loadbalancer-1234567890.us-west-2.elb.amazonaws.com , and you can point a CNAME to it but not an A Record.
(We need an A Record to make MX records work properly, otherwise I would just use a CNAME).
Our domain name is hosted outside of AWS (i.e. not on Route53).
A very clunky and non-scalable way to handle this would be to setup a webserver (NGINX, IIS, etc) with an Elastic IP and simply have that redirect to the www version of my site, which uses a CNAME to point to the load balancer.
This is something I really want to avoid, for maintainability reasons and for scalability.
What is the quickest and most straight forward way to either point an A record to an ELB, or re-route an income request from an IP (mysite.com) to something else (www.mysite.com).
Extra
Here's a similar question, but dated. One answer say's it's not possible, and the other answer seems dated, and I don't believe is relevant.
You need to have your domain name hosted in Route 53 in order to have an A record pointing to the ELB.
Here's a blog post on how to use a static ip in application load balancer, but its not very straight forward.
You could also have a look at the classic load balancer, prett ysure that you can use elastic IPs with that one.
I had a question about using the URL in my Load Balancer - and using it as the A Record for my DNS entry via GoDaddy...GoDaddy doesn't allow a URL, and insists on the A Record being an IP address and no other format. But I don't see this option available in the Load Balancer I created, only a URL.
What I have so far is this..
I've created a Load Balancer successfully using both HTTP and HTTPS, along with the RapidSSL cert I purchased and imported.
When I open my new Load Balancer item in EC2 dashboard, under the Description tab, I see an auto-generated URL next to DNS Name: http://ACThttp-617756314.us-east-2.elb.amazonaws.com (A record)
The above URL works fine in my browser. I went to plug this into GoDaddy'a A record in the DNS settings --- but apparently GoDaddy only allows an IP address to be used as an A Record...and not a URL like the one generated by EC2. I find this confusing since it literally says "A Record" next to this generated URL in my Load Balancer.
Does this mean I need to generate an IP Address inEC2 dashboard, so that I can use it in GoDaddy DNS settings? I'm guessing this is done via Route53...or could I skip this altogether and still find a way to connect my new Load Balancer to my DNS A record some other way?
However this is done, any help would be appreciated. If Route53, what are the exact steps I need to take? Or any other solutions, as much detail you could provide would be so so so helpful.
I've done this a few times successfully in the past, but it was a while ago and I can't recall how I connected them to the DNS properly.
Thanks!
You should use a CNAME record (not an A record).
A CNAME record points to another DNS name, whereas an A record points to an IP address.
Load Balancers should always be addressed by their DNS Name, so use a CNAME record.
I am running my website on AWS.
I have one load balancer for my two web servers. My load balancer doesn't have a static IP address, it has a domain name.
I want my traffic to come only via the load balancer. I am using Cloudflare's DNS instead of Route 53, because that's what the Cloudflare instructions said.
I cannot add the load balancer's IP as an A record because it is dynamic and cannot be added through Cloudflare's DNS panel (Not like Route 53). Help me I am stuck in this situation. No solution is offered by Cloudflare so far.
Has anyone faced the same issue?
You can set your Cloudflare record as a CNAME alias of your ELB's A record
See:
https://support.cloudflare.com/hc/en-us/articles/200168986-How-do-I-add-a-Amazon-ELB-Elastic-Load-Balancing-record-to-CloudFlare-
I suggest to manage your domain DNS with CloudFlare.
Add a CNAME record for your subdomain demo which points to that IP.
On CloudFlare Console go to Crypto > Origin Certificates. Create a new one with RSA, then import it to AWS Certificate Manager at us-east-1. For the certificate chain use this.
Be sure that Always use HTTPS in Crypto tab is on.
After some minutes you should be using your domain pointing to AWS with HTTPS working fine.
That's what I did to make a subdomain to work with an AWS API endpoint with SSL.
I decided like this:
I created in the cloudflare, in the DNS table, two CNAME records that point to the dns name of the load balancer generated in aws.
The first record created must contain in the "Name" field, the value "www" with the "content" field pointing to the url of the load balancer in aws. The second record, on the other hand, points to root, containing the value "#" in the "Name" field and "Content" pointing to the same load balancer server in "aws".
See the images below for a better understanding.
I've tried with the Cname record with target as Load Balancer DNS name, but the website is not secured.
If you need static IP for your Load Balancer then use Global Accelerator. It will provide you a static IP. After that create an A record with domain name in cloud flare and content with your Static IP provided by Global Accelerator and the Proxy status must be Proxied.