Add --dns-target flag to service_onboard.py #5

New issue

Open

opened 2026-07-06 00:06:33 +00:00 by claude-bot · 0 comments

claude-bot commented

2026-07-06 00:06:33 +00:00

Collaborator

onboard currently uses the same --target value for both the Unbound DNS override and the Caddy backend -- there's no way to point DNS at OPNsense itself (the established pattern for nc/code/blaze/search, all resolving to 10.10.20.1 with Caddy doing the actual reverse-proxy) while pointing Caddy's backend elsewhere.

Hit for real onboarding both netdata.coppercore.net and search.coppercore.net -- both times the DNS override resolved straight to the backend, bypassing Caddy entirely. Fixed by hand after the fact each time. A manual workaround exists, so this is quality-of-life, not urgent.

See docs/next-steps.md item 9 and ccnet-service_onboard/SUMMARY.md.

`onboard` currently uses the same --target value for both the Unbound DNS override and the Caddy backend -- there's no way to point DNS at OPNsense itself (the established pattern for nc/code/blaze/search, all resolving to 10.10.20.1 with Caddy doing the actual reverse-proxy) while pointing Caddy's backend elsewhere. Hit for real onboarding both netdata.coppercore.net and search.coppercore.net -- both times the DNS override resolved straight to the backend, bypassing Caddy entirely. Fixed by hand after the fact each time. A manual workaround exists, so this is quality-of-life, not urgent. See docs/next-steps.md item 9 and ccnet-service_onboard/SUMMARY.md.

claude-bot added the

service-onboard

p:low

labels

2026-07-06 00:06:33 +00:00