Updating a custom resolver in the console

To update your custom resolver name, description, and profile, and toggle to change enablement status or allow disruptive updates in the details view in the console, follow these steps:

1. From your browser, open the IBM Cloud console and log in to your account.
2. Select the Navigation Menu , then click Resource list > Networking > dns-cr-instance.
3. Navigate to the Custom resolver tab.
4. In the Custom resolver table, click the name of the custom resolver that you want to edit.
5. 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.
6. To enable or disable the custom resolver or to enable or disable allowing disruptive updates to the custom resolver, toggle the Enablement switches.

Update a custom resolver from the 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

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
   }