dns.query-log.setTurn query logging on or off
PUT /dns/api/zones/{id}/query-loggingIAM dns:UpdateQueryLoggingChanges state
Takes effect within one nameserver pull; lines arrive about a minute later.
Request syntax
PUT /dns/api/zones/{id}/query-logging
{
"enabled": "boolean"
}Path parameters
idRequiredstring
Constraints: uuid
Request body
enabledRequiredboolean
Log every answered query of the zone
Response
200 with { queryLogging }, the setting now stored. 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:UpdateQueryLogging 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 set id --enabledcurl -X PUT "https://console.platform-development.deutschecloud.app/dns/api/zones/id/query-logging" \
-H "Authorization: EWS-ACCESS-KEY $ACCESS_KEY" \
-H "Content-Type: application/json" \
-d '{"enabled":true}'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_set.