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

# Delete DHCP Scope

## Endpoint

`/api/dhcp/scopes/delete`

Obsolete path: `/api/deleteDhcpScope`

## Method

GET

## Description

Permanently deletes the DHCP scope from the disk. This removes the scope configuration and all associated data. This action cannot be undone.

## Authentication

Required. Token must have **DhcpServer: Delete** permission.

## Parameters

| Name | Type | Required | Conditional | Description |
|------|------|----------|-------------|-------------|
| `token` | string | Yes | No | The session token generated by the `login` or the `createToken` call. |
| `name` | string | Yes | No | The name of the DHCP scope to delete. |

## Response Fields

Empty response object on success.

## Conditional Logic Notes

- None. This is a simple destructive operation.

## Edge Cases

- The documentation states the scope is deleted "from the disk," meaning this is a permanent deletion of the scope's configuration file.
- It is not documented whether the scope must be disabled before deletion, or whether an enabled scope can be deleted directly.
- Existing active leases may become orphaned after deletion; the behavior for clients attempting to renew leases from a deleted scope is not documented.
- The scope must exist; behavior when targeting a nonexistent scope is not documented.