Skip to content
StratumStratum Docs

Cluster DNS posture — recursor on/off + default resolver policy.

GET
/v1/admin/network/dns-status
Code sample: Shell / cURL
curl --request GET \
  --url https://stratum.example.com/v1/admin/network/dns-status \
  --header 'Authorization: Bearer <token>'

Answers “is the per-VPC DNS recursor on, and what resolver do a subnet’s guests get by default?” from one place instead of grepping CP logs + ovn-nbctl list DHCP_Options. When the recursor is off, subnet DHCP falls back to the configured upstream resolvers rather than the dead .3 VIP; healthy is false only when neither is available. The fallback resolvers are the cluster’s upstream DNS servers, read from the setting at /v1/admin/network/dns/upstream-servers. Install-scope; gates on network:GetDNSStatus.

Authorizations

Section titled “Authorizations”

Responses

Section titled “Responses”

200

Section titled “200”

The cluster DNS posture.

Media typeapplication/json

cluster DNS posture (recursor on/off + default resolver policy).

object
recursorEnabled
required

Config dns.recursor_enabled (default true).

boolean
fallbackDnsServers
required

The cluster’s upstream DNS servers (the upstream-servers setting), advertised to guests when the recursor is off. Empty when there are none.

Array<string>
defaultResolverPolicy
required

What a subnet without a DHCP override advertises in option 6.

string
Allowed values: recursor-vip fallback-upstreams dead-recursor-vip-no-fallback
healthy
required

False only for the dead-VIP posture (guests get a resolver that never answers).

boolean
detail
required

Human-readable explanation of the current posture.

string

Example 

{
  "defaultResolverPolicy": "recursor-vip"
}

403

Section titled “403”

Authenticated but not authorized.

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"
    }
  ]
}

503

Section titled “503”

Upstream temporarily unavailable (driver / scheduler / dependency).

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"
    }
  ]
}