Catalog Zones Tools
catz2nsd
catz2nsd configures NSD using catalog zones. It reads a configuration file (default /etc/nsd/catz2nsd.conf) and updates NSD using nsd-control. catz2nsd must be able to read the list of currently configured zones in NSD (default /var/lib/nsd/zone.list) in order to determine which zones to add, remove, or update.
The configuration file is NSD-like as described below:
catalog-zone:
name: <string>
request-xfr: <ip-address> <key-name | NOKEY>
zonefile: <filename>
pattern: <pattern-name>
key:
name: <string>
algorithm: <string>
secret: <base64 blob>
zones2catz
zones2catz creates a catalog zone from a comma-separated text file containing one zone per line (and optionally the intended group for the zone) and writes its output to a file or stdout.
References
Metadata
Release files for dnscatz 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| dnscatz-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for dnscatz-0.1.0-py3-none-any.whl |
Release files / dnscatz-0.1.0-py3-none-any.whl
| Download URL | dnscatz-0.1.0-py3-none-any.whl |
|---|---|
| Size | 7.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6c60e067f24e0e1c7637844750da6f6483b7feb7d0893bd8860b52bd3fb0706a
|
|
BLAKE2b-256 checksum How to use checksums |
1359f94c4fff3e2899825343954eee358b71e4c963a27c023af79299189240af
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.10.6
|
Security for dnscatz 0.1.0
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.