Skip to content

Nodes

The Nodes page lists the self-hosted nodes enrolled to this profile: name, online or offline, versions, last seen, and how many log batches are waiting for the node.

  1. Click Add a node and give it a name, for example Living room Pi.

  2. Click Create enrolment code. The dashboard shows a one-time code (opdnsenrol_…) and two ready-made commands. The code works once and expires after 15 minutes.

  3. Run one of the commands on the machine. See Enrol a node.

The node shows as pending until it uses the code, then enrolled.

A node is online while its link to opdns is up. It shows offline as soon as the link closes, or when nothing has been heard from it for a while (for example when the link server that held its connection stopped: opdns notices within about 30 seconds). An offline node keeps resolving with its last profile and lists; see Offline behaviour.

When a node has been offline for 10 minutes (the operator’s setting), the owners of the account get an email naming the node, its profile and when it was last seen, with a link to this page. A second email says when it is back online and that the logs queued in the cloud meanwhile are being delivered. There is at most one such pair per node every 6 hours, so a flapping connection does not flood your inbox.

The alerts are on by default. Turn them off on the Account page, under Preferences. Only owners receive them, and cloud profiles without a node never trigger them.

Revoke refuses the node’s token from then on and closes its link within seconds. The node stops reconnecting and keeps resolving with the last profile it had, as an unmanaged node. To use it again, create a new code and enrol it again.

opdns-node unenrol on the node does the same from the other side: it revokes the node in the cloud with its own token, then removes the token locally. If the node cannot reach opdns at that moment it unenrols locally anyway and asks you to revoke it here. See Unenrol.

To keep this profile’s logs at home, set the log destination to My self-hosted node or Both. See Logs on your node.