chore: pull manual Cloudflare changes into the zone files

[jaspermayone]

Somebody changed DNS in the Cloudflare dashboard instead of opening a pull request. This brings the zone files back in line so that the next deploy does not undo the change.

witcc.dev

Added in Cloudflare

• @
• _dmarc
• _gh-witcodingclub-o
• calendar
• calendar-site
• cf2024-1._domainkey
• resend._domainkey.send
• send.send
• staging-calendar
• str

Removed in Cloudflare

• strings

hackwit.org

Added in Cloudflare

• @
• _dmarc
• cf2024-1._domainkey

Check the removals. A record is listed as removed because it is in the zone file but not in Cloudflare. That usually means somebody deleted it in the dashboard. It can also mean the last deploy failed. Confirm which one it is before you merge.

Before you merge

• Give every record marked TODO owner unknown an owner, in a comment on the same line.
• Check that each change is one the club wants to keep.
• If a change should not have been made, revert it in Cloudflare and close this pull request. It reopens tomorrow if the change is still there.

[github-actions]

octoDNS plan

hackwit.org.

cloudflare

Operation	Name	Type	TTL	Value	Source
Create	octodns-meta	TXT	60	octodns-version=1.22.0; provider=cloudflare; time=2026-09-21T19:50:23.265313+00:00

Summary: Creates=1, Updates=0, Deletes=0, Existing=4, Meta=False

witcc.dev.

cloudflare

Operation	Name	Type	TTL	Value	Source
Create	octodns-meta	TXT	60	octodns-version=1.22.0; provider=cloudflare; time=2026-09-21T19:50:23.265313+00:00

Summary: Creates=1, Updates=0, Deletes=0, Existing=14, Meta=False

---

Planned against main with a read-only Cloudflare token. Only the zone files at the repository root are included. Changes to config/, bin/ or .github/ are not in this plan, so review those by hand.