Skip to content

Latest commit

 

History

History
82 lines (58 loc) · 2.95 KB

cr-update.md

File metadata and controls

82 lines (58 loc) · 2.95 KB
copyright lastupdated keywords subcollection
years
2021, 2025
2025-02-04
dns-svcs

{{site.data.keyword.attribute-definition-list}}

Updating a custom resolver

{: #update-cr}

You can update custom resolvers in {{site.data.keyword.dns_full}} by using the UI, CLI, or API. {: shortdesc}

Updating a custom resolver in the UI

{: #ui-update-cr} {: ui}

You can update your custom resolver name, description, and profile, and toggle to change enablement status or allow disruptive updates in the details view in the UI.

To edit the name, description or profile of the custom resolver, click Edit to see the edit view. Click Save to commit the changes, or cancel.

To enable or disable the custom resolver, toggle the Enablement switch.

To enable or disable the allow disruptive updates to custom resolver, toggle the Enablement switch.

Update a custom resolver from the CLI

{: #cli-update-cr} {: cli}

To update a custom resolver using the CLI, run the following command:

ibmcloud dns custom-resolver-update RESOLVER_ID [--name NAME] [--enabled true|false] [--description DESCRIPTION] [--profile essential|advance|premier] [--allow_disruptive_updates true|false] [-i, --instance INSTANCE] [--output FORMAT]

Where:

  • RESOLVER_ID is the ID of custom resolver.
  • -n, --name is the name of the custom resolver.
  • -d, --description is the descriptive text of the custom resolver.
  • --enabled determines whether to enable the custom resolver.
  • --profile is the profile name of custom resolver. Valid values: "essential", "advanced", "premier".
  • --allow_disruptive_updates determines weather disruptive update is allowed for the custom resolver.
  • -i, --instance is the instance name or ID. If this is not set, the context instance specified by dns instance-target INSTANCE is used instead.
  • --output specifies output format. Currently, JSON is the only supported format.

Update a custom resolver with the API

{: #api-update-cr} {: api}

To update a custom resolver using the API, follow these steps:

  1. Set up your API environment with the correct variables.

  2. Store the following values in variables to be used in the API command:

    • instance_id, which is the unique identifier of a service instance.
    • resolver_id, which is the unique identifier of a custom resolver.
    • X-Correlation-ID, which is a string that uniquely identifies a request.

  3. When all variables are initiated, update your custom resolver:

    {
  "name": "my-resolver",
  "description": "custom resolver",
  "enabled": false,
  "profile": "essential",
  "allow_disruptive_updates": false
}

    {: codeblock}

Next steps

{: #next-steps-update-cr}