Skip to main content

Update DNS settings using the Schlundtech XML-Gateway

Project description

This packages provides a way to update DNS records programmatically, for customers of Schlundtech, using their XML-Gateway.

Many thanks to for doing the heavy lifting of figuring out how to talk to the XML-Gateway in a way that actually makes it do what we want.


First, you need to create a subdomain with an A-record in your domain, say, and install this package, e.g. with pip install ws.ddns (or git clone ...; pip install -e .)

Then you can use the command-line utility provided by this package, like so:

$ schlund-ddns --username USER --password PASS

If you have both an A and AAAA record for the subdomain, you have to update them separately, i.e. call the script twice, once with an IPv4 and a second time with IPv6 address.

(See schlund-ddns --help for more configuration parameters, e.g. the context that you were told to use when applying for the XML-Gateway.)

Instead of passing the parameters on the commandline, you can instead call schlund-ddns --config myconfig.ini (see below for the file format).

Alternatively, set up the provided cgi script schlund-ddns-cgi to provide HTTP access. You’ll need to provide username and password using a configuration file and then passing that file’s path as an environment variable. Here’s an example apache configuration snippet to do this:

ScriptAlias /dns-update /path/to/ddns/schlund-ddns-cgi
<Location /dns-update>
  SetEnv DDNS_CONFIG /path/to/ddns/config

  AuthName "Dynamic DNS"
  AuthType Basic
  AuthUserFile /path/to/ddns/htpasswd
  require valid-user

The configuration file is a standard ini file and should look like this:

username = USER
password = PASS
context  = CONTEXT

You can optionally add an allowed_hostnames = whitespace-separated list to the config file, only those will then be accepted.

The HTTP protocol is modeled after the one from NoIP, that is, clients should perform a request like this to trigger a DNS update:

There is also a docker image of the HTTP service here:

2FA support

  • Install pip install pyotp in addition to this package

  • Pass the 2FA secret (probably 16 characters, you may have to reverse-engineer them from the QR-Code used for setup) as –totp-secret` commandline or configuration parameter


1.6.0 (2024-02-05)


  • Support TOTP in CGI mode as well (totp)

1.5.0 (2023-09-18)


  • Support subdomains with both A and AAAA records (ipv6)

1.4.0 (2023-05-12)


  • Fix config parsing after introducing totp secret parameter (totp)

1.3.1 (2023-04-04)


  • Switch from to pyproject.toml (wheel)

1.3.0 (2023-03-20)

  • Support a configuration file for the command line script

  • Determine the domain name correctly for multi-level subdomains

  • Support 2FA TOTP authentication

  • Drop Python-2 support

1.2.0 (2020-10-04)

  • Model our response text after the protocol

1.1.1 (2018-03-05)

  • Handle PATH_INFO internally

1.1.0 (2018-03-03)

  • Add optional allowed_hostnames config option

1.0.4 (2018-03-03)

  • Make web part Python-3 compatible

1.0.3 (2018-03-03)

  • Make current-setuptools compatible

1.0.2 (2018-03-03)

  • Make Python-3 compatible

1.0.1 (2018-01-14)

  • Move from bitbucket to github

1.0.0 (2014-04-06)

  • First release.

Project details

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

ws.ddns-1.6.0.tar.gz (5.7 kB view hashes)

Uploaded Source

Built Distribution

ws.ddns-1.6.0-py3-none-any.whl (5.7 kB view hashes)

Uploaded Python 3

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page