Chris Marchesi 64f8e0d225 providers/dns/route53: Adjust DNS challenge TTL to 10 seconds ... While more than likely never to come up in a real-world situation, during renewal integration testing a value of 120 seconds has proven to be too high (the old challenge record has not expired by the time the new one is created).		2016-06-17 16:07:37 -07:00
..
cloudflare	Better cloudflare API error handling. Report all errors if more then one error is available.	2016-05-19 18:33:35 +02:00
digitalocean	Retry logic for dnsQuery	2016-04-12 00:24:11 +01:00
dnsimple	Fix: DNSimple passes not-a-FQDN string to FindZoneByFqdn()	2016-04-17 04:43:43 +02:00
dyn	Fixes #199	2016-04-26 22:36:48 -04:00
gandi	Retry logic for dnsQuery	2016-04-12 00:24:11 +01:00
googlecloud	Make DNS provider credential-handling more consistent.	2016-03-20 11:40:30 -07:00
namecheap	Make DNS provider credential-handling more consistent.	2016-03-20 11:40:30 -07:00
rfc2136	Retry logic for dnsQuery	2016-04-12 00:24:11 +01:00
route53	providers/dns/route53: Adjust DNS challenge TTL to 10 seconds	2016-06-17 16:07:37 -07:00
vultr	Add DNS challenge provider for Vultr.	2016-03-23 20:35:23 +00:00