dns.query-log.get

The queries the nameservers answered for the zone, newest first

GET /dns/api/zones/{id}/query-logIAM dns:GetQueryLogRead

One line per query: name, type, rcode, answer count, transport, client network (/24 or /56), DO and ECS flags. Kept seven days. Query counts per zone and rcode are the EWS/DNS Queries metric in monitoring, whether logging is on or not.

Request syntax

GET /dns/api/zones/{id}/query-log

Path parameters

  • idRequired

    string

    Constraints: uuid

Query parameters

  • minutesOptional

    number

    How far back, in minutes: 1 to 10080 (the seven days the log keeps), default 60

    Constraints: integer, 1-10080

  • limitOptional

    number

    At most this many lines, newest first: 1 to 1000, default 200

    Constraints: integer, 1-1000

  • containsOptional

    string

    Only lines containing this text (a name, a type, an rcode, a client network), at most 253 characters

    Constraints: max 253 chars

Response

200 with { queryLogging, lines }: queryLogging is whether logging is on now; lines, newest first, each { at, nameserver, line }. 404 when the organization has no such zone.

A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.

Errors

  • 400The request does not pass the schema above. The body is { "error": …, "issues": […] }, one issue per field.
  • 401No credentials, or an access key that is unknown, revoked or expired.
  • 403The caller's policies do not allow dns:GetQueryLog on this resource. The body names the action and the resource, and the refusal is recorded in the audit log.
  • 404The resource does not exist in your organization.

Examples

The required parameters only, with example values. Replace id and the other placeholders with your own.

dcloud dns query-log get id

Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_dns_query-log_get.