moving everything to active or retired vs incubating and graduated
All checks were successful
Reese's Arch Toolbox / build-and-push-arch-toolbox (push) Successful in 14s
All checks were successful
Reese's Arch Toolbox / build-and-push-arch-toolbox (push) Successful in 14s
This commit is contained in:
30
active/aws_route53/aws-route53.md
Normal file
30
active/aws_route53/aws-route53.md
Normal file
@@ -0,0 +1,30 @@
|
||||
# Network Management
|
||||
|
||||
- [Network Management](#network-management)
|
||||
- [Reeseapps vs Reeselink](#reeseapps-vs-reeselink)
|
||||
- [Reeselink Addresses](#reeselink-addresses)
|
||||
- [Reeseapps Addresses](#reeseapps-addresses)
|
||||
|
||||
## Reeseapps vs Reeselink
|
||||
|
||||
.reeseapps domains are for hosted service that do something. They are usually accessible via the
|
||||
web and are usually public. Web apps, Minecraft servers, other game servers, etc. are all reeseapps
|
||||
domains.
|
||||
|
||||
.reeselink domains are for linking machines together. They are for SSH, Cockpit, NFS, SMB, ISCSI,
|
||||
and other machine to machine connections. They can be public or private and are mostly for
|
||||
convenience.
|
||||
|
||||
## Reeselink Addresses
|
||||
|
||||
See `example-record-file.json` for example contents of `file://active/aws_route53/secrets/aws/reeselink.json`.
|
||||
|
||||
```bash
|
||||
aws route53 change-resource-record-sets --hosted-zone-id $(cat active/aws_route53/secrets/reeselink-zoneid) --change-batch file://active/aws_route53/secrets/reeselink.json
|
||||
```
|
||||
|
||||
## Reeseapps Addresses
|
||||
|
||||
```bash
|
||||
aws route53 change-resource-record-sets --hosted-zone-id $(cat active/aws_route53/secrets/reeseapps-zoneid) --change-batch file://active/aws_route53/secrets/reeseapps.json
|
||||
```
|
||||
Reference in New Issue
Block a user