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 Allowed Zone

## Endpoint

`/api/allowed/flush`

**Obsolete Path:** `/api/flushAllowedZone`

## Method

GET

## Description

Flushes the Allowed zone to clear all records. This is a bulk operation that removes all entries from the Allowed Zones at once.

## Authentication

Required. A valid session token obtained from the `login` or `createToken` API call.

## Permissions

Allowed: 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.
- This endpoint shares the "Delete" permission level with the `delete` endpoint.
- This is a destructive bulk operation that clears all allowed zones, not just a single domain.

## Edge Cases

- The documentation does not specify behavior when flushing an already-empty Allowed Zones list (likely returns `"ok"` regardless).
- No confirmation mechanism is documented; the flush happens immediately upon request.
- No `node` parameter is documented, so this may not support cluster-aware targeting.
- Unlike `delete`, this does not take a `domain` parameter -- it removes everything.