Dnsmule

**Summary**
This version should already be fairly stable. The major points of improvement are still the YANL loading and some implementation details of the rule factories and rules entities.

The dynamic rule loading is not that well defined at the moment as the addition callback mechanism is only used and given to the rules when loading them through the YAML. For this the proposed solution is to remove the dynamic addition and instead provide a reference to the mule instance inside the dynamic rules. This way the loading can be made more straightforward. The init logic in the dynamic rules will be kept, but it might be moved to run in a secondary thread.

**In this release:**
- Some more IP range providers
- Example code
- Fairly stable configuration format

**To be expected in the future:**
- Removal of storage fallback parameter
- Unifying rule addition and creation under one method
- Making a lot more methods private
- Changes to the dynamic rule dynamic addition of rules

This release contains an _Alpha_ version of DNSMule.

You can run the example server easily via:
shell
$ ./build-image
$ ./run-server


Currently the YAML loading for DNSMule supports the following features:

- Rules
- Plugins
- Backend

See the example rules for usage.

To get started in code:
python
from dnsmule import DNSMule

mule = DNSMule.load(
'rules.yml' Change
)

Rules require changes to the declaration. The declaration is changed to be more verbose and requires changing the old definition to the new format. The major changes are a mandatory name line instead of the implicit old one and appending any configuration values to the `config` section. Any `name` parameter in config will get overridden by the rule name.

Old:
yaml
rules:
- test:
type: my.rule
record: A
key: 'value'


New:
yaml
rules:
- name: test
type: my.rule
record: A
config:
key: 'value'