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.
19 lines
653 B
Dns
19 lines
653 B
Dns
; Zone file for inspect.pics
|
|
; Generated by mcp-vultr
|
|
$ORIGIN inspect.pics.
|
|
$TTL 3600
|
|
|
|
300 IN NS ns1.vultr.com
|
|
300 IN NS ns2.vultr.com
|
|
l 300 IN A 127.0.0.1
|
|
*.l 300 IN A 127.0.0.1
|
|
300 IN A 74.91.22.232
|
|
* 300 IN CNAME inspect.pics
|
|
300 IN MX 10 inspect.pics
|
|
_acme-challenge 300 IN TXT "O76KUDoUq834H7foiWV2VXVO-XWWAx2mGm1Gt3YJtvQ"
|
|
_acme-challenge 300 IN TXT "0QRoK7IMPLfLffpv8aH8afyw6f9ssDb9NPbWJSJ66q8"
|
|
_acme-challenge.admin 300 IN TXT "i5VYntrsr97R142m7Xj7FJR4huFX1KGlQPgnQjHEeTk"
|
|
; Explicit CNAMEs added to fix RFC 4592 empty-non-terminal cases
|
|
; (parent name has _acme-challenge children, so wildcard would skip it)
|
|
admin 300 IN CNAME inspect.pics
|