Gets a list of all endpoints within a resolver. The collection can be filtered by name or lifecycle state. It can be sorted on creation time or name both in ASC or DESC order. Note that when no lifecycleState query parameter is provided that the collection does not include resolver endpoints in the DELETED lifecycle state to be consistent with other operations of the API.


oci dns resolver-endpoint list [OPTIONS]

Required Parameters

--resolver-id [text]

The OCID of the target resolver.

Optional Parameters


Fetches all pages of results. If you provide this option, then you cannot provide the --limit option.

--from-json [text]

Provide input to this command as a JSON document from a file using the file://path-to/file syntax.

The --generate-full-command-json-input option can be used to generate a sample json file to be used with this command option. The key names are pre-populated and match the command option names (converted to camelCase format, e.g. compartment-id --> compartmentId), while the values of the keys need to be populated by the user before using the sample file as an input to this command. For any command option that accepts multiple values, the value of the key can be a JSON array.

Options can still be provided on the command line. If an option exists in both the JSON document and the command line then the command line specified value will be used.

For examples on usage of this option, please see our "using CLI with advanced JSON options" link:

--lifecycle-state [text]

The state of a resource.

Accepted values are:

--limit [integer]

The maximum number of items to return in a page of the collection.

--name [text]

The name of a resource.

--page [text]

The value of the opc-next-page response header from the previous "List" call.

--page-size [integer]

When fetching results, the number of results to fetch per call. Only valid when used with --all or --limit, and ignored otherwise.

--scope [text]

Specifies to operate only on resources that have a matching DNS scope.

Accepted values are:

--sort-by [text]

The field by which to sort resolver endpoints.

Accepted values are:

name, timeCreated
--sort-order [text]

The order to sort the resources.

Accepted values are: