Please enable JavaScript.
Coggle requires JavaScript to display documents.
M6 demo R53 ACM - Coggle Diagram
M6 demo R53 ACM
route 53
to purchase a domain
-
- check the domain name whether is available
- will appear in pending request. Once approved. will see under register domain
- go to register domain ; USD12 per year
- create a A record set the translate to IP
-
-
concept
from client side perceptive, if use dig cmd can't see if weighted to multiple DNS
TTL
after default 300 second, will try to resolve to new IP
3 Ec2, 70%, 20% and 10%, 70$ percent will be landed on 1 site
-
direct connect
-
Create a public virtual interface for your DX connection. For Prefixes you want to advertise, enter your customer gateway device’s public IP address and any network prefixes that you want to advertise.
Note: Your public virtual interface receives all AWS public IP address prefixes from each AWS Region (except the AWS China Region). These include the public IP addresses of AWS managed VPN endpoints.
Create a new VPN connection. Be sure to use the same customer gateway’s public IP address that you used in the previous step.
Note: The customer gateway can be configured in Border Gateway Protocol (BGP) with an Autonomous System Number (ASN).
Configure your VPN to connect to your VPC. For sample configurations, see Scenarios and Examples.
-
-
NS and SOA
For each public hosted zone that you create, Amazon Route 53 automatically creates a name server (NS) record and a start of authority (SOA) record. You rarely need to change these records.
It lists the four name servers that are the authoritative name servers for your hosted zone. Except in rare circumstances, we recommend that you don't add, change, or delete name servers in this record.
SOA
The start of authority (SOA) record identifies the base DNS information about the domain, for example
-
-
-
-