Provider Features

The table below shows various features supported, or not supported by DNSControl providers.
Underlined items have tooltips for more detailed explanation. This table is automatically generated
from metadata supplied by the provider when they register themselves inside dnscontrol.

An empty space may indicate the feature is not supported by a provider, or it may simply mean
the feature has not been investigated and implemented yet. If a feature you need is missing from
a provider that supports it, we'd love your contribution to ensure it works correctly and add it to this matrix.

If a feature is definitively not supported for whatever reason, we would also like a PR to clarify why it is not supported, and fill in this entire matrix.

ACTIVEDIRECTORY_PS

BIND

CLOUDFLAREAPI

DIGITALOCEAN

DNSIMPLE

GANDI

GCLOUD

LINODE

NAMECHEAP

NAMEDOTCOM

NS1

OVH

ROUTE53

SOFTLAYER

VULTR

Official Support

Registrar

DNS Provider

ALIAS

SRV

PTR

CAA

TLSA

dual host

create-domains

no_purge

Providers with “official support”

Official support means:

New releases will block if any of these providers do not pass integration tests.

Providers with “contributor support”

The other providers are supported by community members, usually the
original contributor.

Due to the large number of DNS providers in the world, the DNSControl
team can not support and test all providers. Test frameworks are
provided to help community members support their code independently.

Maintainers are expected to support their provider and/or find a new maintainer.

Bugs will be referred to the original contributor or their designate.

Maintainers should set up test accounts and regularly verify that all tests pass (pkg/js/parse_tests and integrationTest).

Contributors are encouraged to add new tests and refine old ones. (Test-driven development is encouraged.)

Maintainers of contributed providers:

digital ocean @Deraen

dnsimple @aeden

gandi @TomOnTime

Linode @koesie10

namecheap @captncraig

ns1 @captncraig

OVH @masterzen

Vultr @geek1011

Requested providers

We have received requests for the following providers. If you would like to contribute
code to support this provider, please re-open the issue. We’d be glad to help in any way.

In progress providers

These requests have open issues, which indicates somebody is actively working on it. Feel free to follow the issue, or pitch in if you think you can help.

Providers with open PRs

These providers have an open pr with (potentially) working code. They may be ready to merge, or may have blockers. See issue and pr for details.