The zones.kind CHECK constraint still only allowed 'forward', 'reverse4'
and 'reverse6', so creating an extended zone hit a constraint failure
and a 500. Rebuilds the zones table with the widened constraint while
preserving row ids so records.zone_id references stay valid.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01V8c76Xr2BycaHHu5N4buqi
An extended zone answers authoritatively only for the records it holds
locally; any name with nothing configured falls through to recursive
resolution instead of a synthesized NXDOMAIN, so a public domain's
records don't need to be duplicated just to override a few of them.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01V8c76Xr2BycaHHu5N4buqi
owenandClaude Sonnet 5