Package: django-powerdns-dnssec
Welcome to the PowerDNS app for Django.This application allows easy administration of PowerDNS records stored in an
SQL database by leveraging the standard Django Admin app. You may also use the
Django PowerDNS application as part of a larger project to programatically
modify your DNS records.Note:This is an updated and enhanced fork ofdjango-powerdnswhich looks abandoned as of
November 2012.QuickstartSimply addpowerdnsandlck.django.commontoINSTALLED_APPSin yoursettings.py.  Use South for database migrations.Customizing resource record typesIf you’re not using DNSSEC or the other less common record types, you can
simplify the user interface even more by specifying a sequence of types the app
should use. Simply put this in yoursettings.py:POWERDNS_RECORD_TYPES = (
    'A', 'AAAA', 'CNAME', 'HINFO', 'MX', 'NAPTR', 'NS',
    'PTR', 'SOA', 'SRV', 'TXT',
)Consult PowerDNS documentation for alist of supported resource record types.Using a separate database for PowerDNSIf your Django application is using a different database than the one used by
PowerDNS, provide the configuration for the DNS database insettings.pyas
a separate entry inDATABASES, 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 routepowerdnsrequests to the right database,
add this setting tosettings.py:DATABASE_ROUTERS = ['powerdns.routers.PowerDNSRouter']You have to sync and migrate thedefaultand thepowerdnsdatabases
separately. First the default database:$ python manage.py syncdb
$ python manage.py migrateThen thepowerdnsdatabase:$ python manage.py syncdb --database=powerdns
$ python manage.py migrate --database==powerdns powerdnsNote that thepowerdnsdatabase will maintain its own separate South
migration history table. This is especially helpful if your connecting several
Django projects to a single PowerDNS database.Also note that due toSouth limitations,migratewill create all powerdns
tables also in the default database. This is harmless, even though creates some
clutter.Change Log0.9.3Fixed issue #3: HTTP 500 in record admin form if no type given0.9.2Fixed issue #2: numeric sorting of IP addresses in admin0.9.1Domain foreign keys support auto completion and have “Edit separately” linksField choices use radio selects whenever that makes sense (fever clicks
necessary)Forward/reverse domain filter (requires Django 1.4+)The0002database migration in 0.9.0 was incomplete, this is now fixed0.9.0DNSSEC tables supported.Support for multiple databases.Updated the project to require at least Django 1.3.UI translations supported (currently Polish translation added).South migrations.Source code compliant with PEP8.Minor fixes.0.2.0First release with basic PowerDNS support.AuthorsApplication written byPeter NixonandŁukasz Langa. NSEC3 code based on George Notaras’
work withdjango-powerdns-manager.