I am dealing with some weird inconsistency issues with the dns to my subdomain, and was hoping someone would be able to shed some light!
I have a domain purchased through Google Domains and have a need to use the main domain, and a single subdomain for my api service. With Route 53, i have 2 hosted zones, one for the main, and one for the subdomain, each providing the 4 NS configs, and two aliases back to my Elastic Beanstalk nodes for the www & non www calls.
For my main domain, using WhatsMyDomain, the propagation is pretty much worldwide at all times, but when it comes to my subdomain, it is intermittent and changes throughout the day, where it was working in one location earlier on, it will then stop working.
In Google Domains, i have all 8 NS configurations set in my DNS settings.
I feel like im missing just one piece of something, just can't figure it out
Thanks to Michael - sqlbot for his return question, never even thought about just trying it by adding an alias to the subdomain in the original Hosted Zone! In the docs on AWS, they do provide info on having 2 different zones, which i think thats what i stumbled across when i first started, but i believe there is a bit more setup involved in that route!
Just made the switch, gonna see if this solves the issue!
Related
0
I realise that LightSail is an entry level provision that enables people like me who sadly don't know near enough to tap into what is pretty amazing tech. However, it's very frustrating that things that should work just as a result of a few clicks definitely DO NOT. Furthermore, most of the documentation is outdated or lack sufficient detail. Does AWS really want to charge $18 per month for something this buggy / filling up countless forums with people expressing their difficulties and frustrations??
For over a day now (8+ hours) I have tried in vain to set up a Load balancer connected to two Wordpress / Bitnami Instances. First the DNS related to the LB 7668[...].eu-west-2.elb.amazonaws.com was clearly broken in that clicking that link returned a Safari couldn't open the page error:
Safari can’t open the page “7668[...].eu-west-2.elb.amazonaws.com”
because Safari can’t find the server
“7668[...].eu-west-2.elb.amazonaws.com”.
Having found out the relevant IP I was able to load the page, but still...
But it is when it comes to setting things up within the DNS zone where the trouble really begins. When assigning my domain to a Static IP address associated with one of my instances everything works fine—but obviously the load balancer is not "active"; i.e. traffic to my domain goes straight to the instance. However when assigning the domain to the LoadBalancer (with certificates, validated, etc.) the page instantly "breaks" with the error message:
"Too many redirects occurred trying to open
“https://7668[...].eu-west-2.elb.amazonaws.com”. This might occur if
you open a page that is redirected to open another page, which then is
redirected to open the original page."
At this point there's zero help from within Lightsail and none of the docs (mostly outdated or overly vague) cover this. So I hit various forums, searching and the problem seems to be all over the place in various forms with potential "solutions", none of which however work... I can't help thinking this problem would be very simple for someone knowledgeable to fix, but there's certainly no way within Lightsail to solve this... MEGA FRUSTRATING.
As such, after 8+ hours, I now deleted the Load balancer (not wanting to be charged for something that doesn't work) and returned to serving my website content from a single instance.
What am I missing? Why is such a no doubt simple problem for those in the know, seemingly insurmountable for the kind of audience Lightsail is aimed at? What is the solution?
I am trying to connect my Amplify app to a GoDaddy website and the AWS instructions are not clear on how to do this.
Following these instructions I created a CNAME record to point to my Amplify app.
(Image from the documentation)
I have a "master.xxxxxxxx.amplifyapp.com" and a "feature.xxxxxxxx.amplifyapp.com", am I supposed to use one of these or just the "xxxxxxxx.amplifyamp.com"?
It seems from the docs that these records take up to 2 days to update and I do not want to waste 4 days attempting this by trial and error.
Edit
Following #Rodrigo M's answer I used the 'master.xxxxxxxx.amplifyapp.com' route for the CNAME record but when I go to the page all I see is the error:
This page isn’t working xxxxx.domain.com redirected you too many times.
And then when I look in the Network tab I see that the page did a bunch of 302 redirects where the name and the initiator were "Index.html".
Does anyone have any ideas of what is going wrong?
Each of the AWS Amplify domains that you reference refer to a branch of your app eg master or feature. Use the full domain name eg master.xxxxxxxx.amplifyapp.com as the target of your CNAME record for the branch you want to expose on your custom domain.
All of the standard DNS propagation warnings say allow 24 to 48 hours but in practice it's usually much much quicker so don't worry about waiting for two days too much.
I can see your DNS TTL is set for 1 hour. This value is how long the DNS system will cache your DNS records. Which means you can make a change and it would take up to an hour for those records to be updated throughout the internet. You could drop that to 5 minutes or less if you want to do trial and error testing or make quick switches to a different branch.
Godaddy doesn't support ANAME/ALIAS so you can't connect it properly. However you can forward the domain without www
Scroll down to the Forwarding section of the go daddy DNS page and set up a Temporary (302) http forward from yourdomain.com to www.yourdomain.com
It took about 30min for this to take affect for me.
I have multiple GoDaddy domains that point to AWS DNS Servers, which in turn point to a load balancer and thence to (at the moment) an instance. All but one of these work fine and one steadfastly refuses to work, even after deleting and recreating (multiple times).
Using the SDK I have tried to find a significant difference between Zones / Resource Record Sets and have not come up with anything that would explain it. DNSSTuff has not yielded any clues (nor have a couple of other online tools).
An example of a working domain is care.work, and the failing one is plaitapp.org.
Thanks in advance.
It just appears to have been amazingly slow propogation for one domain, while all the others were almost instant.
So I know that somesites allow you to host web content for you, but they can start to charge an arm and a leg based on how much you want to update it, how much you have, and other things. Pretty much what I want to do is host a personal site for and about me. Essentially access things I need like RPG characters and references, cosplay stuff, gaming stuff, and all that ilk.
I'm going to be investing in a small box that is more or less always on and always online, unless I loose internet for some reason or have to restart a router etc, but I'm running into the issue of I need to buy a static IP which is around $60 a month. That's $60 I don't have or want to spend on a little pet project. And before you suggest or ask, no I don't want just a site like blogger or w/e to do it for me.
My question is, and I know that I've been told this before by a friend I just can't seem to remember what he said, is there a way this can be done without using a static IP address and hosting the site from home still?
Oh I should also add that I'd eventually like this to be something I can host my own RESTful webservice on for small little one off personal apps I'd use for myself too.
Actually you live in an elastic cloud century, there is no need to buy any static IP. You can try these things as follows.
Amazon Web Service. You can get 1 year free trial, EC2 is really wonderful to host whatever you want.
Openshift. You can freely create 3 gears to host your application. The environment is very easy to configure. If you want
to deploy symphony, laravel and some other frameworks, openshift
should be the best choice.
Free web service.
You could use a Dynamic DNS service. You create an account (it often costs money, but there are some plans where it's free if you log in every month), and then install a piece of software on a computer/connect it to your router, and you get a subdomain like network63.example.com, which you can have a CNAME in your Domain's dns records to. Then whenever your IP changes, the software detects it and sends a request to their servers to update the record. I'm actually considering starting one myself. These are generally a lot cheaper than getting another IP address.
I host a few things from home (A gitea server and an ownCloud server), and I haven't needed this as although I don't have a static IP, it doesn't change very often, and it's easy enough to update the record after my router restarts or there is an outage (very rare), although this probably varies by ISP.
Websites that have sort of a secondary domain.
What are links like these called?
Can it be done trough code or is it a domain thing?
This isn't a coding question - this is related to network and DNS administration.
The "drive" part of "drive.google.com" is just a subdomain or machine name on the "google.com" domain. As far as DNS is concerned, it is even easier - these are just additional entries in your DNS configuration. There is almost nothing special that needs to be done.