From 7389aef444067ea20911724b3cd0b5d7efcc67e1 Mon Sep 17 00:00:00 2001 From: Matt Holt Date: Mon, 8 May 2017 11:42:39 -0600 Subject: [PATCH] Update link to forum --- Writing-a-Plugin:-DNS-Provider.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Writing-a-Plugin:-DNS-Provider.md b/Writing-a-Plugin:-DNS-Provider.md index 99f3f9a..2df321b 100644 --- a/Writing-a-Plugin:-DNS-Provider.md +++ b/Writing-a-Plugin:-DNS-Provider.md @@ -1,4 +1,4 @@ -**[Join the Caddy Community Forum](https://forum.caddyserver.com) to chat with other Caddy developers!** +**[Join the Caddy Community Forum](https://caddy.community) to chat with other Caddy developers!** Caddy magically obtains TLS certificates for your site in 3 ways: HTTP, TLS-SNI, and DNS. The first two are used by default and can be completed without intervention by you. The third is more versatile in some environments where you cannot start a listener that can be accessed by external networks, etc. The problem is that doing it the DNS way requires custom code to interact with the DNS provider whom your domain's nameservers are pointed to.