From e3f73618b1076b6848ebf179e03596bb6ec18d5d Mon Sep 17 00:00:00 2001 From: cliedeman Date: Thu, 4 Oct 2018 18:49:28 +0200 Subject: [PATCH] Added linode to support cloud providers --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index 364aa12a5..b67829a9b 100644 --- a/README.md +++ b/README.md @@ -38,6 +38,7 @@ ExternalDNS' current release is `v0.5`. This version allows you to keep selected * [CoreDNS](https://coredns.io/) * [Exoscale](https://www.exoscale.com/dns/) * [Oracle Cloud Infrastructure DNS](https://docs.cloud.oracle.com/iaas/Content/DNS/Concepts/dnszonemanagement.htm) +* [Linode DNS](https://www.linode.com/docs/networking/dns/) From this release, ExternalDNS can become aware of the records it is managing (enabled via `--registry=txt`), therefore ExternalDNS can safely manage non-empty hosted zones. We strongly encourage you to use `v0.5` (or greater) with `--registry=txt` enabled and `--txt-owner-id` set to a unique value that doesn't change for the lifetime of your cluster. You might also want to run ExternalDNS in a dry run mode (`--dry-run` flag) to see the changes to be submitted to your DNS Provider API.