# Network Management

- [Network Management](#network-management)
  - [Reeseapps vs Reeselink](#reeseapps-vs-reeselink)
  - [Reeselink Addresses](#reeselink-addresses)
  - [Reeseapps Addresses](#reeseapps-addresses)
  - [Converting Unifi Records to AWS Records](#converting-unifi-records-to-aws-records)

## 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
```

## Converting Unifi Records to AWS Records

The script `unifi_to_aws.py` will create a file at
`secrets/unifi_reeselink_records.json` which contains all `reeselink.com`
domains in the unifi server converted to AWS route53 batch format. Simply run
the script and then use that file to update reeselink.com records.

```python
python active/aws_route53/unifi_to_aws.py
```