Claude 8d4d731832 Raise the auth.yokogawa.tech pinpoint record, and check for it ... The DC is authoritative for a yokogawa.tech zone holding pinpoint records only, so from inside the VNet every name not in that zone is NXDOMAIN rather than forwarded. ai and influx are in it. auth is not. So an operator on cicore1 resolves ai.yokogawa.tech, reaches Caddy, is redirected to https://auth.yokogawa.tech/?rd=... and cannot resolve it. The assistant is reachable and cannot be signed into. Nothing caught this because influx is the only other pinpointed hostname and LAN traffic to it uses the bypassed API paths, which never touch the portal - ai.yokogawa.tech is the first thing here a LAN client must interactively sign in to. verify.sh now resolves auth.yokogawa.tech alongside the hostnames that redirect to it, and fails rather than shrugging when it is missing. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>		2026-08-27 15:13:49 +10:00
..
deploy.sh	Serve the operator page and /ask from one origin	2026-08-27 14:48:22 +10:00
verify.sh	Raise the auth.yokogawa.tech pinpoint record, and check for it	2026-08-27 15:13:49 +10:00