A quick summary of a problem with have with DNSimple provider:
Let's suppose that I have the following config:
zones:
30.114.195.in-addr.arpa.:
sources:
- config
targets:
- dnsimple
Even if a customer has this Reverse zone configured in DNSimple, this
fails with:
400 Bad Request for url: https://api.sandbox.dnsimple.com/v2/x/domains
because it is trying to create a domain because the zone wasn't found.
octodns.provider.dnsimple.DnsimpleClientNotFound: Not found
This happens because the GET /domains endpoint at DNSimple does not
bring Reverse Zones. To make this work nice, we should use /zones/
instead making it return properly the reverse zones.
DNSimple does not handle NULL SRV records correctly (either via
their web interface or API). Flag to end user if attempted.
Issue noted with DNSimple support 2020-12-09
Implements the unsupported records skipping fix [proposed by ross](https://github.com/github/octodns/issues/176#issuecomment-359294960) in #176 for DNSimple and additionally for NS1.
Fixes #176 and also the NS1 version of it (`AttributeError: 'Ns1Provider' object has no attribute '_data_for_DNSKEY'`) that currently affect domains that have DNSSEC enabled.
- adds lenient flag to Record.new, problems during validation are just
warnings if it's true
- target populate calls during the plan phase pass lenient=True
- make all of the provider.populate call logging consistent including both
target and lenient
- add source=self to Record.new in a few places that were missing it
Supports ALIAS for Dnsimple, Dyn, Ns1, and PowerDNS. Notes added to readme about
some of the quirks found while working with them. TTL seems to mostly be
accepted on ALIAS records so it has been added back, what it means seems to vary
across providers, thus notes.
