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
1 answer

AWS CloudFront and apex domain with third-party domain registrar

I have an existing domain example.de, that should be served via AWS CloudFront and its SSL certificates provided by ACM. That domain is registered and managed at a third-party registrar. Setting up CloudFront and ACM for the www.example.de domain…
user1933738
  • 247
  • 1
  • 6
0
votes
1 answer

AWS: Multi region APIGateway with single endpoint

I'm trying to design a highly available API. I'd like to deploy the API to multiple regions to increase reliability, but to have a single URL so that clients don't have to use multiple URLs. I'm not concerned with geographic routing. I'd like to…
marti H
  • 1
  • 1
0
votes
1 answer

AWS Route 53 pricing for hosted zones and domain names

Novice dealing with DNS services here. I'm setting up an ECS cluster of Fargate containers that need to communicate with each other. They are deployed as separate services in the same cluster, so I wanted to use CloudMap in order to automatically…
gsantos
  • 3
  • 2
0
votes
3 answers

GCP to AWS Hosted Zone migration

I have a publicly hosted zone in GCP for example.com. I want to move the hosted zone to AWS route 53. Is there a tool which can make this process easier? Alternate: I will export the records using gcp cloud cli, modify the file to match the AWS…
Jeetendra Pujari
  • 109
  • 2
0
votes
0 answers

Web application not serving with Route53 under wifi?

I have a node application running in an Ec2 container on port 443. I've added an Elastic IP to the container. When I reference the Elastic IP or IPv4 DNS in the browser, I can see my application. I added a Loadbalancer and attach it with the IP…
Scott
  • 101
0
votes
1 answer

Why is Route53 registered domain not able resolve EC2 IP while I can access the IP without domain?

This is what I have right now: A domain which is registered with Route53. This domain resides with Route53 only. An nginx listening on port 80 which is then running on EC2 instance. I can view the webpage served by nginx when I go to this IP on…
Santosh Kumar
  • 131
  • 7
0
votes
0 answers

Unable to resolve host domain name

Recently, I noticed that time to time my client is unable to resolve my domain name. I have a Lightsail instance with a static IP, a Lightsail DNS Zone, and finally a Route53 domain name. The only thing I did for now is adding the Lightsail DNS Zone…
user907169
0
votes
0 answers

AWS DNS alias for VPC local resources

I'd like to be able to provide a resource SRV that lives in two different VPCs. So I'd give them DNS names srv.vpc1.corp.com and srv.vpc2.corp.com. What I'm trying to figure out is if I can provision a srv.corp.com which always goes to the in-VPC…
Mark Robinson
  • 101
  • 2
0
votes
1 answer

Cannot access my website with the custom domain name when using VPN

I developed a website and deployed it using EC2 on AWS and redirected the domain name which I bought from domain.com to the EC2 IP address with Route 53. The site is accessible when I'm not using VPN. However, when I start using the VPN, I cannot…
Yichong Chen
  • 11
  • 3
0
votes
2 answers

Strange requests keep coming to my gateway API on AWS

I have a simple HTTP service built with AWS lambda and API gateway. The Domain pointing to the gateway is hosted by Route53 and the gateway uses certificate from Certificate Manager. It's absolutely fresh with sole "service is running" text on index…
glowka
  • 111
  • 4
0
votes
2 answers

A record in Route 53 doesn't resolve

I added an A record in my Route 53 hosted zone pointing to the CloudFront. But for some reason, it doesn't work. When I do dig mywebsite.com I get ; <<>> DiG 9.16.1-Ubuntu <<>> mywebsite.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<-…
Dmitrii Mikhailov
  • 199
  • 1
  • 1
  • 10
0
votes
1 answer

A CNAME pointing to 2 different A Records set up with Primary/Secondary Failover Routing?

Considering records like: host.example.com as a CNAME to: host01.example.com and host02.example.com (on two separate records). I want to set up those A records to be with a Failover routing policy. Record Name Type Routing Differentiator …
Kahn
  • 115
  • 1
  • 7
0
votes
0 answers

Is it possible to alias a non aws service with AWS Route 53

We have a domain wich is managed on AWS 53. Is it possible to create an alias record in AWS route 53 to refer to a public IP address (for instance AZURE VM public IP). So that I could use this example "azvm.domain.com" to reference to the Azure VM .
YusufD
  • 11
  • 1
  • 4
0
votes
1 answer

Why is AWS Route 53 / Application Load balancer resolving a multilevel subdomain

Within AWS I terminate TLS at an Application Load Balancer. I have configured a wildcard TLS certificate with AWS' Certificate Manager (ACM), e.g. *.example.com. I have AWS Route 53 resolving *.example.com, but I have nothing for *.*.example.com as…
Darragh
  • 103
  • 1
0
votes
2 answers

Does AWS Route 53 private DNS work with Latency Based Routing?

Looking to setup a private DNS hosted zone in AWS Route 53. I would like to know if this configuration supports Latency Based Routing.
BillMan
  • 164
  • 8
1 2 3
…
40 41