Add support for more DNS providers

[Ice3man543]

We should have more DNS provider integrations for getting complete list.

• Add Support for Azure DNS DNS provider
• Add Support for Linode DNS provider
• Add Support for Cloudflare DNS provider
• Add Support for Alibaba cloud DNS provider
• Add Support for Namecheap DNS provider
• Add Support for Active Directory DNS provider
• Add Support for AXFR+DDNS DNS provider
• Add Support for BIND DNS provider
• Add Support for ClouDNS DNS provider
• Add Support for Constellix (DNSMadeEasy) DNS provider
• Add Support for CSC Global DNS provider
• Add Support for deSEC DNS provider
• Add Support for DNSimple DNS provider
• Add Support for Exoscale DNS provider
• Add Support for Gandi DNS provider
• Add Support for GoDaddy DNS provider
• Add Support for Hetzner DNS provider
• Add Support for HEXONET DNS provider
• Add Support for Hurricane Electric DNS DNS provider
• Add Support for Internet.bs DNS provider
• Add Support for INWX DNS provider
• Add Support for Joker.com DNS provider
• Add Support for knot-dns DNS provider
• Add Support for Name.com DNS provider
• Add Support for NameSilo DNS provider
• Add Support for Netcup DNS provider
• Add Support for Netlify DNS provider
• Add Support for NS1 DNS provider
• Add Support for OctoDNS DNS provider
• Add Support for OpenSRS DNS provider
• Add Support for Oracle Cloud Infrastructure DNS provider
• Add Support for OVH DNS provider
• Add Support for PowerDNS DNS provider
• Add Support for RcodeZero DNS provider
• Add Support for SoftLayer DNS provider
• Add Support for Vultr DNS provider

[mzpqnxow]

FYI- I added a note to #5 about some work I've done. If speaking strictly about DNS providers (and not sources of DNS names) then I think the only source I have that would be of use here is CSC, which is in your list as not yet implemented. I use the following endpoints to dump data

• https://apis.cscglobal.com/dbs/api/v2
  • /domains (CSC domain registration data)
  • /zones (Resource records for all zones in the account)
  • /tls/certificates (CSC certificate issuance data)

The API pattern is pretty simple if you just want to grab the RRs. Authenticate, and then make paged requests to /dbs/api/v2/zones, which will return all of the RRs for all zones

The paging mechanism (for the domains endpoint, though the zones endpoint is the same):

        'domains': [ ... ],
        'meta': {'numResults': 560, 'pages': 56},
        'links': {
            'self': 'https://apis.cscglobal.com/dbs/api/v2/domains?page=1&size=10',
            'next': 'https://apis.cscglobal.com/dbs/api/v2/domains?page=2&size=10'}
        }

CSC is one of the few sources I've encountered where you don't need one call per-zone, simply using /dbs/api/v2/zones returns every resource record in every zone. Very convenient :)

Hope this is helpful and saves you 30 minutes of reading the API docs (actually, it tookl me longer to find the documentation than it did to write the code)

I'll try to contribute an implementation if I have the time and there aren't conflicts with my employer

Thanks for your work on this project

[mzpqnxow]

If I can add one question, can you clarify these two from your list:

• Add Support for BIND DNS provider
• Add Support for AXFR+DDNS DNS provider

Are you referring to parsing BIND format zone files / AXFRs or are either of these also the names of some DNS provider/service?

I ask because I've done some work to perform and process AXFR data, both with and without TSIG keys, via dig and natively via dnspython. Neither of these are necessarily complicated or difficult, but may be something I can port to golang and contribute if I have time