Cirrus
dns_setup reads a simple yaml file that only defines credentials, domains and bind style zone files used to define the domains.
Amazon Alias entries are treated as a TXT dns type with _alias added to the domain name and the value starting with ‘Alias ‘. This is to work around the dnspython library does not allowing invalid dns types. An example alias in a zone file, (replace hosted_zone_id and dns_name): $TTL 600 ; 10 minutes - Alias entries always have a ttl of 600 _alias IN TXT “Alias hosted_zone_id dns_name.”
update_host.py will update a single host entry in an route 53 domain. It relies on environment variables and command line arguments rather than yaml. I use it to accomplish dynamic dns for ec2 with the simple init script found in contrib. Since this will potentially be on many many machines for security I suggest you use a dns subdomain and different AWS credentials with this script.
1 maintainer
Metadata
1 maintainer
Release files for Cirrus 0.10
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| Cirrus-0.10.tar.gz | 9.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| Cirrus-0.10-py2.7.egg | Legacy Egg format | - | - | Details |
Total release size: 24.5 kB
Release files / Cirrus-0.10.tar.gz
| Download URL | Cirrus-0.10.tar.gz |
|---|---|
| Size | 9.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9043b022ec947d8c8b9b329eb19778e0489fd492d7c865b77254f6e18e9142a3
|
|
BLAKE2b-256 checksum How to use checksums |
a689d04920339bfbe9455eba3b35767ae5a4023c4aa3fb8847afa48ecd19be95
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / Cirrus-0.10-py2.7.egg
| Download URL | Cirrus-0.10-py2.7.egg |
|---|---|
| Size | 15.4 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
bd58f89420105e8e1b25dda4664fa4a1522c84fa5ee65ac41730ead790a4a6aa
|
|
BLAKE2b-256 checksum How to use checksums |
6e664668124dedf878bd5da15195569677c087855e1686223992b980710bdb77
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for Cirrus 0.10
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
