Netlify DNS Manager
The netlify-dns-manager is a command-line tool designed to manage DNS records for domains hosted on Netlify. It allows users to either import DNS records from a local zone file into Netlify or export Netlify DNS records to a local zone file.
Features
- Import DNS Records: Upload DNS records from a local DNS zone file to Netlify.
- Export DNS Records: Save DNS records from Netlify to a local zone file.
Installation
To install netlify-dns-manager, you need Python 3.6 or higher. You can install this package using pip:
pip install netlify-dns-manager
Usage
Command Line Interface
netlify-dns-manager can be run from the command line with several options.
Importing DNS Records
To import DNS records from a zone file to Netlify, use the following command:
netlify-dns-manage import <token> -zp <path_to_zone_file> -d <domain_name>
<token>: Your Netlify access token for authentication.<path_to_zone_file>: The path to your local DNS zone file.<domain_name>: The domain name for which the DNS records will be managed.
Exporting DNS Records
To export DNS records from Netlify to a local zone file, use the following command:
netlify-dns-manage export <token> -d <domain_name>
<token>: Your Netlify access token for authentication.<domain_name>: The domain name for which the DNS records will be managed.
Parameters
execution_type: Specify'import'to upload DNS records to Netlify from a zone file, or'export'to save Netlify DNS records to a local zone file.token: Netlify access token for authentication.zone_path: Path to the local DNS zone file (required for import only).domain_name: Domain name details.
Contributing
Contributions are welcome! For major changes, please open an issue first to discuss what you would like to change.
License
This project is licensed under the MIT License - see the LICENSE.md file for details.
Support
If you have any questions or encounter any issues, please open an issue on the project's GitHub issue tracker.
Metadata
Release files for netlify-dns-manager 0.4
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 | Actions |
|---|---|---|---|---|
| netlify_dns_manager-0.4.tar.gz | 5.9 kB | Without provenance | Details for netlify_dns_manager-0.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| netlify_dns_manager-0.4-py3-none-any.whl | Python 3 | none | any | Details for netlify_dns_manager-0.4-py3-none-any.whl |
Total release size: 13.8 kB
Release files / netlify_dns_manager-0.4.tar.gz
| Download URL | netlify_dns_manager-0.4.tar.gz |
|---|---|
| Size | 5.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7995cf5b26f721694772543c3c2c0ac9079ab9555975802d1ddacab354163128
|
|
BLAKE2b-256 checksum How to use checksums |
8ea8025ecf251cac5d2d7e4643c752d6d41c564b1e056a8f4b54cf4977407134
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.12.3
|
Release files / netlify_dns_manager-0.4-py3-none-any.whl
| Download URL | netlify_dns_manager-0.4-py3-none-any.whl |
|---|---|
| Size | 7.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
53eaca01ec95f345a5bfa9bb3c8c3e073df3fb3885614fc7f2208d79e070736a
|
|
BLAKE2b-256 checksum How to use checksums |
ac21e0251366968c3f2147e5b7b2fee592685633f648888e12cad5b1e01f3461
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.12.3
|
Security for netlify-dns-manager 0.4
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.