django-powerdns-dnssec 0.9.0

Quickstart

Simply add powerdns to INSTALLED_APPS in your settings.py. Use South for database migrations.

Using a separate database for PowerDNS

If your Django application is using a different database than the one used by PowerDNS, provide the configuration for the DNS database in settings.py as a separate entry in DATABASES, for example:

DATABASES = {
    'default': {
        'ENGINE': 'django.db.backends.mysql',
        'NAME': 'project_db',
        'USER': 'user',
        'PASSWORD': 'secret',
        'HOST': '127.0.0.1',
        'PORT': '3306',
        'OPTIONS': {
            "init_command": "SET storage_engine=INNODB",
        },
    },
    'powerdns': {
        'ENGINE': 'django.db.backends.mysql',
        'NAME': 'powerdns',
        'USER': 'pdns',
        'PASSWORD': 'pdns',
        'HOST': '127.0.0.1',
        'PORT': '3306',
        'OPTIONS': {
            "init_command": "SET storage_engine=INNODB",
        },
    },
}

For Django to automatically route powerdns requests to the right database, add this setting to settings.py:

DATABASE_ROUTERS = ['powerdns.routers.PowerDNSRouter']

You have to sync and migrate the default and the powerdns databases separately. First the default database:

$ python manage.py syncdb
$ python manage.py migrate

Then the powerdns database:

$ python manage.py syncdb --database=powerdns
$ python manage.py migrate --database==powerdns

Note that the powerdns database will maintain its own separate South migration history table. This is especially helpful if your connecting several Django projects to a single PowerDNS database.

Change Log

Authors

Application written by Peter Nixon and Łukasz Langa. NSEC3 code based on George Notaras’ work with django-powerdns-manager.