github.com/teknogeek/dnscontrol/v2@v2.10.1-0.20200227202244-ae299b55ba42/docs/provider-list.md (about)

     1  ---
     2  layout: default
     3  title: Service Providers
     4  ---
     5  <h1> Service Providers </h1>
     6  
     7  <table class='table table-bordered'>
     8    <thead>
     9      <th>Name</th>
    10      <th>Identifier</th>
    11    </thead>
    12  {% for p in site.providers %}
    13  <tr>
    14    <td><a href=".{{p.id}}">{{p.name}}</a></td>
    15    <td>{{p.jsId}}</td>
    16  </tr>
    17  {% endfor %}
    18  </table>
    19  
    20  <a name="features"></a>
    21  <h2> Provider Features </h2>
    22  
    23  <p>The table below shows various features supported, or not supported by DNSControl providers.
    24    Underlined items have tooltips for more detailed explanation. This table is automatically generated
    25    from metadata supplied by the provider when they register themselves inside dnscontrol.
    26  </p>
    27  <p>
    28    An empty space may indicate the feature is not supported by a provider, or it may simply mean
    29    the feature has not been investigated and implemented yet. If a feature you need is missing from
    30    a provider that supports it, we'd love your contribution to ensure it works correctly and add it to this matrix.
    31  </p>
    32  <p>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.</p>
    33  <br/>
    34  <br/>
    35  
    36  {% include matrix.html %}
    37  
    38  
    39  ### Providers with "official support"
    40  
    41  Official support means:
    42  
    43  * New releases will block if any of these providers do not pass integration tests.
    44  * The DNSControl maintainers prioritize fixing bugs in these providers (though we gladly accept PRs).
    45  * New features will work on these providers (unless the provider does not support it).
    46  * StackOverflow maintains test accounts with those providers for running integration tests.
    47  
    48  Current owners are:
    49  
    50  * `ACTIVEDIRECTORY_PS` @tlimoncelli
    51  * `AZURE_DNS` @vatsalyagoel
    52  * `BIND` @tlimoncelli
    53  * `CLOUDFLAREAPI` @tlimoncelli
    54  * `GCLOUD` @tlimoncelli
    55  * `NAMEDOTCOM` @tlimoncelli
    56  * `ROUTE53` @tlimoncelli
    57  
    58  ### Providers with "contributor support"
    59  
    60  The other providers are supported by community members, usually the
    61  original contributor.
    62  
    63  Due to the large number of DNS providers in the world, the DNSControl
    64  team can not support and test all providers.  Test frameworks are
    65  provided to help community members support their code independently.
    66  
    67  * Maintainers are expected to support their provider and/or find a new maintainer.
    68  * Bugs will be referred to the original contributor or their designate.
    69  * Maintainers should set up test accounts and regularly verify that all tests pass (`pkg/js/parse_tests` and `integrationTest`).
    70  * Contributors are encouraged to add new tests and refine old ones. (Test-driven development is encouraged.)
    71  
    72  Maintainers of contributed providers:
    73  
    74  * `CLOUDNS` @pragmaton
    75  * `DIGITALOCEAN` @Deraen
    76  * `DNSIMPLE` @aeden
    77  * `EXOSCALE` @pierre-emmanuelJ
    78  * `GANDI_V5` @TomOnTime
    79  * `GANDI-LIVEDNS` (going away in 3.0)
    80  * `GANDI` (going away in 3.0)
    81  * `HEXONET` @papakai
    82  * `INTERNETBS` @pragmaton
    83  * `LINODE` @koesie10
    84  * `NAMECHEAP` @captncraig
    85  * `NS1` @captncraig
    86  * `OCTODNS` @TomOnTime
    87  * `OPENSRS` @pierre-emmanuelJ
    88  * `OVH` @masterzen
    89  * `SOFTLAYER`@jamielennox
    90  * `VULTR` @geek1011
    91  
    92  ### Requested providers
    93  
    94  We have received requests for the following providers. If you would like to contribute
    95  code to support this provider, please re-open the issue. We'd be glad to help in any way.
    96  
    97  <ul id='requests'>
    98  
    99  </ul>
   100  
   101  ### In progress providers
   102  
   103  These requests have an *open* issue, which indicates somebody is actively working on it. Feel free to follow the issue, or pitch in if you think you can help.
   104  
   105  <ul id='inprog'>
   106  </ul>
   107  
   108  ### Providers with open PRs
   109  
   110  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.
   111  
   112  <ul id='haspr'>
   113  </ul>
   114  
   115  <script>
   116  $(function() {
   117    $.get("https://api.github.com/repos/StackExchange/dnscontrol/issues?state=all&labels=provider-request&direction=asc")
   118    .done(function(data) {
   119      for(var i of data) {
   120        var el = $(`<li><a href='${i.html_url}'>${i.title}</a> (#${i.number})</li>`);
   121        var target = $("#requests");
   122        if (i.state == "open") {
   123          target = $("#inprog");
   124          for(var l of i.labels) {
   125            if (l.name == "has-pr")
   126              target = $("#haspr");
   127          }
   128        }
   129        target.append(el);
   130      }
   131    })
   132    .fail(function(err){
   133      console.log("???", err)
   134    });
   135  });
   136  </script>