List each VPC's resolver addresses and whether they answer.
curl --request GET \ --url https://stratum.example.com/v1/projects/example/dns/recursors \ --header 'Authorization: Bearer <token>'The tenant’s view of each VPC’s resolver (; reduced by): the address each available subnet resolves through (its .3, which DHCP hands instances) and whether a client on each subnet got an answer from it in the last 3 minutes. It names no node, no address on the VPC’s internal DNS switch and no placement; operators find those at GET /v1/admin/network/dns/recursors. Optionally narrowed to one VPC.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Query Parameters
Section titled “Query Parameters”Responses
Section titled “Responses”Each VPC’s resolver.
object
A VPC’s resolver, as the tenant sees it: the address each of its subnets resolves through and whether it answers. It names no node, no address on the VPC’s internal DNS switch and no placement; those are the operator’s (GET /v1/admin/network/dns/recursors).
object
The resolver address of each available subnet (its .3, which DHCP hands instances), ordered by subnet id, each with its own verdict.
One subnet’s resolver address (its .3) and whether it answers.
object
The subnet’s .3, which DHCP hands instances as their DNS server.
A client on the subnet resolved a public name through this address within the last 3 minutes.
When a client on the subnet last asked. Absent before the first check.
Why not healthy.
True when every available subnet’s .3 answered a client on that subnet within the last 3 minutes: a probe port on the subnet’s own switch resolved a public name through it (NOERROR or NXDOMAIN pass; SERVFAIL and no answer fail). That is the path an instance’s query takes. False with no subnet, since the resolver then has no address.
Why not healthy, subnet by subnet.
Example
{ "items": [ { "resolverAddresses": [ { "address": "10.0.1.3" } ] } ]}