github.com/StackExchange/DNSControl@v0.2.8/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 ### Providers with "contributor support" 49 50 The other providers are supported by community members, usually the 51 original contributor. 52 53 Due to the large number of DNS providers in the world, the DNSControl 54 team can not support and test all providers. Test frameworks are 55 provided to help community members support their code independently. 56 57 * Maintainers are expected to support their provider and/or find a new maintainer. 58 * Bugs will be referred to the original contributor or their designate. 59 * Maintainers should set up test accounts and regularly verify that all tests pass (`pkg/js/parse_tests` and `integrationTest`). 60 * Contributors are encouraged to add new tests and refine old ones. (Test-driven development is encouraged.) 61 62 Maintainers of contributed providers: 63 64 * digital ocean @Deraen 65 * dnsimple @aeden 66 * gandi @TomOnTime 67 * HEXONET @papakai 68 * Linode @koesie10 69 * namecheap @captncraig 70 * ns1 @captncraig 71 * OVH @masterzen 72 * Vultr @geek1011 73 74 ### Requested providers 75 76 We have received requests for the following providers. If you would like to contribute 77 code to support this provider, please re-open the issue. We'd be glad to help in any way. 78 79 <ul id='requests'> 80 81 </ul> 82 83 ### In progress providers 84 85 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. 86 87 <ul id='inprog'> 88 </ul> 89 90 ### Providers with open PRs 91 92 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. 93 94 <ul id='haspr'> 95 </ul> 96 97 <script> 98 $.get("https://api.github.com/repos/StackExchange/dnscontrol/issues?state=all&labels=provider-request&direction=asc") 99 .done(function(data){ 100 for(var i of data){ 101 var el = $(`<li><a href='${i.html_url}'>${i.title}</a> (#${i.number})</li>`) 102 var target = $("#requests"); 103 if (i.state == "open") target = $("#inprog"); 104 for(var l of i.labels){ 105 if (l.name == "has-pr") target = $("#haspr"); 106 } 107 target.append(el); 108 } 109 }) 110 .fail(function(err){ 111 console.log("???", err) 112 }) 113 </script>