List DNS firewall rule groups.
curl --request GET \ --url 'https://stratum.example.com/v1/projects/example/dns/firewall-rule-groups?limit=100' \ --header 'Authorization: Bearer <token>'Per-VPC DNS Firewall (Slice E,) — the Route 53 Resolver DNS Firewall analog. A rule group is a named set of domain rules (block/allow); associating it with a VPC applies it to that VPC’s recursor.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Query Parameters
Section titled “Query Parameters”Opaque cursor from a previous response’s nextPageToken; omit for the
first page. A token that cannot be parsed is treated as no token, so a
client gets the first page rather than a 400.
Cursor-paginated, ordered name, id. Ordering on
name alone is not a total order, so id is the tiebreaker: without
it a cursor sitting on two same-named rows repeats or skips one.
This endpoint returned every matching row with no limit of any kind until.
Responses
Section titled “Responses”The project’s firewall rule groups.
object
object
True for a platform-curated managed group: owned by the platform, read-only to tenants, associable by any project with its own VPCs.
Human-readable description; set on managed groups to explain the curated list.
The group’s domain rules. Omitted on the managed-list discovery endpoint (see domainCount).
object
FQDN to match (its subtree is included). A trailing dot is added if omitted.
Block sinkholes the domain (NXDOMAIN); alert logs matched queries but resolves normally (monitoring); allow overrides a block/alert for that exact domain.
VPCs this rule group is associated with.
Number of domain rules; set by the managed-list discovery endpoint in lieu of the full domains array.
Example
{ "items": [ { "domains": [ { "action": "block" } ] } ]}