Skip to content

Latest commit

 

History

History
63 lines (45 loc) · 2.19 KB

cr-res-loc-delete.md

File metadata and controls

63 lines (45 loc) · 2.19 KB
copyright lastupdated keywords subcollection
years
2021, 2024
2024-10-25
dns-svcs

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

Deleting custom resolver locations

{: #cr-res-loc-delete}

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

Deleting a resolver location in the UI

{: #ui-delete-res-loc} {: ui}

To delete a resolver location by using the UI, follow these steps:

  1. Select a custom resolver to open the details page.
  2. Select the Resolver locations tab, if not selected already.
  3. Click the overflow menu icon for the location that you want to delete.
  4. Select Delete.

Deleting a resolver location from the CLI

{: #cli-delete-res-loc} {: cli}

To delete a resolver location using the CLI, run the following command:

ibmcloud dns custom-resolver-location-delete RESOLVER_ID LOCATION_ID [-i, --instance INSTANCE] [-f, --force]

Where:

  • RESOLVER_ID is the ID of custom resolver.
  • LOCATION_ID is the ID of the custom resolver location.
  • -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.
  • -f, --force deletes the resolver location without prompting for confirmation.

Deleting a resolver location with the API

{: #api-delete-res-loc} {: api}

To delete a custom resolver location 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.
    • location_id, which is the custom resolver location ID.
    • X-Correlation-ID, which is a string that uniquely identifies a request.
  3. When all variables are initiated, get the details of your custom resolver:

    curl -X DELETE https://api.dns-svcs.cloud.ibm.com/v1/instances/2be5d4a7-78f0-4c62-a957-41dc15342777/custom_resolvers/ddbe7a53-7971-46dc-b021-420335c31562/locations/ bf6b4f83-bf0b-47c2-8bdf-e7fbd92db2c6 -H 'Authorization: Bearer xxxxxx'

    {: codeblock}