hornet-bind9 0.1.0

Parse, write, and validate BIND9 named.conf configuration files and DNS zone files
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
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84

# `hornet convert`

Convert legacy BIND8/9 keywords to their modern equivalents.

---

## Usage

```
hornet convert [OPTIONS] <FILE>

Arguments:
  <FILE>  Path to named.conf

Options:
      --in-place  Write output back to the source file instead of stdout
  -h, --help      Print help
```

---

## Conversions performed

| Legacy keyword | Modern equivalent |
|---|---|
| `master` (zone type) | `primary` |
| `slave` (zone type) | `secondary` |

---

## Examples

### Preview changes (stdout)

```sh
hornet convert /etc/bind/named.conf
```

The modern-keyword output is printed to stdout; the source file is unchanged.

### Apply in-place

```sh
hornet convert --in-place /etc/bind/named.conf
```

Output:

```
Converted /etc/bind/named.conf to modern keywords
```

### Migrate all configs

```sh
for f in /etc/bind/named.conf.d/*.conf; do
    hornet convert --in-place "$f"
done
```

---

## Exit codes

| Code | Meaning |
|---|---|
| `0` | Conversion succeeded |
| `1` | Parse error |

---

## Notes

- All other formatting (indentation, keyword modernisation) uses the same defaults as `fmt`.
- After converting, run `hornet check` to verify the result is semantically valid.
- The conversion is idempotent — running it on an already-modern config is safe.

---

## Related commands

- [`fmt`](./fmt.md) — Reformat a config file
- [`parse`](./parse.md) — Preview formatted output
- [`check`](./check.md) — Validate after conversion