AWS Route Problem

0

Hello,

I bought a domain via Aws and created a bucket from S3. I set all the permissions of my bucket, I made it static. I can enter from the static link. I created a hosted zone from Route 53 to my domain and I opened a record and set this bucket. But when I type the address of my website address, I cannot access it. where could I have done wrong. Thank you.

asked 6 months ago213 views
13 Answers
0

OK, so you've bought mydomain.com and you've created buckets called mydomain.com (and maybe also www.mydomain.com ?) and you've put your website content in these buckets and set static website hosting. Now you can successfully hit http://mydomain.com.s3-website-[region].amazonaws.com ?

All good so far.

Sounds like in the hosted zone in Route 53 you need to create an A record for mydomain.com with a value of s3-website-[region].amazonaws.com. And perhaps also a CNAME for www.mydomain.com with a value of www.mydomain.com.s3-website-[region].amazonaws.com

It sounds like you're nearly there, if you still have trouble then can you post the error message any any screenshots on here?

This user guide is useful for troubleshooting https://docs.aws.amazon.com/AmazonS3/latest/userguide/website-hosting-custom-domain-walkthrough.html

profile picture
EXPERT
Steve_M
answered 6 months ago
0

thanks for reply but as I said above, I created a record. If we're going through addresses;

I prepared a simple html like this: http://gokhanaltindirek.com.s3-website.eu-central-1.amazonaws.com

Record name: gokhanaltindirek.com Type: A Routing Policy: Simple Alias: Yes Value/Route traffic to: s3-website.eu-central-1.amazonaws.com.

Unfortunately it did not happen.

answered 6 months ago
0

Look at this https://dns.google/query?name=gokhanaltindirek.com

The four IP addresses in square brackets after extra_text are the four nameservers associated with this record. These IP addresses resolve to the following:

$ getent hosts 205.251.192.96 205.251.196.204 205.251.195.239 205.251.198.240
205.251.192.96  ns-96.awsdns-12.com
205.251.196.204 ns-1228.awsdns-25.org
205.251.195.239 ns-1007.awsdns-61.net
205.251.198.240 ns-1776.awsdns-30.co.uk
$

This matches the nameservers in whois for your domain https://who.is/whois/gokhanaltindirek.com

Are these the same as the nameserver (NS) records in your Route 53 hosted zone for gokhanaltindirek.com ?

In Route 53 have you got DNSSEC signing enabled? Try disabling it.

profile picture
EXPERT
Steve_M
answered 6 months ago
0

In Route 53 DNSSEC signing is diabled but the NS on Route 53 is as follows;

ns-340.awsdns-42.com. ns-998.awsdns-60.net. ns-2034.awsdns-62.co.uk. ns-1249.awsdns-28.org.

unfortunately it does not match.

How can I solve this?

answered 6 months ago
0

Did you purchase gokhanaltindirek.com from AWS in Route 53, in the same account? A hosted zone should have been created with that name, and the NS records would have been preset within it. So I don't unsderstand how it's ended up like this.

Anyway, the way to resolve it now is to delete the four current (bad) NS records and populate it with the correct records as seen in https://who.is/whois/gokhanaltindirek.com

The TTL (time-to-live) will probably be set to something large like 172800 (i.e. 48 hours), so before deleting and adding any records drop this to something small like 300 (5 minutes) to ensure the updates propagate much quicker https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/migrate-dns-domain-in-use.html#migrate-dns-lower-ttl

profile picture
EXPERT
Steve_M
answered 6 months ago
0

yes, I bought the domain with the same account. I did what you said as seen in the attachment, but the same problem persists.attachment

answered 6 months ago
0

You have a typo - ns-1776.awsdnd-30.co.uk should be ns-1776.awsdns-30.co.uk

profile picture
EXPERT
Steve_M
answered 6 months ago
0

I changed it but it still doesn't work. I put it as an attachment again. I've been having a strange problem for a few days.

IMAGE

in case this helps; Enter image description here

answered 6 months ago
0

I'm all out of ideas now. You've dropped the nameserver TTL to 5 minutes in the hosted zone, updated the NS records so it aligns with what's in the domain registration, and DNS (and dig) still fails. I would suggest raising a support call with AWS as the next step (I don't work for AWS so I can't see inside your account). Even if you're on a Basic Support plan (which would preclude you from raising a support call most of the time) you can still do so under Account and Billing -> Service: Billing -> Category: Domain Registration Issue

https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-contact-support.html

I still don't understand how your NS records managed to get out of alignment until you straightened them out a couple of hours ago. When you purchased the gokhanaltindirek.com domain last week through Route 53, a public hosted zone of that name should have automatically been created in Route 53 in the account that purchased the domain, and the NS records should have been correct.

You don't have two public hosted zones with the same name do you?

I think a support call with AWS is the best way to go, and point them to this re:Post question if they want into on what's been tried already. It would also be useful if you could post an update with what the solution turns out to be.

profile picture
EXPERT
Steve_M
answered 6 months ago
0

There was only 1 hosted zone. As you said, I wrote to the support section and I will inform you when the answer comes. Thank you very much for your help. Sincerely regards.

answered 6 months ago
0

if you are setting a public website , Amazon S3 website endpoints do not support HTTPS or access points. if your link is Https you need to use Amazon CloudFront to serve a static website. Also please confirm bucket name are same as your domain name.

Sachin
answered 6 months ago
0

My link is http, bucket name is the same as my domain name.

answered 6 months ago
0

Here's the solution;

When these values don't match, your website or web application can be intermittently unavailable on the internet. To make these values match, please perform the following procedure:

  1. Go to the hosted zones page in the Route 53 console
  2. Choose the radio button next to the name of the hosted zone that you want to update. The hosted zone has the same name as your domain registration. The Hosted Zone Details pane displays a list of the name servers that Route 53 assigned to the hosted zone when it was created.
  3. Copy the names of the four name servers in the Name Servers field.
  4. Choose the name of the hosted zone, and a list of the records in the hosted zone appears.
  5. Choose the record that has a value of NS in the Type column.
  6. In the Value field, paste the names of the name servers that you copied in step 3.

----------------- and --------------

When you're finished updating the NS record, confirm that the name servers that are associated with the domain registration match the name servers that Route 53 assigned to the hosted zone. Perform the following procedure:

  1. Open a text editor and paste the names of the four name servers that you got in the previous procedure. The domain registration page doesn't let you paste all four name servers at once.

  2. Go to the domain details page for your domain. In the following URL, replace DOMAIN with the name of your domain

  3. Choose Add/Edit Name Servers.

  4. One at a time, copy the name servers that you pasted into a text editor in step 1, and replace the existing name servers for your domain.

  5. Choose Update.

The update can take 2-24 hours to take effect.

answered 6 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions