/django-powerdns-manager

django-powerdns-manager is a web based PowerDNS administration panel. This repository is mirrored from https://bitbucket.org/gnotaras/django-powerdns-manager

Primary LanguagePythonApache License 2.0Apache-2.0

django-powerdns-manager

Author: George Notaras
Development Web Site: django-powerdns-manager project
Source Code Repository: django-powerdns-manager source code
Documentation: django-powerdns-manager documentation
Downloads: django-powerdns-manager releases

django-powerdns-manager is a web based PowerDNS administration panel.

Licensed under the Apache License version 2.0. More licensing information exists in the license section.

Note

The following table includes some unofficial information about the compatibility of django-powerdns-manager with Django and PowerDNS releases. This information comes without any warranty of correctness. It indicates that the release has been unofficially tested to work with the listed releases of Django and PowerDNS. Please, test the releases in your environment in order to ensure that all pieces work together as expected.

django-powerdns-manager Django PowerDNS
0.2.9a1 1.9.4 3.4.8
0.2.2a1 1.8.5 3.4.6
0.2.1a1 1.7.3 3.4.1

Note

django-powerdns-manager, since version 0.2.0a1, supports database migrations using the internal migrations mechanism of Django 1.7.3. It is recommended to use the following commands instead of manually altering the database tables:

manage.py migrate
manage.py migrate --database=powerdns

django-powerdns-manager should be considered work in progress. If you use it in production, please make sure you test new releases before upgrading your production systems.

This software comes without any warranty of any kind. You are on your own.

Note

This note demonstrates how to use the Django API to manage Domains (Zones) and Resource Records in bulk from the command line. Launch a Python shell from your Django project's root directory with the following:

python manage.py shell

The following snippet assumes that the SPF policy is stored in TXT records. It then resets the SPF policy to "v=spf1 mx -all" on all domains (zones):

# Import our models
from powerdns_manager.models import Record, Domain
# Fetch all TXT RRs that contain SPF policy.
rrset = Record.objects.filter(type='TXT', content__contains='v=spf1')
# Iterate over all RRs and reset the SPF policy.
for rr in rrset:
    # Set the new SPF policy in the record's content.
    # Notice the double quotes.
    rr.content = '"v=spf1 mx -all"'
    # Save the Resource Record.
    rr.save()
    # Update the zone's serial. We can access the domain (zone) as an
    # attribute of the current resource record.
    rr.domain.update_serial()

Using the flexibility of the Python code and the Django API many complex modifications can be done on the command line.

Always make sure to test your code in a development environment.

Features

  • Web based administration interface based on the admin Django app.
  • Easy management of all records of a zone from a single web page.
  • Support for multiple users.
  • Database schema is DNSSEC enabled.
  • Automatic zone-rectify support, including support for empty non-terminals, using native python code.
  • The application can be configured to support a user-defined subset of the resource records supported by PowerDNS and customize the order in which they appear in the administration panel.
  • Zone cloning (experimental).
  • Zone transfers between users.
  • Zone file import through web form.
  • Zone file export.
  • Basic zone templates.
  • Command-line interfaces to import and export zones in bulk.
  • Support for secure updating of dynamic IP addresses in A and AAAA records.
  • Supports using a dedicated database to store the tables needed by PowerDNS. This database may use a different backend than the main database of the Django project.
  • Contains demo project for quick start and experimentation.

Quickstart Guide

The distribution package of django-powerdns-manager contains an example project that can help you check out the features of the software and also quickly experiment with the source code.

Although, the example project has already been configured for you, there are still some required steps before you are able to run it using the development server. These steps are discussed in detail in the Quickstart Guide.

Development

The source code of this project is available at the following official repositories.

Main repository (mercurial):

https://bitbucket.org/gnotaras/django-powerdns-manager

Mirror repository (git):

https://github.com/gnotaras/django-powerdns-manager

Pull requests are welcome. Please note that it may take a long time before pull requests are reviewed.

Donations

This software is released as free-software and provided to you at no cost. However, a significant amount of time and effort has gone into developing this software and writing this documentation. So, the production of this software has not been free from cost. It is highly recommended that, if you use this software in production, you should consider making a donation.

Documentation

Apart from the django-powerdns-manager Online Documentation, more information about the installation, configuration and usage of this application may be available at the project's wiki.

Bugs and feature requests

In case you run into any problems while using this application or think that a new feature should be implemented, it is highly recommended you submit a new report about it at the project's issue tracker.

Using the issue tracker is the recommended way to notify the authors about bugs or make feature requests. Also, before submitting a new report, please make sure you have read the new issue guidelines.

Support

CodeTRAX does not provide support for django-powerdns-manager.

You can still get community support at the Community Support Forums:

License

Copyright 2012-2016 George Notaras <gnot@g-loaded.eu>

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License.

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

A copy of the License exists in the product distribution; the LICENSE file. For copyright and other important notes regarding this release please read the NOTICE file.