My favorites | Sign in
Project Home Downloads Wiki Issues Source
Search
for

These are all auto-generated from the same source as the real manpages - do not edit these here, edit the corresponding POD source in the main git repo

Manpages

gdnsd(8) - The daemon itself

gdnsd.config(5) - Config file reference

gdnsd.zonefile(5) - Zone file reference

gdnsd-plugin-simplefo(8) - Plugin for simple pri->sec address failover

gdnsd-plugin-multifo(8) - Plugin for all-active multi-address failover groups

gdnsd-plugin-weighted(8) - Plugin for several variations on the theme of weighted-round-robin addresses and cnames

gdnsd-plugin-metafo(8) - Meta-plugin for failover between resources defined by other plugins

gdnsd-plugin-geoip(8) - Meta-plugin for geographic load distribution and failover

gdnsd_geoip_test(1) - A commandline tool to help validate/debug geographic map configurations used by gdnsd-plugin-geoip(8)

Design Doc / Manual ?

GdnsdManual - This is a design doc that's missing a lot, and/or a manual that's not very helpful :). In either case, it does close up a few gaps in the above manpages.

Planning  
Updated Feb 3, 2012 by blbl...@gmail.com

Branching and Versioning

gdnsd uses a 3-number versioning system. The first two numbers denote a release series, and the last number denotes a specific release within that series. If the second number is even, the series is a stable release series and gets bugfixes only. If the second number is odd, this is an unstable development series. This is very similar to the scheme Linux followed for a long time.

The repository has recently been converted to git.

The "master" branch is the source of stable series releases, and should only receive bugfix commits directly.

The "dev" branch is the primary target for the current unstable development series.

Please read http://gdnsd.googlecode.com/git/GIT-POLICY for more details.


Sign in to add a comment
Powered by Google Project Hosting