Merge branch 'master' into tinydns-additions

.gitignore

@@ -2,6 +2,7 @@
 .coverage
 .env
 /config/
+/build/
 coverage.xml
 dist/
 env/

CHANGELOG.md

@@ -9,6 +9,7 @@
 * CloudflareProvider SRV record unpacking fix
 * DNSMadeEasy provider uses supports to avoid blowing up on unknown record
   types
+* Normalize MX/CNAME/ALIAS/PTR value to lower case
 
 ## v0.9.4 - 2019-01-28 - The one with a bunch of stuff, before the big one
 

README.md

@@ -9,6 +9,26 @@ The architecture is pluggable and the tooling is flexible to make it applicable
 
 It is similar to [Netflix/denominator](https://github.com/Netflix/denominator).
 
+## Table of Contents
+
+- [Getting started](#getting-started)
+  - [Workspace](#workspace)
+  - [Config](#config)
+  - [Noop](#noop)
+  - [Making changes](#making-changes)
+  - [Workflow](#workflow)
+  - [Bootstrapping config files](#bootstrapping-config-files)
+- [Supported providers](#supported-providers)
+    - [Notes](#notes)
+- [Custom Sources and Providers](#custom-sources-and-providers)
+- [Other Uses](#other-uses)
+  - [Syncing between providers](#syncing-between-providers)
+  - [Dynamic sources](#dynamic-sources)
+- [Contributing](#contributing)
+- [Getting help](#getting-help)
+- [License](#license)
+- [Authors](#authors)
+
 ## Getting started
 
 ### Workspace

docs/records.md

@@ -174,6 +174,6 @@ In the above example each name had a single record, but there are cases where a
 
 ### Record data
 
-Each record type has a corresponding set of required data. The easiest way to determine what's required is probably to look at the record object in [`octodns/record.py`](/octodns/record.py). You may also utilize `octodns-validate` which will throw errors about what's missing when run.
+Each record type has a corresponding set of required data. The easiest way to determine what's required is probably to look at the record object in [`octodns/record/__init__.py`](/octodns/record/__init__.py). You may also utilize `octodns-validate` which will throw errors about what's missing when run.
 
 `type` is required for all records. `ttl` is optional. When TTL is not specified the `YamlProvider`'s default will be used. In any situation where an array of `values` can be used you can opt to go with `value` as a single item if there's only one.