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
49

# Admin: Resync Cluster

## Endpoint

`/api/admin/cluster/secondary/resync`

## Method

GET

## Description

Allows an admin user to manually trigger a complete configuration resync on the Secondary node. When triggered, the Secondary node will use the Transfer Config call to sync the complete configuration from the Primary node. This call can only be made at the Secondary node.

## Authentication

Required. Token must be provided via the `token` parameter.

## Permissions

Administration: Modify

## Parameters

| Name | Type | Required | Conditional | Description |
|------|------|----------|-------------|-------------|
| `token` | string | Yes | No | The session token generated by the `login` or the `createToken` call. |
| `node` | string | No | No | The node domain name for which the API call is intended. When unspecified, the current node is used. Can only be used when Clustering is initialized. |

## Response Fields

No response body fields beyond the status. Response is simply:

```json
{
    "status": "ok"
}
```

## Conditional Logic Notes

- This call can only be made at a Secondary node.
- Unlike the scheduled automatic sync, this triggers a full (not incremental) configuration resync.
- The resync is performed asynchronously; the API returns immediately and the sync happens in the background.

## Edge Cases

- If the Primary node is unreachable, the resync will fail (silently or with a delayed error).
- This triggers a complete sync, which may be resource-intensive for large configurations.