StackExchange/dnscontrol
1
1
Fork 0
mirror of https://github.com/StackExchange/dnscontrol.git synced 2025-01-10 17:38:13 +08:00
Code Issues Projects Releases Packages Wiki Activity
dnscontrol/OWNERS

18 lines
438 B
Text
Raw Normal View History

Add OWNERS file and instructions.
2017-11-10 02:38:56 +08:00
# providers/activedir
Add Azure DNS (#547) * Add Azure DNS * Remove unused code * Fix failing tests and update build
2019-09-19 09:45:14 +08:00
providers/azuredns @vatsalyagoel
Add OWNERS file and instructions.
2017-11-10 02:38:56 +08:00
providers/bind @tlimoncelli
# providers/cloudflare
providers/digitalocean @Deraen
providers/dnsimple @aeden
providers/gandi @TomOnTime
# providers/gcloud
new provider module HEXONET (#373)
2018-08-30 20:54:42 +08:00
providers/hexonet @papakai
New provider: Linode (#268)
2017-11-15 12:08:06 +08:00
providers/linode @koesie10
Add OWNERS file and instructions.
2017-11-10 02:38:56 +08:00
providers/namecheap @captncraig
# providers/namedotcom
providers/ns1 @captncraig
# providers/route53
# providers/softlayer
providers/vultr @geek1011
New Provider: OVH DNS Provider (#143) (#175) * OVH DNS Provider (#143) This adds the OVH Provider along with its documentation. Unfortunately we can't set this DNS provider to support `CanUsePTR`, because OVH only supports setting PTR target on the Arpa zone. * OVH Registrar provider (#143) This implements OVH as a registrar provider. Note that NS modifications are done in a "best effort" mode, as the provider doesn't wait for the modifications to be fully applied (the operation that can take a long time). * Allow support for dual providers scenarios Since OVH released their APIv6, it is now possible to update zone apex NS records, opening the door to complete dual providers scenarii. This change implements apex NS management in an OVH zone.
2017-11-11 03:02:34 +08:00
providers/ovh @masterzen
Reference in a new issue Copy permalink