From 280c62670470c8090c1d7c7f78f29ca9cbdc3e5e Mon Sep 17 00:00:00 2001 From: Johan Siebens Date: Wed, 28 May 2025 21:39:25 +0200 Subject: [PATCH] fix incorrect dns configuration examples --- mkdocs/docs/configuration/dns-providers.md | 16 ++++++---------- 1 file changed, 6 insertions(+), 10 deletions(-) diff --git a/mkdocs/docs/configuration/dns-providers.md b/mkdocs/docs/configuration/dns-providers.md index 87a9a39..b9cd0b6 100644 --- a/mkdocs/docs/configuration/dns-providers.md +++ b/mkdocs/docs/configuration/dns-providers.md @@ -99,10 +99,7 @@ dns: name: "cloudflare" zone: "example.com" config: - auth_token: "your-cloudflare-api-token" - # OR use email/api_key authentication - # email: "your-email@example.com" - # api_key: "your-global-api-key" + api_token: "your-cloudflare-api-token" ``` For Cloudflare, create an API token with the "Edit" permission for "Zone:DNS". @@ -138,6 +135,7 @@ dns: secret_access_key: "your-secret-access-key" # Optional region, defaults to us-east-1 region: "us-east-1" + ... ``` For AWS Route 53, create an IAM user with permissions to modify records in your hosted zone. @@ -151,11 +149,9 @@ dns: name: "googleclouddns" zone: "example-com" # Note: GCP uses zone names without dots config: - project: "your-project-id" - # Either provide service account JSON directly - service_account_json: '{"type":"service_account","project_id":"your-project",...}' - # OR specify a path to a service account key file - # service_account_key_file: "/path/to/service-account-key.json" + gcp_project: "your-project-id" + # Optional path to a service account key file + # gcp_application_default: "/path/to/service-account-key.json" ``` For Google Cloud DNS, create a service account with the "DNS Administrator" role. @@ -169,7 +165,7 @@ dns: name: "digitalocean" zone: "example.com" config: - token: "your-digitalocean-api-token" + auth_token: "your-digitalocean-api-token" ``` For DigitalOcean, create an API token with read and write access.