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

# Flush Blocked Zone

## Endpoint

`/api/blocked/flush`

Obsolete path: `/api/flushBlockedZone`

## Method

GET

## Description

Flushes the Blocked zone to clear all records. This is a destructive operation that removes all entries from the Blocked Zones in one call.

## Authentication

Required. A valid session token generated by the `login` or `createToken` call.

## Permissions

Blocked: Delete

## Parameters

| Name | Type | Required | Conditional | Description |
|------|------|----------|-------------|-------------|
| `token` | string | Yes | No | The session token generated by the `login` or the `createToken` call. |

## Response Fields

| Field | Type | Description |
|-------|------|-------------|
| `status` | string | `"ok"` on success. |

## Conditional Logic Notes

- No conditional parameters. Only `token` is required.
- Uses the same "Blocked: Delete" permission as the individual delete endpoint, but this operation affects all blocked zones at once.

## Edge Cases

- Flushing when the Blocked Zones are already empty: the API docs do not specify behavior, but it likely returns `"ok"` regardless.
- This is a destructive bulk operation with no confirmation prompt -- all blocked zones are removed immediately.
- No `domain` parameter exists; the entire blocked zone set is cleared.
- No `node` parameter is documented, so cluster-aware targeting may not be supported.
- There is no undo mechanism documented; flushed zones would need to be re-added individually or via the import endpoint.