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

# `hornet zone`

Parse a DNS zone file and print the re-formatted output to stdout.

**Alias:** `hornet z`

---

## Usage

```
hornet zone [OPTIONS] <FILE>

Arguments:
  <FILE>  Path to zone file

Options:
  -i, --indent <N>  Indent size in spaces [default: 4]
  -h, --help        Print help
```

---

## Examples

```sh
# Parse and pretty-print a zone file
hornet zone /etc/bind/zones/example.com.db

# Use 2-space indent
hornet zone --indent 2 /etc/bind/zones/example.com.db

# Redirect to a file
hornet zone /etc/bind/zones/example.com.db > /tmp/example.com.db.formatted
```

---

## Exit codes

| Code | Meaning |
|---|---|
| `0` | Parse succeeded; formatted output written to stdout |
| `1` | Parse failed; error written to stderr |

---

## Notes

- Output is written to **stdout**; errors are written to **stderr**.
- The source file is never modified.
- `$INCLUDE` directives are recorded in the AST but not followed; included files are
  not read or output.

---

## Related commands

- [`parse`](./parse.md) — Parse a `named.conf` instead of a zone file
- [`check-zone`](./check-zone.md) — Validate a zone file for semantic errors