Welcome to Python DNS Failover’s documentation!¶
Contents:
Python DNS Failover¶
Python script to automatically update DNS records for a bunch of servers participating in a Round-Robin DNS setup.
- Free software: BSD license
- Documentation: http://python-dns-failover.rtfd.org.
This project is mainly based on @dotcloud‘s work on his project autodnsfailover.
The main difference is that python-dns-failover script is aimed to run in an external machine while autodnsfailover is to run in the participating servers themselves.
DNS Backends¶
A DNS backend is responsible for updating the DNS records. It must provide the following methods:
- get_a_records(fqdn): Returns the list of ip adresses records associated with the given FQDN.
- add_a_record(fqdn, ip): Adds a resource record of type A to the DNS list. Optionally return the new record created.
- delete_a_record(fqdn, ip): Deletes all DNS A-type resource records targeting the given ip. Optionally return the number of deleted records.
The constructor will typically be implementation-dependent, and allow to set the credentials and/or the zone to act upon.
Available DNS Backends¶
- CloudFlareDNS
- email: E-mail address of your CloudFlare account.
- key: API key of your CloudFlare account.
- zone: target DNS full qualified domain name.
- ttl: TTL of record in seconds. 1 = Automatic, otherwise, value must in between 120 and 4,294,967,295 seconds. Defaults to 1.
- url: CloudFlare client gateway interface url. Defaults to ‘https://www.cloudflare.com/api_json.html‘.
TODO¶
- Documentation
- Testing
Installation¶
At the command line:
$ easy_install python-dns-failover
Or, if you have virtualenvwrapper installed:
$ mkvirtualenv python-dns-failover
$ pip install python-dns-failover
Contributing¶
Contributions are welcome, and they are greatly appreciated! Every little bit helps, and credit will always be given.
You can contribute in many ways:
Types of Contributions¶
Report Bugs¶
Report bugs at https://github.com/marccerrato/python-dns-failover/issues.
If you are reporting a bug, please include:
- Your operating system name and version.
- Any details about your local setup that might be helpful in troubleshooting.
- Detailed steps to reproduce the bug.
Fix Bugs¶
Look through the GitHub issues for bugs. Anything tagged with “bug” is open to whoever wants to implement it.
Implement Features¶
Look through the GitHub issues for features. Anything tagged with “feature” is open to whoever wants to implement it.
Write Documentation¶
Python DNS Failover could always use more documentation, whether as part of the official Python DNS Failover docs, in docstrings, or even on the web in blog posts, articles, and such.
Submit Feedback¶
The best way to send feedback is to file an issue at https://github.com/marccerrato/python-dns-failover/issues.
If you are proposing a feature:
- Explain in detail how it would work.
- Keep the scope as narrow as possible, to make it easier to implement.
- Remember that this is a volunteer-driven project, and that contributions are welcome :)
Get Started!¶
Ready to contribute? Here’s how to set up python-dns-failover for local development.
Fork the python-dns-failover repo on GitHub.
Clone your fork locally:
$ git clone git@github.com:your_name_here/python-dns-failover.git
Install your local copy into a virtualenv. Assuming you have virtualenvwrapper installed, this is how you set up your fork for local development:
$ mkvirtualenv python-dns-failover $ cd python-dns-failover/ $ python setup.py develop
Create a branch for local development:
$ git checkout -b name-of-your-bugfix-or-feature
Now you can make your changes locally.
When you’re done making changes, check that your changes pass flake8 and the tests, including testing other Python versions with tox:
$ flake8 dns_failover tests $ python setup.py test $ tox
To get flake8 and tox, just pip install them into your virtualenv.
Commit your changes and push your branch to GitHub:
$ git add . $ git commit -m "Your detailed description of your changes." $ git push origin name-of-your-bugfix-or-feature
Submit a pull request through the GitHub website.
Pull Request Guidelines¶
Before you submit a pull request, check that it meets these guidelines:
- The pull request should include tests.
- If the pull request adds functionality, the docs should be updated. Put your new functionality into a function with a docstring, and add the feature to the list in README.rst.
- The pull request should work for Python 2.6, 2.7, and 3.3, and for PyPy. Check https://travis-ci.org/marccerrato/python-dns-failover/pull_requests and make sure that the tests pass for all supported Python versions.
Credits¶
Development Lead¶
- Marc Cerrato <marccerrato@gmail.com>
Contributors¶
None yet. Why not be the first?