Questions tagged with Amazon Route 53
Content language: English
Sort by most recent
Route53 domain status is coming as "inactive addPeriod" from last 3 days, what should I do?
Already verified my email
On AWS instance I’ve installed Ubuntu 22 and then WordPress. I am using subdomain of a registered domain. (Domain was registered for another site running on another instance). I am trying to create a new instance for testing and I am using subdomain of registered domain.
I can access the frontend of my WordPress but not the backend.
When I try to login to my wp-admin backend by typing in browser
```
http://aws_route_53_subdomain_name.domain_name.com/wp-admin
```
I get this error
```
"Not Found" The requested URL was not found on this server. Apache/2.4.52 (Ubuntu) Server at <IP address> Port 80".
```
I also tried entering
```
"aws_route_53_subdomain_name.domain_name.com/wordpress/wp-admin",
```
but the result is the same.
When I hit enter I see the URL changes to something like
```
"http:///wordpress/wp-login.php?redirect_to=http%3A%2F%2Ftest.%2Fwp-admin%2F&reauth=1".
```
Can you please help me with this?
I suspect that the issue could be with the fact that I am using subdomain of a first prod instance and pointing it to another (this new) test instance. (I can access the frontend with “mydomainname.com” but not the backend) E.g when I ran
```
sudo certbot --apache
```
I got this error
```
Certbot failed to authenticate some domains (authenticator: apache). The Certificate Authority reported these problems: Domain: www.test.mydomainname.com Type: dns Detail: DNS problem: NXDOMAIN looking up A for www.test.mydomainname.com - check that a DNS record exists for this domain; DNS problem: NXDOMAIN looking up AAAA for www.test.mydomainname.com - check that a DNS record exists for this domain Hint: The Certificate Authority failed to verify the temporary Apache configuration changes made by Certbot. Ensure that the listed domains point to this Apache server and that it is accessible from the internet. Some challenges have failed. Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.
```
Hello, I accidentally deleted the automatically created HostedZone for my .it domain.
I created a new HostedZone and it assigned a new NS record with a different NameServer. Then I updated the Name server in Route53Console/Registered Domains/my-domain-name.it/Name Servers to what the HostedZone assigned to it. Did I do the correct procedure? If so, how much time will it take for the Name servers to update? If not, how can I restore the original HostedZone?
Hey all! Hope your are doing well. I have been trying to write a query service for some internal databases in my VPC. My current setup is API Gateway with a Lambda that queries the database which works fine, but unfortunately I ran into two issues:
- API Gateway default timeout is 30s which is not very long for queries.
- Lambda response size limit is 6mb, which is fine but also not suitable for the biggest queries.
Are there any serverless services I can use to solve this problem? I do require custom domain / authentication. Some solution I thought of were:
- Chunking request, which should work fine but I think 30s is still not very long. It is a temporary solution for now.
- Using ALB as a "api" to trigger lambdas, which would fix the timeout, but response size limit is still 6mb.
- Hosting my own API on a EC2/Container, which I can do but I like serverless solutions.
- Using websockets, but it seems harder to attach existing apps to a WS compared to a REST api.
If somebody has some input would really appreciate it! Thanks in advance.
We have tried requesting for ACM certificates however they just seem be waiting for "Pending Validation" despite we using the DNS method to authenticate and the relevant CNAME being added directly to the DNS of the domain within S3 services.
Check attached screenshot!, wherein we can directly create CNAME records within Route 63
Please help!
I have been trying to create a secure website with a domain name registered in route 53. I Requested a public certificate so that Amazon CloudFront distributions require HTTPS. I created 2 buckets in s3 and selected on Block all public access. I followed the instructions to create a cloudfront distribution in "Configuring Amazon Route 53 to route traffic to a CloudFront distribution". I created OAC and copied the policy to the bucket policy. I created an alias record that points to my CloudFront distribution.
Can't access the website.
If the Block all public access is set to on for a bucket used for a static website, can the website be accessed by routing traffic to a CloudFront distribution.
We have setup multiple endpoints all the same way within our organisation but the api.ecr.eu-west-2.amazonaws.com seems to resolve to the external IP rather than the interface endpoints. An example of the different responses can be seen below, is there a reason for this or a fix?
```
$ nslookup rds.eu-west-2.amazonaws.com
Server: 127.0.0.53
Address: 127.0.0.53#53
Non-authoritative answer:
Name: rds.eu-west-2.amazonaws.com
Address: 172.16.1.60
Name: rds.eu-west-2.amazonaws.com
Address: 172.16.2.132
Name: rds.eu-west-2.amazonaws.com
Address: 172.16.3.168
$ nslookup api.ecr.eu-west-2.amazonaws.com
Server: 127.0.0.53
Address: 127.0.0.53#53
Non-authoritative answer:
api.ecr.eu-west-2.amazonaws.com canonical name = ecr.eu-west-2.amazonaws.com.
Name: ecr.eu-west-2.amazonaws.com
Address: 52.94.53.88
```
I want to transfer my domain to AWS but the extension of the domain - @group is not in the list. Any solutions?
asked 17 days ago
Hi,
We have been trying to setup our cloud-front distribution to work with a backend origin. The distribution is setup fine but the alternate domain name attached to the distribution is not getting resolved. Here is the sequence of steps followed.
1. Create a cloud front distribution - Configure the backend origin, cache behaviors, etc.
2. Update the cloud front distribution - A custom SSL certificate (not from AWS) is imported into the ACM and attached to the distribution and the same has been used as the alternate domain name for the distribution i.e., the alternate domain name is "myapi-demo.example.com" and my SSL certificate has the SAN entry for the same
3. Create an ALIAS record under "example.com" hosted zone in R53
#3 is not working and tried the following options:
* Created a CNAME as some old articles say to use CNAME. Didn't work
* Created an ALIAS record. Didn't work
* Created a new hosted zone in R53 for "myapi-demo.example.com" and added ALIAS record. Didn't work.
* Created a new hosted zone in R53 for "myapi-demo.example.com" and tried creating a CNAME. Didn't work - failed with error "RRSet of type CNAME with DNS name myapi-demo.example.com. is not permitted at apex in zone "
Record name - "myapi-demo.example.com"
Record value - "d3hui35xh0ym6w.cloudfront.net"
Type - [CNAME] [ALIAS]
Bought a domain on route 53.
Need to transfer to GoDaddy/Google domains.
How??
Also is there a possibility of setting up a subdomain on a domain bought from route 53??
TIA
5 days into this billing cycle, and my Route 53 zone has received over 33 million requests for a particular host that I recently deleted. And the associated DNS record was deleted too. I didn't think I would get billed for a deleted host record, but indeed I am according to the billing dashboard. Some initial query logging suggests that there are clients making many redundant requests for this deleted hostname.
I will most likely add back a record that resolves to 127.0.0.1 with a multi-day TTL. That might make whatever code that's repeating the request to stop asking (as much). But excessive and redundant DNS queries has always been a costly problem that I never could get a handle on. I've dealt with the DDOS attacks on the host service for years, but I've never understood how to firewall Route 53 when these clients make redundant requests.
The ideal solution would be that Route 53 would simply ignore requests for the deleted host name (and not bill me for it).
What are my options?
I have a registered domain **xxx.com**.
I would like to make an **aaa.xxx.com** and **bbb.xxx.com** subdomains, and point them to different locations (in my case, CloudFront distributions). I found conflicting documentation even on the AWS Docs about this use case, and there's a lot of confusion out there on the net in different tutorials.
For the time being, I have the following configuration in Route 53 for the public hosted zone **xxx.com**:
```
xxx.com NS ...
xxx.com SOA ...
<rnd>.xxx.com CNAME ... (needed for the ssl cert)
aaa.xxx.com A Routes to CloudFront1
bbb.xxx.com A Routes to CloudFront2
```
If I copy&paste the CloudFront2 location here to the browser, I get to the proper static website I'd like to use. If I go to the address **bbb.xxx.com**, then I see the contents of **aaa.xxx.com***. I have waited 72h+ to wait for the DNS caches to clean up, but still no change unfortunately. I'm suspecting I might be doing something completely flawed here :-)
So, my question is: how should such a normal config would look like where there is a root domain + 2 subdomains pointing to different location? Any articles, links would be more than welcome!