Content
0.1.0
Just use two core-dns resolves in parallel instead of native-dns

It's not worth trying to make native-dns work right now just for
TTLs, especially considering there's a whole bunch of intermediate
API we'd essentially have to copy-paste to get around the way it
handles caching and simplified return values.

native-dns has a bunch of issues related to stuff like truncation
that haven't been addressed in the past 8 months (in spite of
a big red "failing" badge for its Travis tests). For all intents
and purposes, considering the marginal benefits (and headaches)
involved in trying to integrate record TTLs here, we'll just
set doing TTLs correctly aside for now and let the end use case
come up with its own workaround (like setting it to a static
value).

Another non-advantage of native-dns: we can't just do an 'ALL'
request since * requests will return stuff like CNAMEs that
require the whole resolution runaround, at which point we're making
multiple requests anyway.

At some point in the future I *might* revisit this, write my own
forked resolver that does ALL queries and follows CNAMEs and
discovers multiple records types and notes TTLs... but I doubt it.
0.2.0