Providers

Provider Features

The table below shows various features supported, or not supported by DNSControl providers. 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.

Provider name

Official Support

DNS Provider

Registrar

Concurrency Verified

dual host

create-domains

get-zones

Providers with "official support"

Official support means:

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

  • The DNSControl maintainers prioritize fixing bugs in these providers (though we gladly accept PRs).

  • New features will work on these providers (unless the provider does not support it).

  • StackOverflow maintains test accounts with those providers for running integration tests.

Providers in this category and their maintainers are:

NameMaintainer

@vatsalyagoel

@tlimoncelli

@tresni

@mikenz

@riyadhalnur

@tlimoncelli

@tresni

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.

Expectations of maintainers:

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

  • Maintainers should set up test accounts and periodically 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.)

  • Bugs will be referred to the maintainer or their designate.

  • Maintainers must be responsible to bug reports and PRs. If a maintainer is unresponsive for more than 2 months, we will consider disabling the provider. First we will put out a call for new maintainer. If nobody volunteers, the provider may be disabled.

  • Tom needs to know your real email address. Please email tlimoncelli at stack over flow dot com so he has it.

Providers in this category and their maintainers are:

NameMaintainer

@matthewmgamble

@edglynes

@hnrgrgr

@ppmathis

@tresni

@pragmaton

@Air-New-Zealand

@D3luxee

@Deraen

@onlyhavecans

@vojtad

@mikenz

@SimenBai

@tresni

@pierre-emmanuelJ

@TomOnTime

@xddxdd

@rblenkinsopp

@das7pad

@KaiSchwarz-cnic

@membero

@pragmaton

@patschi

@koesie10

@systemcrash

@riku22

@willpower232

@kordianbruck

@SphericalKat

@costasd

@philhug

@kallsyms

@masterzen

@hamptonmoore

@jpbede

@PJEilers

@tresni

@MisterErwin

@jamielennox

@blackshadev

@pgaskin

Requested providers

We have received requests for the following providers. If you would like to contribute code to support this provider, we'd be glad to help in any way.

Q: Why are the above GitHub issues marked "closed"?

A: Following the bug triage process, the request is closed once it is added to this list. If someone chooses to implement the provider, they re-open the issue.

Q: Would someone write a provider for me?

A: The maintainer of DNSControl does not write new providers. New providers are contributed by the community.

DNSControl tries to make writing a provider as easy as possible. DNSControl does most of the work for you, you only have to write code to authenticate, download DNS records, and perform create/modify/delete operations on those records. Please read the directions for Writing new DNS providers. The DNS maintainers will gladly coach you through the process.

Last updated