AWS ROUTE53 - s50600822/Notes GitHub Wiki
How do I associate a Route 53 private hosted zone with a VPC on a different AWS account?
How can I redirect one domain to another in Route 53?
Route 53 Resolver for Hybrid Clouds
Route 53 Resolver inbound endpoint to resolve DNS records in a private hosted zone
create-vpc-association-authorization
https://aws.amazon.com/blogs/architecture/using-route-53-private-hosted-zones-for-cross-account-multi-region-architectures/ https://aws.amazon.com/blogs/networking-and-content-delivery/centralized-dns-management-of-hybrid-cloud-with-amazon-route-53-and-aws-transit-gateway/
Feature | CNAME Record | ALIAS Record |
---|---|---|
Supported Zone | Can be used in any DNS zone in Route 53. | Can only be used within Route 53 hosted zones. |
Target | Can point to any DNS record or domain. | Can point to specific AWS resources (e.g., Elastic Load Balancers). |
Root Apex | Cannot be used for the root domain (e.g., example.com). | Can be used for the root domain (e.g., example.com). |
TTL Control | TTL is controlled by the authoritative DNS for the target. | TTL is controlled by Route 53 and set to a low value (e.g., 60 seconds). |
AWS Integration | Cannot be used with some AWS services like AWS CloudFront. | Specifically designed for seamless integration with AWS services. |
DNS Resolution | Results in an additional DNS lookup for each resolution. | Resolves to the target IP address without additional lookups. |
Health Checks | Cannot be used for health checks or failover configurations. | Can be used for health checks and failover configurations. |
Can point to rootdomain | NO | YES |
Res $ | YES | FREE |