Skip to content
StratumStratum Docs

List a VPC's DNS resolver rules.

GET
/v1/projects/{projectId}/dns/resolver-rules
Code sample: Shell / cURL
curl --request GET \
  --url 'https://stratum.example.com/v1/projects/example/dns/resolver-rules?vpcId=example' \
  --header 'Authorization: Bearer <token>'

Per-VPC conditional-forwarding rules — the Stratum equivalent of Route 53 Resolver outbound endpoints + rules. Scope to a VPC via the required vpcId query parameter.

Authorizations

Section titled “Authorizations”

Parameters

Section titled “Parameters”

Path Parameters

Section titled “Path Parameters”
projectId
required
string
/^p-[a-z0-9-]+$/

Query Parameters

Section titled “Query Parameters”
vpcId
required
string

Responses

Section titled “Responses”

200

Section titled “200”

The VPC’s resolver rules.

Media typeapplication/json
object
items
required
Array<object>
object
id
required
integer format: int64
vpcId
required
string
domain
required

The FQDN whose queries are forwarded (trailing dot).

string
forwardTo
required

Target resolvers in IP[@port][#sni] form.

Array<string>
recurse
required
boolean
forwardTls
required
boolean

Example generated

{
  "items": [
    {
      "id": 1,
      "vpcId": "example",
      "domain": "example",
      "forwardTo": [
        "example"
      ],
      "recurse": true,
      "forwardTls": true
    }
  ]
}

400

Section titled “400”

Bad request.

Media typeapplication/problem+json
object
type
required
string format: uri
title
required
string
status
required
integer
>= 400 <= 599
detail
string
instance
string format: uri-reference
requestId
required
string
code
required
string
issues

The findings of a rejected IAM policy document (custom and resource policies).

Array<object>

One finding of a rejected IAM policy document. A rejection lists every finding, so the author fixes the document in one round trip.

object
code
required

The finding, e.g. INVALID_DOCUMENT, UNKNOWN_ACTION, ACTION_NOT_APPLICABLE.

string
statement
required

Index of the statement at fault; -1 for the document as a whole.

integer
>= -1
detail
required
string
action

The offending action, where one is at fault (ACTION_NOT_APPLICABLE).

string
errors

Field errors, for codes that carry them: each problem at its field (see FieldError). Documented on the responses that set it, e.g. approveNodeJoin’s INVALID_INPUT and JOIN_APPROVAL_REFUSED. Absent otherwise.

Array<object>

One field’s problem, the stage-2 installer API’s shape. field is the field’s path, message what is wrong with it.

object
field
required

The field’s path, e.g. links[0].interface, disks[1].confirm, mgmt.address or role; empty for the whole request.

string
message
required
string
details

Structured facts about the refusal, for codes that carry them. The shape is fixed per code and documented on the response that answers it, e.g. IMAGE_POOL_MISMATCH (see ImagePoolMismatchDetails) and IMAGE_IN_USE. Absent for codes that carry none.

object
key
additional properties
any

Example 

{
  "issues": [
    {
      "code": "ACTION_NOT_APPLICABLE",
      "action": "compute:CreateVpc"
    }
  ]
}