Web UI: zone naming and reverse zones, ACL suggestions, record form

- New zone dialog: choose Domain or Reverse zone. Reverse zones are
  created from a network and their name is generated; both kinds show the
  exact zone name and flag likely mistakes (addresses or URLs as names,
  host-like names, duplicates in the view, parent/child zones, networks
  off the octet/nibble boundaries) before anything is submitted.
- Record form: clears every field but the type after an add; shows the
  record exactly as it will be stored and warns about unqualified names.
  In reverse zones it takes an address, defaults to PTR, suggests host
  names of A/AAAA records with that address and warns about a second PTR;
  the record list shows addresses.
- Address match lists (options, view match lists, ACL elements) offer the
  existing ACLs, TSIG keys and built-ins as one-click suggestions and
  flag unknown names.
- Server: in reverse zones a record can be named by its address, and a
  PTR target like nas.example.com without the final dot is read as the
  full host name (a bare label is refused). Warnings noticed while parsing
  record data reach the result again.
- Fixes: brand link hover underline, the dashboard's "New zone" link
  opening the dialog twice.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

docs/cli.md

@@ -98,11 +98,17 @@ jarl record update 1234 --ttl default
 jarl record delete adbraun.lol www A                      # every A record of www
 jarl record delete adbraun.lol www A 192.168.1.10         # just this one
 jarl record delete --id 1234 [--ptr]
+
+# reverse zones: name records by address; the host name needs no final dot
+jarl record add 0.10.10.in-addr.arpa 10.10.0.20 PTR nas.adbraun.lol
 ```
 
 Names are relative to the zone (`@` is the apex) unless they end with a
 dot. Data uses zone file syntax, except that TXT/SPF take plain text: Jarl
-adds the quotes and splits long values into 255-byte strings. `--ptr`
+adds the quotes and splits long values into 255-byte strings. In reverse zones the name can be the address
+(`10.10.0.20`), and a PTR target such as `nas.adbraun.lol` is read as the full
+host name (a bare `nas` is refused, since it would mean
+`nas.0.10.10.in-addr.arpa.`). `--ptr`
 keeps the PTR record in the reverse zone in step (when that zone is managed
 by Jarl). Every record type BIND supports can be used. Jarl knows the
 syntax of the common ones and checks them strictly, and the rest are

docs/concepts.md

@@ -147,7 +147,9 @@ RFC 1982 arithmetic.
   resolved against the zone, and `www.example.com` without a final dot in a
   zone `example.com` is caught as the classic `www.example.com.example.com.`
   mistake. Adding an A/AAAA record with `ptr` also maintains the PTR record in
-  the matching reverse zone.
+  the matching reverse zone. In reverse zones a record can be named by its
+  address (`10.10.0.20`), and a PTR target without a final dot is read as
+  the full host name, because a PTR never points into the reverse zone.
 * **Options** are named.conf statements attached to a scope: server
   `options { }`, a view, a zone, or the top level (`logging`, `controls`,
   `statistics-channels`, `include`, ...). The UI and CLI know every BIND 9.20