A Python implementation for changing your DNSimple details, when your home WAN ip changes.
Based on the article [here][1].
[1]:http://jasonseifer.com/2011/04/04/auto-update-ip-dnsimple
Usage:
dyndnsimple –domain_id XXXXX –record_id XXXXX –user your@email.com –token XXXXX
1 maintainer
Metadata
1 maintainer
Release files for dyndnsimple 0.0.11
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 | |
|---|---|---|---|---|
| dyndnsimple-0.0.11.tar.gz | 2.4 kB | Without provenance | Details |
Release files / dyndnsimple-0.0.11.tar.gz
| Download URL | dyndnsimple-0.0.11.tar.gz |
|---|---|
| Size | 2.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fe5f0b761f5068aff41fdfc58a5531a2805316e71cdb5609d85d252715ffab18
|
|
BLAKE2b-256 checksum How to use checksums |
a7c5c17200fdd6d9ae4cf97f265bdb686c248c17f0477792fae0b7a1b9e95220
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for dyndnsimple 0.0.11
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.
