<!--
SPDX-FileCopyrightText: 2024 Max Mehl <https://mehl.mx>
SPDX-License-Identifier: GPL-3.0-only
-->
# INWX DNS Recordmaster
[](https://github.com/mxmehl/inwx-dns-recordmaster/actions/workflows/test.yaml)
[](https://api.reuse.software/info/github.com/mxmehl/inwx-dns-recordmaster)
[](https://pypi.org/project/inwx-dns-recordmaster/)
[](https://pypi.org/project/inwx-dns-recordmaster/)
Manage DNS nameserver records of INWX domains via YAML files and API requests. Lightweight, fast, version-control ready.
Note: This is no official software project by INWX, it just kindly uses their public API.
- [Overview](#overview)
- [Install](#install)
- [Configuration](#configuration)
- [App/API configuration](#appapi-configuration)
- [DNS records configuration](#dns-records-configuration)
- [Run the program](#run-the-program)
- [Synchronisation mode](#synchronisation-mode)
- [Conversion mode](#conversion-mode)
- [Contribute and Develop](#contribute-and-develop)
- [Troubleshooting](#troubleshooting)
- [Debug and dry-run](#debug-and-dry-run)
- [I deleted all my productive records!](#i-deleted-all-my-productive-records)
- [Simulate API response](#simulate-api-response)
- [URL records](#url-records)
- [License](#license)
## Overview
This tool enables customers of [INWX](https://www.inwx.de) (formerly known as InterNetworX) to manage the DNS entries/records of their domains via files. This has multiple advantages:
* Version-control of nameserver entries, therefore a good record of what has changed over time.
* Very simple copy/paste of existing entries for new domains, e.g. when a new alias domain has been added.
* Enables search/replace, e.g. of IP addresses.
* Work can be done offline and quicker, and pushed once it's done. No waiting times for the sometimes slow web interface.
Configuration of the DNS records is done in YAML files with a quite simple structure. It is compared against the "remote" state, pulled via the INWX API. If necessary, minimal API requests will be issues to align the remote state with the local configuration.
## Install
The tool depends on the following applications:
* Python 3
You can install the latest release via `pip3 install inwx-dns-recordmaster`
The tool is executable with `inwx-dnsrm`. The `--help` flag informs you about the required and available commands.
## Configuration
There are two types of configuration:
1. App configuration: INWX API login data
1. DNS records configuration: the desired state for each configured domain
### App/API configuration
You need to add your credentials for the API authentication. The file will be created automatically on first run if it doesn't exist. On Linux systems, it will be located in `~/.config/inwx-dns-recordmaster/config.toml`.
In any case, you will need to add your INWX username and password, be it of the main or a sub-account. If you use two-factor-authentication you may add the shared secret as well, although this may weaken your security. You may also want to ask the INWX support to limit the login to specific IP addresses.
### DNS records configuration
DNS records are configured in YAML files. If you have multiple domains, you can either put all definitions in one big file, or create multiple ones. The `--dns-config` flag of the program just needs to point to a directory in which at least one such file is present. Only files ending with `.yaml` or `.yml` are considered.
You can find an example DNS records configuration in the file [`records/example.com.yaml.sample`](records/example.com.yaml.sample). Here is a much shorter example:
```yaml
example.com:
# Records configuring example.com
.:
- type: A
content: "192.168.13.37"
- type: MX
content: "my.mailhost.tld"
prio: 10 # priority of MX record, relevant with multiple MX
# *.example.com
"*":
- type: A
content: "192.168.13.37"
# cloud.example.com
cloud:
- type: CNAME
content: cloudprovider.tld
ttl: 86400 # long TTL
```
Please note that the general idea of this program is that ALL records are managed locally. In the above example, it would delete the `NS` records of the domain which is a bad idea.
However, there are default and extendable exceptions:
* By default, records of the type `SOA` are not considered as they change upon each change and are handled well by INWX. You can add additional record types with the `--ignore-types` argument if you don't want to handle them.
* You can also blatantly ignore records that exist at INWX but not in your local configuration, using the `--preserve-remote` flag. This way, you only *update existing* and *add new* records, but don't *delete unconfigured* records at INWX.
If you already have a domain configured at INWX whose records you want to migrate to your local DNS records configuration, there is the convert command: `inwx-dnsrm convert --domain example.com`. This enables you to take the DNS config at INWX for a specific domain, put it in your local configuration, and start from this point onwards. You don't have to manually write long configuration files from scratch, unless you want to.
## Run the program
You can execute the program using the command `inwx-dnsrm`. `inwx-dnsrm --help` shows all available arguments and options.
The program has two main commands: `sync` and `convert`.
### Synchronisation mode
`sync` covers the main functionality, managing INWX domain records based on local configuration files whose format is explained above.
Some examples:
* `inwx-dnsrm sync -c records/`: read the DNS records from the `records/` directory, match them with the remote, and call the API to add, update, and delete entries for each locally configured domain.
* `inwx-dnsrm sync -c records/ -d example.com`: like the above, but only check the domain `example.com` and ignore all other locally configured. If you have many domains, this may speed up operations.
* `inwx-dnsrm sync -c records/ -p`: run normally, but do not delete nameserver entries at INWX which are not configured locally.
* `inwx-dnsrm sync -c records/ --dry`: run the whole program but do not make any changes at INWX. Very helpful if you just configure a new domain.
* `inwx-dnsrm sync --debug -c records/`: run the whole program and show all debug messages.
Run `inwx-dnsrm sync -h` to see all options.
### Conversion mode
`convert` can convert existing nameserver entries at INWX to the local configuration file format which is explained above. This is neat if you want to "on-board" a domain you already have configured at INWX and don't want to write the configuration files from scratch.
Some examples:
* `inwx-dnsrm convert -d example.com`: get the remote records for the domain "example.com" and output its corresponding local YAML configuration which you can just copy.
* `inwx-dnsrm convert -d example.com > records/example.com.yaml`: like the above, but write the configuration to a file so you don't have to copy it.
* `inwx-dnsrm -i SOA,NS convert -d example.com`: the same as above, but do not fetch SOA and NS records (SOA is the default).
Run `inwx-dnsrm convert -h` to see all options.
## Contribute and Develop
Contributions are welcome! The development is easiest with `poetry`: `poetry install` and `poetry run inwx-dnsrm` will get you started.
## Troubleshooting
### Debug and dry-run
The `--debug` flag will bring you a long way. If you want to create an issue with this project, please provide a debug log, it will be of great help!
When running the `sync` command, this may also help:
* `--dry` is recommended to play around with the program and avoid breaking your productive configuration.
* `--interactive` will ask you before each change for a confirmation.
### I deleted all my productive records!
Oh no, you forgot to make a `sync --dry` run or `convert` the remote records first? While there is no rollback functionality, the tool preserves the local and remote data before making any modification. For each run and domain, you will find an export of the internal data scheme in a cache folder. On Linux systems, this is in `~/.cache/inwx-dns-recordmaster`, the file names will be something like `example.com-1521462189.json` (the number being the current UNIX time). With this, you can reconstruct the remote state before running this tool, either manually in the INWX web interface or you put it in your local DNS records configuration.
### Simulate API response
If you want to work locally or want to modify the INWX API response, you can simulate it. The `--api-response` flag takes a JSON file as argument that basically contains the reponse of the INWX API about the remote state of a domain's nameserver entries. This works in both the `sync` and `convert` commands.
This could look like the following:
```json
{
"roId": 123456,
"domain": "example.com",
"type": "MASTER",
"cleanup": {
"status": "OK",
"tstamp": 1513779810
},
"count": 4,
"record": [
{
"id": 1402323103,
"name": "example.com",
"type": "A",
"content": "185.26.156.148",
"ttl": 3600,
"prio": 0
},
{
"id": 1404343107,
"name": "www.example.com",
"type": "A",
"content": "185.26.156.148",
"ttl": 3600,
"prio": 0
},
{
"id": 209645684,
"name": "example.com",
"type": "NS",
"content": "ns.inwx.de",
"ttl": 86400,
"prio": 0
},
{
"id": 2094329683,
"name": "example.com",
"type": "SOA",
"content": "ns.inwx.de hostmaster.inwx.de 2024030422 10800 3600 604800 3600",
"ttl": 86400,
"prio": 0
}
]
}
```
In order to get this output from an existing domain, you can run the program with the `--debug` flag and search for the line starting with `Response (nameserver.info):`.
### URL Records
INWX has [URL records](https://kb.inwx.com/en-us/3-nameserver/106-how-can-i-forward-a-domain-to-an-internet-address) that allow for redirections of a domain to another domain. These records are somewhat supported by this tool, but there are [several issues and bugs](https://github.com/mxmehl/inwx-dns-recordmaster/pull/23). It's recommended to add and edit these records in the web interface and not via this tool as the INWX API doesn't seem to be reliable, but you can still store these configurations locally.
## License
The main license of this project is the GNU General Public License 3.0, no later version (`GPL-3.0-only`), Copyright Max Mehl.
There may be components under different, but compatible licenses and from different copyright holders. The project is [REUSE](https://reuse.software) compliant which makes these portions transparent. You will find all used licenses in the `LICENSES` directory.
Raw data
{
"_id": null,
"home_page": "https://github.com/mxmehl/inwx-dns-recordmaster",
"name": "inwx-dns-recordmaster",
"maintainer": "",
"docs_url": null,
"requires_python": ">=3.9,<4.0",
"maintainer_email": "",
"keywords": "inwx,dns,nameserver,automation,configuration-management",
"author": "Max Mehl",
"author_email": "mail@mehl.mx",
"download_url": "https://files.pythonhosted.org/packages/05/03/6ab092e76787e8fd75b750823f4bcd64793a6b573e03025758d57da6b774/inwx_dns_recordmaster-0.2.3.tar.gz",
"platform": null,
"description": "<!--\nSPDX-FileCopyrightText: 2024 Max Mehl <https://mehl.mx>\n\nSPDX-License-Identifier: GPL-3.0-only\n-->\n\n# INWX DNS Recordmaster\n\n[](https://github.com/mxmehl/inwx-dns-recordmaster/actions/workflows/test.yaml)\n[](https://api.reuse.software/info/github.com/mxmehl/inwx-dns-recordmaster)\n[](https://pypi.org/project/inwx-dns-recordmaster/)\n[](https://pypi.org/project/inwx-dns-recordmaster/)\n\nManage DNS nameserver records of INWX domains via YAML files and API requests. Lightweight, fast, version-control ready.\n\nNote: This is no official software project by INWX, it just kindly uses their public API.\n\n- [Overview](#overview)\n- [Install](#install)\n- [Configuration](#configuration)\n - [App/API configuration](#appapi-configuration)\n - [DNS records configuration](#dns-records-configuration)\n- [Run the program](#run-the-program)\n - [Synchronisation mode](#synchronisation-mode)\n - [Conversion mode](#conversion-mode)\n- [Contribute and Develop](#contribute-and-develop)\n- [Troubleshooting](#troubleshooting)\n - [Debug and dry-run](#debug-and-dry-run)\n - [I deleted all my productive records!](#i-deleted-all-my-productive-records)\n - [Simulate API response](#simulate-api-response)\n - [URL records](#url-records)\n- [License](#license)\n\n\n## Overview\n\nThis tool enables customers of [INWX](https://www.inwx.de) (formerly known as InterNetworX) to manage the DNS entries/records of their domains via files. This has multiple advantages:\n\n* Version-control of nameserver entries, therefore a good record of what has changed over time.\n* Very simple copy/paste of existing entries for new domains, e.g. when a new alias domain has been added.\n* Enables search/replace, e.g. of IP addresses.\n* Work can be done offline and quicker, and pushed once it's done. No waiting times for the sometimes slow web interface.\n\nConfiguration of the DNS records is done in YAML files with a quite simple structure. It is compared against the \"remote\" state, pulled via the INWX API. If necessary, minimal API requests will be issues to align the remote state with the local configuration.\n\n\n## Install\n\nThe tool depends on the following applications:\n\n* Python 3\n\nYou can install the latest release via `pip3 install inwx-dns-recordmaster`\n\nThe tool is executable with `inwx-dnsrm`. The `--help` flag informs you about the required and available commands.\n\n\n## Configuration\n\nThere are two types of configuration:\n\n1. App configuration: INWX API login data\n1. DNS records configuration: the desired state for each configured domain\n\n\n### App/API configuration\n\nYou need to add your credentials for the API authentication. The file will be created automatically on first run if it doesn't exist. On Linux systems, it will be located in `~/.config/inwx-dns-recordmaster/config.toml`.\n\nIn any case, you will need to add your INWX username and password, be it of the main or a sub-account. If you use two-factor-authentication you may add the shared secret as well, although this may weaken your security. You may also want to ask the INWX support to limit the login to specific IP addresses.\n\n\n### DNS records configuration\n\nDNS records are configured in YAML files. If you have multiple domains, you can either put all definitions in one big file, or create multiple ones. The `--dns-config` flag of the program just needs to point to a directory in which at least one such file is present. Only files ending with `.yaml` or `.yml` are considered.\n\nYou can find an example DNS records configuration in the file [`records/example.com.yaml.sample`](records/example.com.yaml.sample). Here is a much shorter example:\n\n```yaml\nexample.com:\n # Records configuring example.com\n .:\n - type: A\n content: \"192.168.13.37\"\n - type: MX\n content: \"my.mailhost.tld\"\n prio: 10 # priority of MX record, relevant with multiple MX\n # *.example.com\n \"*\":\n - type: A\n content: \"192.168.13.37\"\n # cloud.example.com\n cloud:\n - type: CNAME\n content: cloudprovider.tld\n ttl: 86400 # long TTL\n```\n\nPlease note that the general idea of this program is that ALL records are managed locally. In the above example, it would delete the `NS` records of the domain which is a bad idea.\n\nHowever, there are default and extendable exceptions:\n\n* By default, records of the type `SOA` are not considered as they change upon each change and are handled well by INWX. You can add additional record types with the `--ignore-types` argument if you don't want to handle them.\n* You can also blatantly ignore records that exist at INWX but not in your local configuration, using the `--preserve-remote` flag. This way, you only *update existing* and *add new* records, but don't *delete unconfigured* records at INWX.\n\nIf you already have a domain configured at INWX whose records you want to migrate to your local DNS records configuration, there is the convert command: `inwx-dnsrm convert --domain example.com`. This enables you to take the DNS config at INWX for a specific domain, put it in your local configuration, and start from this point onwards. You don't have to manually write long configuration files from scratch, unless you want to.\n\n\n## Run the program\n\nYou can execute the program using the command `inwx-dnsrm`. `inwx-dnsrm --help` shows all available arguments and options.\n\nThe program has two main commands: `sync` and `convert`.\n\n\n### Synchronisation mode\n\n`sync` covers the main functionality, managing INWX domain records based on local configuration files whose format is explained above.\n\nSome examples:\n\n* `inwx-dnsrm sync -c records/`: read the DNS records from the `records/` directory, match them with the remote, and call the API to add, update, and delete entries for each locally configured domain.\n* `inwx-dnsrm sync -c records/ -d example.com`: like the above, but only check the domain `example.com` and ignore all other locally configured. If you have many domains, this may speed up operations.\n* `inwx-dnsrm sync -c records/ -p`: run normally, but do not delete nameserver entries at INWX which are not configured locally.\n* `inwx-dnsrm sync -c records/ --dry`: run the whole program but do not make any changes at INWX. Very helpful if you just configure a new domain.\n* `inwx-dnsrm sync --debug -c records/`: run the whole program and show all debug messages.\n\nRun `inwx-dnsrm sync -h` to see all options.\n\n### Conversion mode\n\n`convert` can convert existing nameserver entries at INWX to the local configuration file format which is explained above. This is neat if you want to \"on-board\" a domain you already have configured at INWX and don't want to write the configuration files from scratch.\n\nSome examples:\n\n* `inwx-dnsrm convert -d example.com`: get the remote records for the domain \"example.com\" and output its corresponding local YAML configuration which you can just copy.\n* `inwx-dnsrm convert -d example.com > records/example.com.yaml`: like the above, but write the configuration to a file so you don't have to copy it.\n* `inwx-dnsrm -i SOA,NS convert -d example.com`: the same as above, but do not fetch SOA and NS records (SOA is the default).\n\nRun `inwx-dnsrm convert -h` to see all options.\n\n## Contribute and Develop\n\nContributions are welcome! The development is easiest with `poetry`: `poetry install` and `poetry run inwx-dnsrm` will get you started.\n\n\n## Troubleshooting\n\n\n### Debug and dry-run\n\nThe `--debug` flag will bring you a long way. If you want to create an issue with this project, please provide a debug log, it will be of great help!\n\nWhen running the `sync` command, this may also help:\n* `--dry` is recommended to play around with the program and avoid breaking your productive configuration.\n* `--interactive` will ask you before each change for a confirmation.\n\n\n### I deleted all my productive records!\n\nOh no, you forgot to make a `sync --dry` run or `convert` the remote records first? While there is no rollback functionality, the tool preserves the local and remote data before making any modification. For each run and domain, you will find an export of the internal data scheme in a cache folder. On Linux systems, this is in `~/.cache/inwx-dns-recordmaster`, the file names will be something like `example.com-1521462189.json` (the number being the current UNIX time). With this, you can reconstruct the remote state before running this tool, either manually in the INWX web interface or you put it in your local DNS records configuration.\n\n\n### Simulate API response\n\nIf you want to work locally or want to modify the INWX API response, you can simulate it. The `--api-response` flag takes a JSON file as argument that basically contains the reponse of the INWX API about the remote state of a domain's nameserver entries. This works in both the `sync` and `convert` commands.\n\nThis could look like the following:\n\n```json\n{\n \"roId\": 123456,\n \"domain\": \"example.com\",\n \"type\": \"MASTER\",\n \"cleanup\": {\n \"status\": \"OK\",\n \"tstamp\": 1513779810\n },\n \"count\": 4,\n \"record\": [\n {\n \"id\": 1402323103,\n \"name\": \"example.com\",\n \"type\": \"A\",\n \"content\": \"185.26.156.148\",\n \"ttl\": 3600,\n \"prio\": 0\n },\n {\n \"id\": 1404343107,\n \"name\": \"www.example.com\",\n \"type\": \"A\",\n \"content\": \"185.26.156.148\",\n \"ttl\": 3600,\n \"prio\": 0\n },\n {\n \"id\": 209645684,\n \"name\": \"example.com\",\n \"type\": \"NS\",\n \"content\": \"ns.inwx.de\",\n \"ttl\": 86400,\n \"prio\": 0\n },\n {\n \"id\": 2094329683,\n \"name\": \"example.com\",\n \"type\": \"SOA\",\n \"content\": \"ns.inwx.de hostmaster.inwx.de 2024030422 10800 3600 604800 3600\",\n \"ttl\": 86400,\n \"prio\": 0\n }\n ]\n}\n```\n\nIn order to get this output from an existing domain, you can run the program with the `--debug` flag and search for the line starting with `Response (nameserver.info):`.\n\n\n### URL Records\n\nINWX has [URL records](https://kb.inwx.com/en-us/3-nameserver/106-how-can-i-forward-a-domain-to-an-internet-address) that allow for redirections of a domain to another domain. These records are somewhat supported by this tool, but there are [several issues and bugs](https://github.com/mxmehl/inwx-dns-recordmaster/pull/23). It's recommended to add and edit these records in the web interface and not via this tool as the INWX API doesn't seem to be reliable, but you can still store these configurations locally.\n\n\n## License\n\nThe main license of this project is the GNU General Public License 3.0, no later version (`GPL-3.0-only`), Copyright Max Mehl.\n\nThere may be components under different, but compatible licenses and from different copyright holders. The project is [REUSE](https://reuse.software) compliant which makes these portions transparent. You will find all used licenses in the `LICENSES` directory.\n",
"bugtrack_url": null,
"license": "GPL-3.0-only",
"summary": "Manage DNS nameserver records of INWX domains via YAML files and API requests. Lightweight, version-control ready",
"version": "0.2.3",
"project_urls": {
"Homepage": "https://github.com/mxmehl/inwx-dns-recordmaster",
"Repository": "https://github.com/mxmehl/inwx-dns-recordmaster"
},
"split_keywords": [
"inwx",
"dns",
"nameserver",
"automation",
"configuration-management"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "9e5126dfd2e748b86ef9df19d784db370a398b2d0aa17d17755f2094d7b1f94d",
"md5": "ae3a499a4cc1c5cea754cbb13b4b107d",
"sha256": "b3d9450d1aed72861fb6c8574e6388e80133557aeeefd4b77ad0175b15014324"
},
"downloads": -1,
"filename": "inwx_dns_recordmaster-0.2.3-py3-none-any.whl",
"has_sig": false,
"md5_digest": "ae3a499a4cc1c5cea754cbb13b4b107d",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.9,<4.0",
"size": 56847,
"upload_time": "2024-03-19T09:02:02",
"upload_time_iso_8601": "2024-03-19T09:02:02.725404Z",
"url": "https://files.pythonhosted.org/packages/9e/51/26dfd2e748b86ef9df19d784db370a398b2d0aa17d17755f2094d7b1f94d/inwx_dns_recordmaster-0.2.3-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "05036ab092e76787e8fd75b750823f4bcd64793a6b573e03025758d57da6b774",
"md5": "6a906ca7840d8a3a2c2b84d723a8e720",
"sha256": "25464911f3aacd27f4363d14fabf52924acff621e3a8b953f75034c1af8d2218"
},
"downloads": -1,
"filename": "inwx_dns_recordmaster-0.2.3.tar.gz",
"has_sig": false,
"md5_digest": "6a906ca7840d8a3a2c2b84d723a8e720",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.9,<4.0",
"size": 52702,
"upload_time": "2024-03-19T09:02:04",
"upload_time_iso_8601": "2024-03-19T09:02:04.717917Z",
"url": "https://files.pythonhosted.org/packages/05/03/6ab092e76787e8fd75b750823f4bcd64793a6b573e03025758d57da6b774/inwx_dns_recordmaster-0.2.3.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2024-03-19 09:02:04",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "mxmehl",
"github_project": "inwx-dns-recordmaster",
"travis_ci": false,
"coveralls": false,
"github_actions": true,
"lcname": "inwx-dns-recordmaster"
}
JSON
