powerdns-to-gdnsd

PowerDNS to gdnsd domain/zone Migrator

Maintained and provided by https://eXtremeSHOK.com

Description

The powerdns-to-gdnsd script provides a simple way to export all your domains/zones from PowerDNS into gdnsd. The script will test and generate correct gdnsd zonefiles. The zonefiles can be used directly with gdnsd without needing any changes. There are various tests to ensure the generated zonefiles are valid and minor issues will be fixes automatically. The script will attempt to load the powerdns configs to automatically configure itself to be able to fetch the domain/zone records from the database. Due to gdnsd not supporting dnssec as well as some obselete and non-standard record types, they we will be automatically disabled. The script will also disable any invalid records.

FYI

The following was developed to migrate a 5node powerdns mysql cluster with over 2000 domains to gdnsd. The script can also be run via cron, this could allow you to still use your the current powerdns database and webinterfaces to generate working gdnsd records, without actually using powerdns. Please see the "sample" directory or the travis-ci build logs to see 2 examples of generated records.

Assumptions

PowerDNS server (pdns-server) using backend MySQL (dns-backend-mysql / gmysqlbackend) with the standard scheme (table names and columns) : https://raw.githubusercontent.com/PowerDNS/pdns/master/modules/gmysqlbackend/schema.mysql.sql If the need arises we can add support for other backends/database systems (pgsql, sqlite, etc)

Try our other custom scripts: https://github.com/extremeshok

Support / Suggestions / Comments

Please post them on the issue tracker : https://github.com/extremeshok/powerdns-to-gdnsd/issues

Submit Patches / Pull requests to the "master" Branch

Quick Install Guide

• Download the script
• Set 755 permissions on the script
• Run the the script

First Usage

• Run the script as your superuser, MySQL settings are automatically detected from the powerdns configs

Config Files and Detected Settings

• Default configs are loaded in the following order if they exist:
• /etc/powerdns/pdns.conf -> /etc/powerdns/pdns.d/pdns.local.conf -> /etc/powerdns/pdns.d/pdns.local.gmysql.conf -> /etc/pdns/pdns.conf -> /etc/pdns/conf.d/gmysql.conf
• A minimum of 1 config is required which contains the database parameters.
• Specifying a config on the command line (-c | --config) will override the loading of the default configs

Testing generated zonefiles

• Run the following command to display any errors with the generated zonefiles
• assumes gdnsd is installed and the generated zonefiles have been copied to /etc/gdnsd/zones

gdnsd -fDSs -c /etc/gdnsd checkconf

Change Log

Version 2.1.0 ( 29 April 2016 )

• eXtremeSHOK.com Maintenance
• Added function xshok_is_in_array to check if a string is in an array
• Added option to disable dnssec records
• Added option to disable not implemented records
• Added support for wildcard record domains (*.example.com and www.*.example.com)
• Proper support for "" in records
• Fixed: invalid srv records
• Replaced cat << EOF with echo

Version 2.0.0

• eXtremeSHOK.com Maintenance
• Refactored for Public Releas
• Added travis-ci.org code testing

Version 1.x.x

• eXtremeSHOK.com Internal

USAGE

 Usage: powerdns-to-gdnsd.sh     [OPTION] [PATH|FILE]


 -h, --help      Display this script's help and usage information


 -V, --version   Output script version and date information


 -v, --verbose   Be verbose, enabled when not run under cron


 -s, --silence   Only output error messages, enabled when run under cron


 -o, --output    Output the zonefiles to a specific directory eg: '-o /your/directory'


 -c, --config    Use a specific configuration file
         eg: '-c /your/file.name'