Managing DNS connectors

Configure a DNS connector

Once installed, DNS connectors must be configured to connect to your DNS provider. Multiple DNS providers can be connected to a single connector.

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Add the Cloudflare provider.

sectigo-dcs.exe provider add -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

Option	Description
`type`	The type of DNS provider that is being added. For Cloudflare, the value must be `cloudflare`.
`name`	The name used to represent the DNS provider in SCM.
`token`	The authentication token specific to your Cloudflare user or account. This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Amazon Route 53 provider.

sectigo-dcs.exe provider add -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

Option	Description
`type`	The type of DNS provider that is being added. For Amazon Route 53, the value must be `route53`.
`name`	The name used to represent the DNS provider in SCM.
`access-key-id`	The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.
`region`	The AWS region where your Route 53 resources are located. Some examples of AWS region IDs include `us-east-1`, `eu-west-1`, and so on.
`secret-key`	The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.
`session-token`	(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Azure DNS provider.

sectigo-dcs.exe provider add -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

Option	Description
`type`	The type of DNS provider that is being added. For Azure DNS, the value must be `azure`.
`name`	The name used to represent the DNS provider in SCM.
`resource-group`	The name of the Azure resource group that contains your DNS zone.
`subscription`	The Azure subscription ID associated with your account. This identifies your subscription within Azure.
`tenant-id`	The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.
`client-id`	The client ID of the Microsoft Entra application. This is used for authentication.
`client-secret`	The client secret associated with the Microsoft Entra application. This is used for authentication.

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the GoDaddy DNS provider.

sectigo-dcs.exe provider add -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

Option	Description
`type`	The type of DNS provider that is being added. For GoDaddy DNS, the value must be `godaddy`.
`name`	The name used to represent the DNS provider in SCM.
`api-key`	The API key generated from your GoDaddy account. This key is used to authenticate API requests.
`api-secret`	The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Akamai Edge DNS provider.

sectigo-dcs.exe provider add -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

Option	Description
`type`	The type of DNS provider that is being added. For Akamai Edge DNS, the value must be `akamai`.
`name`	The name used to represent the DNS provider in SCM.
`access-token`	The access token generated from your Akamai account. This token is used to authenticate API requests.
`client-secret`	The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.
`client-token`	The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.
`host`	The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the DNSimple DNS provider.

sectigo-dcs.exe provider add -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

Option	Description
`type`	The type of DNS provider that is being added. For DNSimple DNS, the value must be `dnsimple`.
`name`	The name used to represent the DNS provider in SCM.
`access-token`	The access token generated from your DNSimple account. This token is used to authenticate API requests.
`account-id`	The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the OVHcloud provider.

sectigo-dcs.exe provider add -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

Option	Description
`type`	The type of DNS provider that is being added. For OVHcloud, the value must be `ovh`.
`name`	The name used to represent the DNS provider in SCM.
`endpoint`	The OVH region ID indicating where your services are hosted. Some examples of OVHcloud region IDs include `ovh-eu`, `ovh-ca`, and `ovh-us`.
`app-key`	The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.
`app-secret`	The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.
`consumer-key`	The Consumer Key (CK) obtained after authenticating your application with OVHcloud’s API using your Application Key and Application Secret. This key grants your application permission to make API requests on behalf of a user’s account.

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

The Consumer Key (CK) obtained after authenticating your application with OVHcloud’s API using your Application Key and Application Secret. This key grants your application permission to make API requests on behalf of a user’s account.

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

Option	Description
`type`	The type of DNS provider that is being added. For Bind, the value must be `bind`.
`name`	The name used to represent the DNS provider in SCM.
`host`	The hostname or IP address of the Bind server.
`key-file`	The path to the Transaction SIGnature(TSIG) key file used for authentication.
`port`	(Optional) The port number on which the Bind server is listening (default `53`).

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

Option	Description
`type`	The type of DNS provider that is being added. For Infoblox, the value must be `infoblox`.
`name`	The name used to represent the DNS provider in SCM.
`host`	The Infoblox server host name (FQDN or IP address).
`username`	The Infoblox account name used by the connector to authenticate to the API.
`password`	The Infoblox account password.
`dns-view`	(Optional) The Infoblox DNS View where records are managed. (default `External`).
`port`	(Optional) The port number (default `443`).
`version`	(optional) The Infoblox API version to use for requests..

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

Option	Description
`type`	The type of DNS provider that is being added. For Google Cloud, the value must be `google`.
`name`	The name used to represent the DNS provider in SCM.
`project`	The Google Cloud Project ID.
`cred-file`	The path to the Google Cloud credentials JSON file.

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

Option	Description
`type`	The type of DNS provider that is being added. For Cloudflare, the value must be `cloudflare`.
`name`	The name used to represent the DNS provider in SCM.
`token`	The authentication token specific to your Cloudflare user or account. This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

Option	Description
`type`	The type of DNS provider that is being added. For Amazon Route 53, the value must be `route53`.
`name`	The name used to represent the DNS provider in SCM.
`access-key-id`	The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.
`region`	The AWS region where your Route 53 resources are located. Some examples of AWS region IDs include `us-east-1`, `eu-west-1`, and so on.
`secret-key`	The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.
`session-token`	(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

Option	Description
`type`	The type of DNS provider that is being added. For Azure DNS, the value must be `azure`.
`name`	The name used to represent the DNS provider in SCM.
`resource-group`	The name of the Azure resource group that contains your DNS zone.
`subscription`	The Azure subscription ID associated with your account. This identifies your subscription within Azure.
`tenant-id`	The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.
`client-id`	The client ID of the Microsoft Entra application. This is used for authentication.
`client-secret`	The client secret associated with the Microsoft Entra application. This is used for authentication.

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

Option	Description
`type`	The type of DNS provider that is being added. For GoDaddy DNS, the value must be `godaddy`.
`name`	The name used to represent the DNS provider in SCM.
`api-key`	The API key generated from your GoDaddy account. This key is used to authenticate API requests.
`api-secret`	The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

Option	Description
`type`	The type of DNS provider that is being added. For Akamai Edge DNS, the value must be `akamai`.
`name`	The name used to represent the DNS provider in SCM.
`access-token`	The access token generated from your Akamai account. This token is used to authenticate API requests.
`client-secret`	The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.
`client-token`	The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.
`host`	The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

Option	Description
`type`	The type of DNS provider that is being added. For DNSimple DNS, the value must be `dnsimple`.
`name`	The name used to represent the DNS provider in SCM.
`access-token`	The access token generated from your DNSimple account. This token is used to authenticate API requests.
`account-id`	The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

Option	Description
`type`	The type of DNS provider that is being added. For OVHcloud, the value must be `ovh`.
`name`	The name used to represent the DNS provider in SCM.
`endpoint`	The OVH region ID indicating where your services are hosted. Some examples of OVHcloud region IDs include `ovh-eu`, `ovh-ca`, and `ovh-us`.
`app-key`	The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.
`app-secret`	The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.
`consumer-key`	The Consumer Key (CK) obtained after authenticating your application with OVHcloud’s API using your Application Key and Application Secret. This key grants your application permission to make API requests on behalf of a user’s account.

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

Option	Description
`type`	The type of DNS provider that is being added. For Bind, the value must be `bind`.
`name`	The name used to represent the DNS provider in SCM.
`host`	The hostname or IP address of the Bind server.
`key-file`	The path to the Transaction SIGnature(TSIG) key file used for authentication.
`port`	(Optional) The port number on which the Bind server is listening (default `53`).

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

Option	Description
`type`	The type of DNS provider that is being added. For Infoblox, the value must be `infoblox`.
`name`	The name used to represent the DNS provider in SCM.
`host`	The Infoblox server host name (FQDN or IP address).
`username`	The Infoblox account name used by the connector to authenticate to the API.
`password`	The Infoblox account password.
`dns-view`	(Optional) The Infoblox DNS View where records are managed. (default `External`).
`port`	(Optional) The port number (default `443`).
`version`	(optional) The Infoblox API version to use for requests..

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

Option	Description
`type`	The type of DNS provider that is being added. For Google Cloud, the value must be `google`.
`name`	The name used to represent the DNS provider in SCM.
`project`	The Google Cloud Project ID.
`cred-file`	The path to the Google Cloud credentials JSON file.

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

Option	Description
`type`	The type of DNS provider that is being added. For Cloudflare, the value must be `cloudflare`.
`name`	The name used to represent the DNS provider in SCM.
`token`	The authentication token specific to your Cloudflare user or account. This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

Option	Description
`type`	The type of DNS provider that is being added. For Amazon Route 53, the value must be `route53`.
`name`	The name used to represent the DNS provider in SCM.
`access-key-id`	The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.
`region`	The AWS region where your Route 53 resources are located. Some examples of AWS region IDs include `us-east-1`, `eu-west-1`, and so on.
`secret-key`	The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.
`session-token`	(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

Option	Description
`type`	The type of DNS provider that is being added. For Azure DNS, the value must be `azure`.
`name`	The name used to represent the DNS provider in SCM.
`resource-group`	The name of the Azure resource group that contains your DNS zone.
`subscription`	The Azure subscription ID associated with your account. This identifies your subscription within Azure.
`tenant-id`	The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.
`client-id`	The client ID of the Microsoft Entra application. This is used for authentication.
`client-secret`	The client secret associated with the Microsoft Entra application. This is used for authentication.

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

Option	Description
`type`	The type of DNS provider that is being added. For GoDaddy DNS, the value must be `godaddy`.
`name`	The name used to represent the DNS provider in SCM.
`api-key`	The API key generated from your GoDaddy account. This key is used to authenticate API requests.
`api-secret`	The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

Option	Description
`type`	The type of DNS provider that is being added. For Akamai Edge DNS, the value must be `akamai`.
`name`	The name used to represent the DNS provider in SCM.
`access-token`	The access token generated from your Akamai account. This token is used to authenticate API requests.
`client-secret`	The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.
`client-token`	The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.
`host`	The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

Option	Description
`type`	The type of DNS provider that is being added. For DNSimple DNS, the value must be `dnsimple`.
`name`	The name used to represent the DNS provider in SCM.
`access-token`	The access token generated from your DNSimple account. This token is used to authenticate API requests.
`account-id`	The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

Option	Description
`type`	The type of DNS provider that is being added. For OVHcloud, the value must be `ovh`.
`name`	The name used to represent the DNS provider in SCM.
`endpoint`	The OVH region ID indicating where your services are hosted. Some examples of OVHcloud region IDs include `ovh-eu`, `ovh-ca`, and `ovh-us`.
`app-key`	The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.
`app-secret`	The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.
`consumer-key`	The Consumer Key (CK) obtained after authenticating your application with OVHcloud’s API using your Application Key and Application Secret. This key grants your application permission to make API requests on behalf of a user’s account.

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

Option	Description
`type`	The type of DNS provider that is being added. For Bind, the value must be `bind`.
`name`	The name used to represent the DNS provider in SCM.
`host`	The hostname or IP address of the Bind server.
`key-file`	The path to the Transaction SIGnature(TSIG) key file used for authentication.
`port`	(Optional) The port number on which the Bind server is listening (default `53`).

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

Option	Description
`type`	The type of DNS provider that is being added. For Infoblox, the value must be `infoblox`.
`name`	The name used to represent the DNS provider in SCM.
`host`	The Infoblox server host name (FQDN or IP address).
`username`	The Infoblox account name used by the connector to authenticate to the API.
`password`	The Infoblox account password.
`dns-view`	(Optional) The Infoblox DNS View where records are managed. (default `External`).
`port`	(Optional) The port number (default `443`).
`version`	(optional) The Infoblox API version to use for requests..

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

Option	Description
`type`	The type of DNS provider that is being added. For Google Cloud, the value must be `google`.
`name`	The name used to represent the DNS provider in SCM.
`project`	The Google Cloud Project ID.
`cred-file`	The path to the Google Cloud credentials JSON file.

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

Option	Description
`type`	The type of DNS provider that is being added. For Cloudflare, the value must be `cloudflare`.
`name`	The name used to represent the DNS provider in SCM.
`token`	The authentication token specific to your Cloudflare user or account. This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

Option	Description
`type`	The type of DNS provider that is being added. For Amazon Route 53, the value must be `route53`.
`name`	The name used to represent the DNS provider in SCM.
`access-key-id`	The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.
`region`	The AWS region where your Route 53 resources are located. Some examples of AWS region IDs include `us-east-1`, `eu-west-1`, and so on.
`secret-key`	The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.
`session-token`	(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

Option	Description
`type`	The type of DNS provider that is being added. For Azure DNS, the value must be `azure`.
`name`	The name used to represent the DNS provider in SCM.
`resource-group`	The name of the Azure resource group that contains your DNS zone.
`subscription`	The Azure subscription ID associated with your account. This identifies your subscription within Azure.
`tenant-id`	The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.
`client-id`	The client ID of the Microsoft Entra application. This is used for authentication.
`client-secret`	The client secret associated with the Microsoft Entra application. This is used for authentication.

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

Option	Description
`type`	The type of DNS provider that is being added. For GoDaddy DNS, the value must be `godaddy`.
`name`	The name used to represent the DNS provider in SCM.
`api-key`	The API key generated from your GoDaddy account. This key is used to authenticate API requests.
`api-secret`	The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

Option	Description
`type`	The type of DNS provider that is being added. For Akamai Edge DNS, the value must be `akamai`.
`name`	The name used to represent the DNS provider in SCM.
`access-token`	The access token generated from your Akamai account. This token is used to authenticate API requests.
`client-secret`	The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.
`client-token`	The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.
`host`	The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

Option	Description
`type`	The type of DNS provider that is being added. For DNSimple DNS, the value must be `dnsimple`.
`name`	The name used to represent the DNS provider in SCM.
`access-token`	The access token generated from your DNSimple account. This token is used to authenticate API requests.
`account-id`	The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

Option	Description
`type`	The type of DNS provider that is being added. For OVHcloud, the value must be `ovh`.
`name`	The name used to represent the DNS provider in SCM.
`endpoint`	The OVH region ID indicating where your services are hosted. Some examples of OVHcloud region IDs include `ovh-eu`, `ovh-ca`, and `ovh-us`.
`app-key`	The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.
`app-secret`	The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.
`consumer-key`	The Consumer Key (CK) obtained after authenticating your application with OVHcloud’s API using your Application Key and Application Secret. This key grants your application permission to make API requests on behalf of a user’s account.

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

Option	Description
`type`	The type of DNS provider that is being added. For Bind, the value must be `bind`.
`name`	The name used to represent the DNS provider in SCM.
`host`	The hostname or IP address of the Bind server.
`key-file`	The path to the Transaction SIGnature(TSIG) key file used for authentication.
`port`	(Optional) The port number on which the Bind server is listening (default `53`).

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

Option	Description
`type`	The type of DNS provider that is being added. For Infoblox, the value must be `infoblox`.
`name`	The name used to represent the DNS provider in SCM.
`host`	The Infoblox server host name (FQDN or IP address).
`username`	The Infoblox account name used by the connector to authenticate to the API.
`password`	The Infoblox account password.
`dns-view`	(Optional) The Infoblox DNS View where records are managed. (default `External`).
`port`	(Optional) The port number (default `443`).
`version`	(optional) The Infoblox API version to use for requests..

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

Option	Description
`type`	The type of DNS provider that is being added. For Google Cloud, the value must be `google`.
`name`	The name used to represent the DNS provider in SCM.
`project`	The Google Cloud Project ID.
`cred-file`	The path to the Google Cloud credentials JSON file.

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

Option	Description
`type`	The type of DNS provider that is being added. For Cloudflare, the value must be `cloudflare`.
`name`	The name used to represent the DNS provider in SCM.
`token`	The authentication token specific to your Cloudflare user or account. This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

Option	Description
`type`	The type of DNS provider that is being added. For Amazon Route 53, the value must be `route53`.
`name`	The name used to represent the DNS provider in SCM.
`access-key-id`	The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.
`region`	The AWS region where your Route 53 resources are located. Some examples of AWS region IDs include `us-east-1`, `eu-west-1`, and so on.
`secret-key`	The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.
`session-token`	(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

Option	Description
`type`	The type of DNS provider that is being added. For Azure DNS, the value must be `azure`.
`name`	The name used to represent the DNS provider in SCM.
`resource-group`	The name of the Azure resource group that contains your DNS zone.
`subscription`	The Azure subscription ID associated with your account. This identifies your subscription within Azure.
`tenant-id`	The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.
`client-id`	The client ID of the Microsoft Entra application. This is used for authentication.
`client-secret`	The client secret associated with the Microsoft Entra application. This is used for authentication.

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

Option	Description
`type`	The type of DNS provider that is being added. For GoDaddy DNS, the value must be `godaddy`.
`name`	The name used to represent the DNS provider in SCM.
`api-key`	The API key generated from your GoDaddy account. This key is used to authenticate API requests.
`api-secret`	The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

Option	Description
`type`	The type of DNS provider that is being added. For Akamai Edge DNS, the value must be `akamai`.
`name`	The name used to represent the DNS provider in SCM.
`access-token`	The access token generated from your Akamai account. This token is used to authenticate API requests.
`client-secret`	The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.
`client-token`	The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.
`host`	The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

Option	Description
`type`	The type of DNS provider that is being added. For DNSimple DNS, the value must be `dnsimple`.
`name`	The name used to represent the DNS provider in SCM.
`access-token`	The access token generated from your DNSimple account. This token is used to authenticate API requests.
`account-id`	The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Cloudflare, the value must be cloudflare.

name

The name used to represent the DNS provider in SCM.

token

The authentication token specific to your Cloudflare user or account.

This token is required to authorize the DNS connector to interact with Cloudflare’s API on behalf of your account.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Amazon Route 53, the value must be route53.

name

The name used to represent the DNS provider in SCM.

access-key-id

The AWS access key ID generated for your AWS account. This key is used to authenticate API requests.

region

The AWS region where your Route 53 resources are located.

Some examples of AWS region IDs include us-east-1, eu-west-1, and so on.

secret-key

The AWS secret access key generated for your AWS account. This key, along with the access key ID, is used to sign API requests.

session-token

(Optional) The session token for temporary security credentials. This is included if you are using temporary credentials from AWS STS (Security Token Service).

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Azure DNS, the value must be azure.

name

The name used to represent the DNS provider in SCM.

resource-group

The name of the Azure resource group that contains your DNS zone.

subscription

The Azure subscription ID associated with your account. This identifies your subscription within Azure.

tenant-id

The Microsoft Entra ID (formerly Azure Active Directory) tenant ID.

client-id

The client ID of the Microsoft Entra application. This is used for authentication.

client-secret

The client secret associated with the Microsoft Entra application. This is used for authentication.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For GoDaddy DNS, the value must be godaddy.

name

The name used to represent the DNS provider in SCM.

api-key

The API key generated from your GoDaddy account. This key is used to authenticate API requests.

api-secret

The API secret associated with your GoDaddy API key. This secret, along with the API key, is used to sign API requests.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Akamai Edge DNS, the value must be akamai.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your Akamai account. This token is used to authenticate API requests.

client-secret

The client secret associated with your Akamai API client. This secret, along with the client token, is used to sign API requests.

client-token

The client token generated from your Akamai account. This token, along with the client secret, is used to authenticate API requests.

host

The host URL for the Akamai API endpoint. This specifies the server to which API requests are sent.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For DNSimple DNS, the value must be dnsimple.

name

The name used to represent the DNS provider in SCM.

access-token

The access token generated from your DNSimple account. This token is used to authenticate API requests.

account-id

The account ID associated with your DNSimple account. This ID is used to specify which account the API requests should be applied to.

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For OVHcloud, the value must be ovh.

name

The name used to represent the DNS provider in SCM.

endpoint

The OVH region ID indicating where your services are hosted.

Some examples of OVHcloud region IDs include ovh-eu, ovh-ca, and ovh-us.

app-key

The Application Key (AK) provided by OVHcloud when you register your application. This key is used to identify your application in API requests.

app-secret

The Application Secret (AS) provided by OVHcloud alongside the Application Key. This secret, along with the application key, is used to sign API requests.

consumer-key

In a command prompt window, navigate to the DNS connector install location.

Add the Bind DNS provider.

sectigo-dcs.exe provider add -name "<yourProviderName>" -type bind -host <yourHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Bind, the value must be bind.

name

The name used to represent the DNS provider in SCM.

host

The hostname or IP address of the Bind server.

key-file

The path to the Transaction SIGnature(TSIG) key file used for authentication.

port

(Optional) The port number on which the Bind server is listening (default 53).

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Infoblox DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Infoblox, the value must be infoblox.

name

The name used to represent the DNS provider in SCM.

host

The Infoblox server host name (FQDN or IP address).

username

The Infoblox account name used by the connector to authenticate to the API.

password

The Infoblox account password.

dns-view

(Optional) The Infoblox DNS View where records are managed. (default External).

port

(Optional) The port number (default 443).

version

(optional) The Infoblox API version to use for requests..

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

In a command prompt window, navigate to the DNS connector install location.

Add the Google Cloud DNS provider.

sectigo-dcs.exe provider add -name <yourProviderName> -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

The command options are outlined in the following table.

Option Description

type

The type of DNS provider that is being added.

For Google Cloud, the value must be google.

name

The name used to represent the DNS provider in SCM.

project

The Google Cloud Project ID.

cred-file

The path to the Google Cloud credentials JSON file.

Verify the provider is added.

sectigo-dcs.exe debug provider ping -name "<yourProviderName>"

You can view additional CLI commands with the help command.

sectigo-dcs provider help

Managing DNS providers

Modify a DNS provider

Cloudflare
Amazon Route 53
Azure DNS
GoDaddy DNS
Akamai Edge DNS
DNSimple
OVHcloud
Bind
Infoblox
Google Cloud DNS

In a command prompt window, navigate to the DNS connector install location.

Modify the Cloudflare provider.

sectigo-dcs.exe provider modify -type cloudflare -name "<yourProviderName>" -token "<yourCloudflareToken>"

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Amazon Route 53 provider.

sectigo-dcs.exe provider modify -type route53 -name "<yourProviderName>" -access-key-id "<yourAccessKeyID>" -region "<yourAWSRegion>" -secret-key "<yourSecretKey>" -session-token "<yourSessionToken>"

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Azure DNS provider.

sectigo-dcs.exe provider modify -type azure -name "<yourProviderName>" -resource-group "<yourResourceGroupName>" -subscription "<yourSubscriptionID>" -tenant-id "<yourTenantID>" -client-id "<yourClientID>" -client-secret "<yourClientSecret>"

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the GoDaddy DNS provider.

sectigo-dcs.exe provider modify -type godaddy -name "<yourProviderName>" -api-key "<yourAPIKey>" -api-secret "<yourAPISecret>"

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Akamai Edge DNS provider.

sectigo-dcs.exe provider modify -type akamai -name "<yourProviderName>" -access-token "<yourAccessToken>" -client-secret "<yourClientSecret>" -client-token "<yourClientToken>" -host "<yourHost>"

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the DNSimple DNS provider.

sectigo-dcs.exe provider modify -type dnsimple -name "<yourProviderName>" -access-token "<yourAccessToken>" -account-id "<yourAccountID>"

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the OVHcloud provider.

sectigo-dcs.exe provider modify -type ovh -name "<yourProviderName>" -endpoint <yourOVHendpoint> -app-key "<yourAPIkey>" -app-secret "<yourAppSecret>" -consumer-key "<yourConsumerKey>"

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Bind DNS provider.

sectigo-dcs.exe provider modify -name "<yourProviderName>" -type bind -host <yourBindHost> -key-file <yourPathToKeyFile> -port <yourPortNumber>

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Infoblox DNS provider.

sectigo-dcs.exe provider modify -name <yourProviderName> -type infoblox -host '<yourHost>' -username '<yourUserName>' -password '<yourPassword>' -dns-view '<yourDNSView>' -port <yourPort> -version '<yourVersion>'

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```

In a command prompt window, navigate to the DNS connector install location.

Modify the Google Cloud DNS provider.

sectigo-dcs.exe provider modify -name "<yourProviderName>" -type google -project '<yourProjectId>' -cred-file '<yourCredentialsFilePath>'

Verify the provider’s details.
```
sectigo-dcs.exe provider list
```