Time and DNS
This page describes the time synchronisation, DNS, certificates and internet access COD needs to run cleanly.
As of: November 2026, COD 3.8.6
Documentation
Time (NTP)
| Where | Requirement | Why |
|---|---|---|
| COD server | required | Without time synchronisation the audit status is "degraded". Schedules and one-time codes (TOTP) depend on the clock |
| Database servers | required | Audit status, matching timestamps |
| Module servers (NAC, Backup, Passkeepr, Ansible, TACACS+) | required | Audit status, backup timestamps, schedules |
| Network devices | recommended | Comparable timestamps in logs and backups |
Use the same time source for all servers. Check time synchronisation on each server:
timedatectl
The output shows "System clock synchronized: yes".
DNS
COD works with IP addresses. Network objects and backup hosts do not need a DNS name. COD creates Zabbix hosts with either an IP address or a DNS name.
COD's own name does matter:
| For | Why |
|---|---|
| HTTPS address in the browser | The login applies to exactly this address |
| Certificate | The certificate is issued for the name |
| Sign-in token | The name is the issuer in the token, and the modules check it |
| Modules on hosts of their own | They reach COD under this name |
| Requirement | Why | Check |
|---|---|---|
| Decide on COD's name before the initial setup | Name, certificate and token belong together | The name resolves to COD's address |
| Forward and reverse records for the COD server and module servers (recommended) | Certificates, readability in logs | Resolution in both directions |
| After changing COD's public address, roll out the Ansible service again | Until the new rollout, the Ansible service fails | A job sent to the Ansible service completes |
Certificates
HTTPS is required for every access to COD. Session cookies are sent over HTTPS only. Without HTTPS, login does not work. The exceptions are the setup wizard, which runs before HTTPS is set up, and a sign-in locally on the COD server. Details under Initial setup.
| Approach | When | Note |
|---|---|---|
| Installation CA | You have no PKI of your own or want a quick start | The setup wizard creates the CA and the certificate |
| Your own certificate | Certificate from your PKI | Enter it under "Backend config", card "TLS". Saving restarts COD for everyone. Without confirmation, COD reverts to the previous setting after 120 seconds |
| Reverse proxy | You already run a proxy in front of your web services | The proxy must pass WebSocket (terminal) and Server-Sent Events (Passkeepr). COD must trust the proxy (setting "trust proxy"). You receive a sample configuration as part of the project. |
Further certificates:
| Peer | What you store |
|---|---|
| Firewall with a certificate from your CA | CA certificate on the firewall asset in COD |
| Directory service over LDAPS | CA certificate in COD's LDAP settings |
Internet access
COD needs internet access for installation and updates. Beyond that, COD only needs the destinations in this table. Whether the interface should be reachable from outside is up to you.
| Destination | Purpose | When | Required |
|---|---|---|---|
extocode package repository (apt.extoco.de) | COD packages | Installation and update, on all hosts | required |
| Ubuntu archives | Operating system and dependencies | Installation and update | required |
| NodeSource | Node.js 24 | Installation and update | required |
| PostgreSQL repository | PostgreSQL 18 or later, only on Ubuntu 22.04 and 24.04 | Installation and update | required on these versions |
| List of vendors for MAC addresses | Client vendors in the "Vendor Dashboard" | once a week | optional. You receive the address as part of the project. |
| Feedback to extocode | Bugs and requests from the feedback module | when a user sends a report | optional |
| Password breach check | Passkeepr checks from the user's browser whether a password appears in known breaches. Only the first five characters of the hash leave the browser | when Passkeepr runs the check | optional |
The servers reach the package repositories directly or through an HTTP proxy. A proxy must not block the weekly vendor list.
For environments without internet access there is an offline bundle that serves as a local package repository. You receive it on request. Ask your partner, or send the request through the helpdesk form.