technitium 0.4.0

Typed async Rust client for the Technitium DNS Server API
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48

# Delete All Logs

## Endpoint

`/api/logs/deleteAll`

**Obsolete Path:** `/api/deleteAllLogs`

## Method

GET

## Description

Permanently deletes **all** log files from the DNS server's disk in a single operation.

## Authentication

Required. A valid session `token` from `login` or `createToken`.

**Permission:** Logs: Delete

## Parameters

| Name | Type | Required | Conditional | Description |
|------|------|----------|-------------|-------------|
| `token` | string | Yes | No | Session token generated by `login` or `createToken`. |
| `node` | string | No | No | The node domain name to target. Only usable when Clustering is initialized. When unspecified, the current node is used. |

## Response Fields

| Field | Type | Description |
|-------|------|-------------|
| `status` | string | `"ok"` on success. |
| `response` | object | Empty object `{}` on success. |

## Conditional Logic Notes

- The `node` parameter is only meaningful when Clustering is initialized.
- This is a **destructive bulk operation** -- all log files on the targeted node are permanently deleted.
- No confirmation or undo mechanism exists.

## Edge Cases

- Calling this endpoint when no log files exist is not explicitly documented; likely returns `"ok"` with an empty response object.
- Unlike `log_delete`, this endpoint requires no file identifier -- it unconditionally removes everything.
- There is no way to selectively delete a range of logs; use the single Delete Log endpoint (`/api/logs/delete`) for targeted deletion.
- The response provides no indication of how many files were deleted or their identifiers.