-
-
Notifications
You must be signed in to change notification settings - Fork 243
DNS Provider Configuration
Tatsuro Shibamura edited this page Feb 27, 2021
·
28 revisions
-
Acmebot:Route53:AccessKey
- IAM access key
-
Acmebot:Route53:SecretKey
- IAM secret key
-
Acmebot:Route53:Region
- Default AWS region
-
Acmebot:AzureDns:SubscriptionId
- Subscription ID include Azure DNS
Open the Access Control (IAM)
of the target DNS zone or resource group containing the DNS zone, and assign the role of DNS Zone Contributor
to the deployed application.
-
Acmebot:Cloudflare:ApiToken
- API Token (requires
Zone:Read
andDNS:Edit
permissions)
- API Token (requires
Acmebot:DnsMadeEasy:ApiKey
-
Acmebot:DnsMadeEasy:SecretKey
- DNS Made Easy API credentials
Acmebot:GoogleDns:KeyFile64
- Create a service account for your project with DNS readwrite access. (https://www.googleapis.com/auth/ndev.clouddns.readwrite)
- Generate and download a json keyfile.
- Take keyfile contents and encode them in base64
- Create a new application setting named
Acmebot:Google:KeyFile64
and paste the base64 encoded string into it.
Acmebot:GratisDns:Username
-
Acmebot:GratisDns:Password
- GratisDNS admin credentials
-
Acmebot:TransIp:CustomerName
- this is the customer name / username of your TransIp account
-
Acmebot:TransIp:PrivateKeyName
- this is the name of the private key in the Azure Key Vault