api.temps.sh Unresolved

[alixaxel]

Description

temps join with a tunnel relay fails with:

Joining Temps cluster as 'up'...
Warning: could not read Docker info (Error in the hyper legacy client: client error (Connect)). Registering without a container platform; the agent reports it once the daemon is reachable.
Container platform: unknown (will be reported by the agent)
Using relay mode via https://api.temps.sh...
Generated WireGuard keypair.
Error: error sending request for url (https://api.temps.sh/api/relay/clusters/.../join)

Caused by:
    0: client error (Connect)
    1: dns error
    2: failed to lookup address information: Name or service not known

Steps to reproduce

1. https://temps.sh/docs/multi-node#wireguard-mode

Expected behavior

api.temps.sh should resolve and a tunnel should be created.

Actual behavior

api.temps.sh fails to resolve.

 dig api.temps.sh

; <<>> DiG 9.10.6 <<>> api.temps.sh
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 45449
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;api.temps.sh.                  IN      A

;; AUTHORITY SECTION:
temps.sh.               384     IN      SOA     annalise.ns.cloudflare.com. dns.cloudflare.com. 2413947955 10000 2400 604800 1800

;; Query time: 4 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Sat Sep 05 09:07:33 WEST 2026
;; MSG SIZE  rcvd: 129

Operating System

Linux

Temps version

v0.1.0-beta.56 (2413e4d)

Docker version

No response

Relevant logs

Additional context

No response