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

# Delete Allowed Zone

## Endpoint

`/api/allowed/delete`

**Obsolete Path:** `/api/deleteAllowedZone`

## Method

GET

## Description

Deletes a zone from the Allowed Zones. This removes the specified domain from the allow list.

## 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. |
| `domain` | string | Yes | No | The domain name for the zone to be deleted from the Allowed Zones. |

## Response Fields

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

## Conditional Logic Notes

- No conditional parameters. Both `token` and `domain` are always required.
- The API uses the "Delete" permission level, which is shared with the `flush` endpoint.

## Edge Cases

- The documentation does not specify behavior when deleting a domain that does not exist in the Allowed Zones (may return `"ok"` regardless, or may return an error).
- No `node` parameter is documented for this endpoint, so it may not support cluster-aware targeting.
- Deleting a zone removes only that specific domain entry; it does not cascade to child zones or related records.