feat(dns): PiHole answers an explicit LAN name list, not a zone wildcard #157

Merged

jakman85 merged 1 commits from feat/pihole-explicit-lan-names into main

2026-11-09 02:49:40 +00:00

Author	SHA1	Message	Date
jakman85andClaude Opus 5.5	8fe8d5df8a	feat(dns): PiHole answers an explicit LAN name list, not a zone wildcard gate / gate (pull_request) Successful in 1m14s Details gate / conformance (pull_request) Skipped Details Public names are proxied CNAMEs to the Cloudflare Tunnel since PR #156 and work from the LAN, so they should resolve publicly there too. Replace the address=/${BASE_DOMAIN}/ wildcard with explicit entries: the LAN-only names (derived from every controller:none HTTPRoute), gitea/nextcloud (off Cloudflare's 100 MB / 100 s limits), keycloak/auth, and the L4 VIPs. Add L0 check pihole-lan-names, mutation-tested. Correct docs that still described public names as CNAME to wan. and the cloudflared entrypoint comment. Co-Authored-By: Claude Opus 5.5 <[email protected]>	2026-11-08 19:51:49 -06:00

Author

SHA1

Message

Date

jakman85andClaude Opus 5.5

8fe8d5df8a

feat(dns): PiHole answers an explicit LAN name list, not a zone wildcard

gate / gate (pull_request) Successful in 1m14s

Details

gate / conformance (pull_request) Skipped

Details

Public names are proxied CNAMEs to the Cloudflare Tunnel since PR #156 and
work from the LAN, so they should resolve publicly there too. Replace the
address=/${BASE_DOMAIN}/ wildcard with explicit entries: the LAN-only names
(derived from every controller:none HTTPRoute), gitea/nextcloud (off
Cloudflare's 100 MB / 100 s limits), keycloak/auth, and the L4 VIPs.

Add L0 check pihole-lan-names, mutation-tested. Correct docs that still
described public names as CNAME to wan. and the cloudflared entrypoint comment.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

2026-11-08 19:51:49 -06:00