rsp2k/coredns
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
coredns/zones/acrazy.org.zone

59 lines
3 KiB
Dns
Raw Normal View History

Retire prepare-zones.sh pipeline; zones/ is now the served form Big migration: the source/prepared split is gone. Each zones/*.zone is now an RFC-compliant zone file that CoreDNS reads directly. Editing a record is just edit + bump SOA + commit. CoreDNS auto-reloads within 30s; HE pulls on its own 300s SOA-refresh cycle. Why: groundwork for the coredns-rfc2136 plugin to edit zones in place without juggling a source/prepared transformation step. Also reduces the mental model from "edit source, run prep, push" to just "edit". Changes: - zones/*.zone: 84 files migrated from Vultr-export form to RFC-compliant form (SOA injected, Vultr NS replaced with HE NS, CNAME/MX/NS rdata dot-terminated, apex lines get explicit @ prefix). Diff is mechanical and byte-count is unchanged (~340K) -- pure formatting promotion. - docker-compose.yml: bind ./zones:/zones:ro (was ./zones-prepared) - Makefile: dropped 'prep' target. 'reload' is now a no-op explainer. 'tls-up' no longer depends on prep. 'clean' no longer wipes prepared. - scripts/prepare-zones.sh moved to scripts/archive/ (kept for reference). - .gitignore: updated comment for zones-prepared/ (now legacy). NOT in this commit (follow-ups): - CLAUDE.md updates documenting the new workflow. - scripts/bump-serials.sh helper for manual-edit SOA bumping. - coredns-rfc2136 plugin refactor (Phase 2b in the plan).
2026-05-21 11:14:42 -06:00
; Auto-prepared by scripts/prepare-zones.sh on 2026-05-21T11:12:50-06:00
; Source: zones/acrazy.org.zone
coredns: docker compose stack with Vultr zone import - Auto plugin loads zones-prepared/*.zone (regex zone-name extraction) - scripts/prepare-zones.sh transforms raw Vultr exports: * synthesizes SOA (omitted by Vultr; CoreDNS requires it) * prepends @ to leading-TAB apex lines to disambiguate owner inheritance * dot-terminates NS/MX/CNAME rdata so $ORIGIN doesn't double-suffix - DNS_PORT defaults to 1053 (5353=avahi, 53=libvirt dnsmasq on this host) - Forwards non-authoritative queries to 1.1.1.1/1.0.0.1/9.9.9.9 - Makefile targets: prep, up, down, reload, test, logs - 91 zones loaded
2026-05-12 01:51:09 -06:00
$ORIGIN acrazy.org.
$TTL 3600
Retire prepare-zones.sh pipeline; zones/ is now the served form Big migration: the source/prepared split is gone. Each zones/*.zone is now an RFC-compliant zone file that CoreDNS reads directly. Editing a record is just edit + bump SOA + commit. CoreDNS auto-reloads within 30s; HE pulls on its own 300s SOA-refresh cycle. Why: groundwork for the coredns-rfc2136 plugin to edit zones in place without juggling a source/prepared transformation step. Also reduces the mental model from "edit source, run prep, push" to just "edit". Changes: - zones/*.zone: 84 files migrated from Vultr-export form to RFC-compliant form (SOA injected, Vultr NS replaced with HE NS, CNAME/MX/NS rdata dot-terminated, apex lines get explicit @ prefix). Diff is mechanical and byte-count is unchanged (~340K) -- pure formatting promotion. - docker-compose.yml: bind ./zones:/zones:ro (was ./zones-prepared) - Makefile: dropped 'prep' target. 'reload' is now a no-op explainer. 'tls-up' no longer depends on prep. 'clean' no longer wipes prepared. - scripts/prepare-zones.sh moved to scripts/archive/ (kept for reference). - .gitignore: updated comment for zones-prepared/ (now legacy). NOT in this commit (follow-ups): - CLAUDE.md updates documenting the new workflow. - scripts/bump-serials.sh helper for manual-edit SOA bumping. - coredns-rfc2136 plugin refactor (Phase 2b in the plan).
2026-05-21 11:14:42 -06:00
@ 3600 IN SOA ns1.he.net. admin.acrazy.org. (
2026052102 ; serial — bump per change (SERIAL=YYYYMMDDNN make prep)
300 ; refresh (5 min) — slaves poll us this often;
; tightened from 3600 to nudge HE's internal
; puller→anycast replication
120 ; retry (2 min) — kept < refresh per RFC 1912
604800 ; expire (1 week)
60 ; minimum (1 min) — negative-cache TTL on public
; resolvers; shrinks the window when an old
; NXDOMAIN keeps showing after we add a name
)
coredns: docker compose stack with Vultr zone import - Auto plugin loads zones-prepared/*.zone (regex zone-name extraction) - scripts/prepare-zones.sh transforms raw Vultr exports: * synthesizes SOA (omitted by Vultr; CoreDNS requires it) * prepends @ to leading-TAB apex lines to disambiguate owner inheritance * dot-terminates NS/MX/CNAME rdata so $ORIGIN doesn't double-suffix - DNS_PORT defaults to 1053 (5353=avahi, 53=libvirt dnsmasq on this host) - Forwards non-authoritative queries to 1.1.1.1/1.0.0.1/9.9.9.9 - Makefile targets: prep, up, down, reload, test, logs - 91 zones loaded
2026-05-12 01:51:09 -06:00
Retire prepare-zones.sh pipeline; zones/ is now the served form Big migration: the source/prepared split is gone. Each zones/*.zone is now an RFC-compliant zone file that CoreDNS reads directly. Editing a record is just edit + bump SOA + commit. CoreDNS auto-reloads within 30s; HE pulls on its own 300s SOA-refresh cycle. Why: groundwork for the coredns-rfc2136 plugin to edit zones in place without juggling a source/prepared transformation step. Also reduces the mental model from "edit source, run prep, push" to just "edit". Changes: - zones/*.zone: 84 files migrated from Vultr-export form to RFC-compliant form (SOA injected, Vultr NS replaced with HE NS, CNAME/MX/NS rdata dot-terminated, apex lines get explicit @ prefix). Diff is mechanical and byte-count is unchanged (~340K) -- pure formatting promotion. - docker-compose.yml: bind ./zones:/zones:ro (was ./zones-prepared) - Makefile: dropped 'prep' target. 'reload' is now a no-op explainer. 'tls-up' no longer depends on prep. 'clean' no longer wipes prepared. - scripts/prepare-zones.sh moved to scripts/archive/ (kept for reference). - .gitignore: updated comment for zones-prepared/ (now legacy). NOT in this commit (follow-ups): - CLAUDE.md updates documenting the new workflow. - scripts/bump-serials.sh helper for manual-edit SOA bumping. - coredns-rfc2136 plugin refactor (Phase 2b in the plan).
2026-05-21 11:14:42 -06:00
@ 3600 IN NS ns1.he.net.
@ 3600 IN NS ns2.he.net.
@ 3600 IN NS ns3.he.net.
@ 3600 IN NS ns4.he.net.
@ 3600 IN NS ns5.he.net.
@ 300 IN A 74.91.22.234
coredns: docker compose stack with Vultr zone import - Auto plugin loads zones-prepared/*.zone (regex zone-name extraction) - scripts/prepare-zones.sh transforms raw Vultr exports: * synthesizes SOA (omitted by Vultr; CoreDNS requires it) * prepends @ to leading-TAB apex lines to disambiguate owner inheritance * dot-terminates NS/MX/CNAME rdata so $ORIGIN doesn't double-suffix - DNS_PORT defaults to 1053 (5353=avahi, 53=libvirt dnsmasq on this host) - Forwards non-authoritative queries to 1.1.1.1/1.0.0.1/9.9.9.9 - Makefile targets: prep, up, down, reload, test, logs - 91 zones loaded
2026-05-12 01:51:09 -06:00
or 300 IN A 74.91.22.233
Retire prepare-zones.sh pipeline; zones/ is now the served form Big migration: the source/prepared split is gone. Each zones/*.zone is now an RFC-compliant zone file that CoreDNS reads directly. Editing a record is just edit + bump SOA + commit. CoreDNS auto-reloads within 30s; HE pulls on its own 300s SOA-refresh cycle. Why: groundwork for the coredns-rfc2136 plugin to edit zones in place without juggling a source/prepared transformation step. Also reduces the mental model from "edit source, run prep, push" to just "edit". Changes: - zones/*.zone: 84 files migrated from Vultr-export form to RFC-compliant form (SOA injected, Vultr NS replaced with HE NS, CNAME/MX/NS rdata dot-terminated, apex lines get explicit @ prefix). Diff is mechanical and byte-count is unchanged (~340K) -- pure formatting promotion. - docker-compose.yml: bind ./zones:/zones:ro (was ./zones-prepared) - Makefile: dropped 'prep' target. 'reload' is now a no-op explainer. 'tls-up' no longer depends on prep. 'clean' no longer wipes prepared. - scripts/prepare-zones.sh moved to scripts/archive/ (kept for reference). - .gitignore: updated comment for zones-prepared/ (now legacy). NOT in this commit (follow-ups): - CLAUDE.md updates documenting the new workflow. - scripts/bump-serials.sh helper for manual-edit SOA bumping. - coredns-rfc2136 plugin refactor (Phase 2b in the plan).
2026-05-21 11:14:42 -06:00
l 300 IN CNAME rpm-bullet.mer.idahomuellers.net.
*.l 300 IN CNAME rpm-bullet.mer.idahomuellers.net.
zones: repoint 24 records 108.61.229.209 → 108.61.23.129 (docker-1 migration) Bulk swap of the old docker host IP to the new one across 13 zones. docker-1.supported.systems intentionally preserved at the old IP — the hostname stays tied to the old box until decommissioned.
2026-05-20 11:43:44 -06:00
b 300 IN A 108.61.23.129
dootie 300 IN A 108.61.23.129
Retire prepare-zones.sh pipeline; zones/ is now the served form Big migration: the source/prepared split is gone. Each zones/*.zone is now an RFC-compliant zone file that CoreDNS reads directly. Editing a record is just edit + bump SOA + commit. CoreDNS auto-reloads within 30s; HE pulls on its own 300s SOA-refresh cycle. Why: groundwork for the coredns-rfc2136 plugin to edit zones in place without juggling a source/prepared transformation step. Also reduces the mental model from "edit source, run prep, push" to just "edit". Changes: - zones/*.zone: 84 files migrated from Vultr-export form to RFC-compliant form (SOA injected, Vultr NS replaced with HE NS, CNAME/MX/NS rdata dot-terminated, apex lines get explicit @ prefix). Diff is mechanical and byte-count is unchanged (~340K) -- pure formatting promotion. - docker-compose.yml: bind ./zones:/zones:ro (was ./zones-prepared) - Makefile: dropped 'prep' target. 'reload' is now a no-op explainer. 'tls-up' no longer depends on prep. 'clean' no longer wipes prepared. - scripts/prepare-zones.sh moved to scripts/archive/ (kept for reference). - .gitignore: updated comment for zones-prepared/ (now legacy). NOT in this commit (follow-ups): - CLAUDE.md updates documenting the new workflow. - scripts/bump-serials.sh helper for manual-edit SOA bumping. - coredns-rfc2136 plugin refactor (Phase 2b in the plan).
2026-05-21 11:14:42 -06:00
* 300 IN CNAME acrazy.org.
*.dootie 300 IN CNAME dootie.acrazy.org.
@ 300 IN MX 10 acrazy.org.
coredns: docker compose stack with Vultr zone import - Auto plugin loads zones-prepared/*.zone (regex zone-name extraction) - scripts/prepare-zones.sh transforms raw Vultr exports: * synthesizes SOA (omitted by Vultr; CoreDNS requires it) * prepends @ to leading-TAB apex lines to disambiguate owner inheritance * dot-terminates NS/MX/CNAME rdata so $ORIGIN doesn't double-suffix - DNS_PORT defaults to 1053 (5353=avahi, 53=libvirt dnsmasq on this host) - Forwards non-authoritative queries to 1.1.1.1/1.0.0.1/9.9.9.9 - Makefile targets: prep, up, down, reload, test, logs - 91 zones loaded
2026-05-12 01:51:09 -06:00
_acme-challenge 300 IN TXT "eIA2Ii4EA7cfmjVcTUvOrM5nc4nFRRYpjvxtpEYzPG4"
_acme-challenge 300 IN TXT "DQxkmE7D658WT3-MR5xa7x5NW85L0C8Xq80Iv9-ZF60"
_acme-challenge 300 IN TXT "uOz583TEOpuME0AiJgaZYusECS8VDCP55yBuGw9WL58"
_acme-challenge 300 IN TXT "0ZDa-kNYA-D5qM2c2_RwUJppwIVhbfV4kPw_urWCXzU"
_acme-challenge 300 IN TXT "nMa6SYDLhc7zUxoj7HzF-eYj3kesGoG7JLH3WnIB6Os"
_acme-challenge 300 IN TXT "rDK5pFvMHlH4NFc0L4q3g9DpLfBaO39LlXFg7UnFYBs"
_acme-challenge 300 IN TXT "9TYcG6wfz4wuSE6OoYWDP6GeUs7zNaow0YfBHSmZUAM"
_acme-challenge 300 IN TXT "Ogv1O_ccYh_NcA_GZ0c-rnBn1C-2HqBvywZL-GmkZi0"
_acme-challenge 300 IN TXT "gs1ib1BZWPhJnl9P2cHg8DVp4exQzRlWuK5nsojkN8w"
_acme-challenge 300 IN TXT "T1vpnm26TqUVmekX10TSuPkoVsh6Npn7Q3SLqfwsd9U"
_acme-challenge 300 IN TXT "tSKgr-3mIycjPBkCH0biEL7bwSOmyLHosWaYBZlDD1I"
_acme-challenge 300 IN TXT "pT2NA1Wy_7IsxvMhsB6RX8Q0v2-gI1asl6L_mWwTCCE"
_acme-challenge 300 IN TXT "2898oFCfWYJEz6ftWLL7qEMh8-eT_uQleSWiVHalEmk"
_acme-challenge 300 IN TXT "mg55APlmRSX2MhRXLsY7E4JjIlQ2rxV5n68dltG7gLs"
_acme-challenge.mc.l 300 IN TXT "iluaJ10DaYv9nLYOtqLJ5QAfdfv9f7N2lGT1rVk7mZg"
_acme-challenge.mc.l 300 IN TXT "BEecbLO_EBYf4F31Vbf_LTQSJuBLBbgcMglQRanJv6U"
_acme-challenge.mc.l 300 IN TXT "vgjdoUmdabr6iWKuA7jGpCFfE9W03qCM0RVLn1nQRWQ"
_acme-challenge.api.l 300 IN TXT "3kFf8Z9fM8dtjRbb-OFcjNfkzfu-DShkMm0hdzxRaOI"
_acme-challenge.l 300 IN TXT "3wseUmaL1PND6qn3HzTnQF_uaegJ-VHI1voFGw5j4Fs"
_acme-challenge.l 300 IN TXT "0HXwA0Ij6K5pVWO6Liv9j3nzvZyiH6HONcgREA2UDaA"
_acme-challenge.l 300 IN TXT "WmE8LR03vR1ua26QK58PxCmfxQ-_369sXIezIr8cNoM"
_acme-challenge.l 300 IN TXT "Ike1gqcB3VI7WwKoH3T8zqbpYSo2qRPrq0iqzB5wmFU"
_acme-challenge.langfuse.dootie 300 IN TXT "1WJ-mHJ2SQuuC5CgxbYY6euwiMZm1dVicfIkeluovTY"
_acme-challenge.dootie.l 300 IN TXT "uW30ozl6AKA_q9FWPlvaxuwbgBJ-TgTsXxA3JFtn0tg"
zones: add explicit CNAME-to-apex for RFC 4592 empty-non-terminals Wildcards in DNS only synthesize for names that don't already exist in the zone tree. A `_acme-challenge.<sub>` TXT record makes <sub> an "empty non-terminal" — exists in the tree (as a parent node) but has no records of its own. Per RFC 4592 §2.2.3, wildcards skip these, so RFC-compliant resolvers (HE, BIND) return NODATA for <sub> even when the zone has `* CNAME @`. Fix: for each <sub> that's an empty non-terminal in a zone with a wildcard, add an explicit `<sub> CNAME @` so the resolution outcome matches what the wildcard would have produced. Zero-knowledge — no need to identify the specific service IP per name. 30 records added across 14 zones: acrazy.org (langfuse.dootie) context.bet (studio) copper-springs.online (docs.butler.dev) demostar.io (cw.cw, doom, meet) home-inspector.store (api, dashboard, mailpit) inspect.pics (admin) log.doctor (app, docs) malloys.us (cp, cp-sandbox, mary) nielsen-inspections.com (calendar, cw, files, v2-calendar) qubeseptic.com (api.dispatch, dispatch, leads, mail.dispatch, rentcache.dispatch) ryanmalloy.com (c4ai) sidejob.pro (api) upc.llc (catalog, minio.or, or, s3) CoreDNS (lenient) was returning the wildcard CNAME for these names anyway; HE (strict RFC-compliant) was returning empty. After this change, both behave identically.
2026-05-18 18:34:51 -06:00
_acme-challenge.langfuse.dootie.l 300 IN TXT "P6tOVfwB8OBbI6AqnIuHXKQc05FjuABhGihUHwzpMOs"
Retire prepare-zones.sh pipeline; zones/ is now the served form Big migration: the source/prepared split is gone. Each zones/*.zone is now an RFC-compliant zone file that CoreDNS reads directly. Editing a record is just edit + bump SOA + commit. CoreDNS auto-reloads within 30s; HE pulls on its own 300s SOA-refresh cycle. Why: groundwork for the coredns-rfc2136 plugin to edit zones in place without juggling a source/prepared transformation step. Also reduces the mental model from "edit source, run prep, push" to just "edit". Changes: - zones/*.zone: 84 files migrated from Vultr-export form to RFC-compliant form (SOA injected, Vultr NS replaced with HE NS, CNAME/MX/NS rdata dot-terminated, apex lines get explicit @ prefix). Diff is mechanical and byte-count is unchanged (~340K) -- pure formatting promotion. - docker-compose.yml: bind ./zones:/zones:ro (was ./zones-prepared) - Makefile: dropped 'prep' target. 'reload' is now a no-op explainer. 'tls-up' no longer depends on prep. 'clean' no longer wipes prepared. - scripts/prepare-zones.sh moved to scripts/archive/ (kept for reference). - .gitignore: updated comment for zones-prepared/ (now legacy). NOT in this commit (follow-ups): - CLAUDE.md updates documenting the new workflow. - scripts/bump-serials.sh helper for manual-edit SOA bumping. - coredns-rfc2136 plugin refactor (Phase 2b in the plan).
2026-05-21 11:14:42 -06:00
langfuse.dootie 300 IN CNAME acrazy.org.
Reference in a new issue Copy permalink