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

# Block Zone

## Endpoint

`/api/blocked/add`

Obsolete path: `/api/blockZone`

## Method

GET

## Description

Adds a domain name into the Blocked Zones. This creates a new blocked zone entry that will cause the DNS server to block resolution for the specified domain.

## Authentication

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

## Permissions

Blocked: Modify

## 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 added to the blocked list. |

## Response Fields

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

## Conditional Logic Notes

- No conditional parameters. Both `token` and `domain` are always required.
- The `domain` parameter must be a valid domain name.

## Edge Cases

- Adding a domain that is already in the Blocked Zones: the API docs do not specify whether this returns an error or is idempotent (silently succeeds). Likely idempotent based on typical Technitium behavior.
- No `node` parameter is documented for this endpoint, so it may not support cluster-aware targeting (unlike the list and export endpoints).
- The response contains only a status field with no confirmation of which domain was added.