Enhanced record validation

Refactor validation logic to be a method on each record type and to accept a flags parameter to indicate how thoroughly to validate things beyond what’s currently there.

Things like:

• Ensure values are unique
• cname targets, mx, srv, etc. hostnames are resolvable
• maybe ip addresses are routable, pingable, http/https able… though not clear how it’d know what to try
• CNAME can’t coexist

[yzguy]

https://github.com/github/octodns/issues/63 I think is related to making log messages more clear.

There could definitely be a bit more descriptive errors, in-depth knowledge of DNS is needed to understand sometimes what went wrong, whether it be on the OctoDNS side or something that’s happening because of behavior in a provider.

Thanks for the feedback!

[brianeclow]

I just ran into this:

• A cnames cannot point to itself.

A DNS provider happily allowed us to create this condition via the web ux, however, route53 and dyn rejected it upon attempting to create the entries via octodns with the --doit flag.