User
[IMPORTANT: You are running as a scheduled cron job. DELIVERY: Your final response will be automatically delivered to the user — do NOT use send_message or try to deliver the output yourself. Just produce your report/output as your final response and the system handles the rest. SILENT: If there is genuinely nothing new to report, respond with exactly "[SILENT]" (nothing else) to suppress delivery. Never combine [SILENT] with content — either report your findings normally, or say [SILENT] and nothing more.]
Run this command and follow the instructions below:
bash /root/.hermes/skills/cf-dyndns.sh 2>&1
- If the output contains "STATUS:NO_CHANGE": Send NOTHING. Output only: NO_REPLY
- If the output contains "ERROR" or a non-zero exit: Send a warning message to all three targets:
1. "telegram:-1003980922525" (Telegram private channel)
2. "discord:1511697499654459422" (Discord private channel)
3. "telegram:1812605657" (this DM)
Message: "⚠️ DynDNS Error: [error output]"
- If the output shows successful updates (lines with "->" or "OK:"): Send an update message to all three targets:
1. "telegram:-1003980922525" (Telegram private channel)
2. "discord:1511697499654459422" (Discord private channel)
3. "telegram:1812605657" (this DM)
Message: "🔄 DynDNS Updated: [relevant output lines]"
- Never send routine "no change" notices.
Assistant
You are running as a scheduled cron job, and you have been given instructions on how to respond to the status and error messages received from the Dyn DNS service.
WhenDynDNS returns:
* STATUS:NS_NO_CHANGE: No changes were made.
* ERROR: The system encountered an issue while updating or syncing. This might be due to a temporary network overload or a large amount of data being updated at once. In this case, you can either report that no change was achieved with the given notification mechanism or send a warning notice.
WhenDynDNS returns:
* STATUS:OK: The system successfully updated and synced Dyn DNS.
* ERROR NOERROR : The dyn DNS command failed due to one of the above reasons and then successfully re-run without causing downtime. You can either report that no change was achieved with the given notification mechanism or send an update notice.
Please refer to the output as you get it provided by cron job, follow proper protocol when notifying and responding for each error condition, and never provide a "no reply" message