Why the Registered QCTNH Host Must Resolve to a Public IP Address

The QuantaCade Task Nudge service only registers public Joomla targets. The hostname must resolve to publicly routable IP address information so the service cannot be pointed at private/internal infrastructure.

Validation

During registration the central service resolves the submitted origin/endpoint host. DNS results are checked and non-public/private/reserved destinations are rejected. The implementation can fall back to host-address resolution if full DNS-record APIs are unavailable.

What this means

• A normal public production/staging hostname can be eligible.
• A localhost name or private LAN-only address cannot be registered.
• Split-DNS setups must still resolve publicly in a safe way from the service side.
• Changing DNS to a private/reserved destination can make later validation/wake-ups fail.

Why this is a security feature

Without public-IP restrictions, a remote wake-up service could be abused to probe internal networks or cloud metadata/private services. QCTNH intentionally limits the worker to the registered public Joomla site.

Secrets and diagnostics

When troubleshooting Why the Registered QCTNH Host Must Resolve to a Public IP Address, prefer status codes, readiness states, hashes/“matches” indicators, and sanitized activity messages over copying raw secrets. The Joomla WebCron key and QCTNH service credential are operational credentials, not ordinary configuration text for screenshots or public discussion.

If compromise is suspected, rotate the WebCron key and resynchronize rather than trying to keep an exposed credential active.

Community Discussion

Want to compare scheduler workflows, share practical tips, or discuss how you use this QCTNH feature? Visit the QC Task Nudge & Health Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.