Server Fault Stack Exchange
Server Fault Stack Exchange

Questions tagged [amazon-route53]

Amazon Route 53 is a highly available and scalable Domain Name System (DNS) web service.

Amazon Route 53 is a highly available and scalable Domain Name System (DNS) web service. It is designed to give developers and businesses an extremely reliable and cost effective way to route end users to Internet applications by translating human readable names like www.example.com into the numeric IP addresses like 192.0.2.1 that computers use to connect to each other.

608 questions
0
votes
0 answers

CloudFront Access Logs Issue

I was tried querying our CloudFront logs using Athena for an error i'm getting but haven't received any results. The query i'm trying using is: SELECT * FROM cloudfront_logs WHERE request_id = >…
samtech 2021
  • 81
  • 7
0
votes
1 answer

How to check if Route53 will speed up my website?

I have an aws ec2 instance in N.Virginia, an Ubuntu machine with everything inside (mysql as well as apache). Basically all these while, I'm running it on one instance alone, with just image backups and sql backups, but no extra instances nor…
Patrick Teng
  • 1
  • 1
0
votes
0 answers

AWS Route 53 Second Level Wildcard CNAME Not Being Overriden

I am trying to configure some CNAME records for our debug server in AWS Route 53. Our current set up is as follows: example.com A example.com NS *.example.com CNAME …
William Gilmour
  • 1
0
votes
1 answer

Multiple Route53 private hosted zones with same domain

Is it possible to configure multiple private hosted zones with the same domain and have them resolve to different servers? PHZ1/VPC1 - example.com -> ServerA in VPC1 PHZ2/VPC2 - example.com -> ServerB in VPC2 Each PHZ is associated with one distinct…
Ian Danforth
  • 103
  • 5
0
votes
0 answers

How can I use name.com's and AWS's nameservers at the same time

I want to use Titan Email extension but it requires changing my nameservers to Name.com's nameservers. The warning message is like that: But I also need to use AWS's nameservers to use Route 53. I've tried to add 8 nameservers (4 of them were…
oynozan
  • 1
  • 1
0
votes
1 answer

AWS Elastic beanstalk cname with and without www

So, I've got a website running in Elastic beanstalk on AWS and I have a custom domain name which points to it, which is managed in Route 53. When I set up the custom domain initially, I just looked up the IP of the default domain name…
haukurhaf
  • 173
  • 1
  • 7
0
votes
0 answers

Using Route 53 DNS name to communicate between ec2 instances within a single subnet

I have 3 ec2 instances in a single vpc and subnet. Each ec2 instance has an elastic ip and a route 53 domain name pointing to it. The domain name is set as the host name in Amazon Linux 2. I am able to use their host name when directly going to the…
frogg
  • 1
  • 1
0
votes
0 answers

Certificate validation issue with subdomains of subdomains

I have a current, production certificate with a wildcard common-name hosted in Amazon Certificate Manager (ACM). I've added a CNAME with a subdomain of a subdomain (like ....) to our Route53 zone that points to our load-balancer (ALB). However,…
Dustin Oprea
  • 560
  • 2
  • 8
  • 19
0
votes
1 answer

Route 53 "Too Many Redirects" but access from ELB works

I have an EC2 running pgadmin. There's a target group pointing to it on port 80. The TG is listening on port 443 but HTTP so it can redirect to the EC2 on port 80. (I previously had it 443 and HTTPs but read online that SSL termination should be…
Wayneio
  • 121
  • 5
0
votes
1 answer

SPF Too Many DNS Lookups issue

In our scenario, We're running into an issue with our SPF records in route53. We are receiving SPF Too Many DNS Lookups because we are using multiple mail services. Is there a way to resolve this? I saw one thread stating to run a look up on the…
Santosh Baruah
  • 21
  • 6
0
votes
0 answers

DNS lookup spam running up Route 53 bill

Throughout 21 we saw around 15M DNS queries/month. In January 2022 we saw almost 300M and I didn't notice.... then February almost 1 BILLION...... and I noticed because of the bill. Amazon isn't really helping yet I told them this is obviously…
dgobaud
  • 1
  • 1
0
votes
0 answers

host vs name for domain information

Is there a difference in the terms "host" vs "name" when talking about records for routing? I have an account with GoDaddy but but all my DNS management onto Route 53. Then I just purchased email through GoDaddy and am setting up the records. When…
pbuzz007
  • 113
  • 6
0
votes
1 answer

How to redirect an old subdomain with Route53

I've redirected an old subdomain blog.mysite.com to my homepage mysite.com with a CNAME record in Route53, but.... it doesn't work. I get no server response at all. Is there something I'm doing wrong? Update: Now I get a 403 from Cloudfront.
Costa Michailidis
  • 235
  • 1
  • 2
  • 9
0
votes
1 answer

Can't access EC2 on domain name, just on IP. Cname is correct, and can route this domain to lightsail server

Thanks for taking the time. I have ported a lightsail instance over to EC2 and am running a t.2 larger server. I am running a wordpress site and the homepage is just a blank white page. I have assigned the ec2 an eleastic IP and can access the…
Liam Montgomery
  • 1
0
votes
1 answer

Acessing my site using www is not working using AWS Route 53 and NGINX

My site is up and running and can be found on the Internet by typing [domain].com address in the browser. When I try to access it using www.[domain].com, it return an error (not found). I'm using Route 53 as a DNS Server with the following…
Mendes
  • 131
  • 1
  • 10
1 2 3
…
40 41