Discussions

Why the CTRLD service is trying to resolve api.controld.com on itself at startup?

It fail because service is not operationnal at this time until it load the distant toml config

And why it doesn't try the secondary bootstrap ? So how can I change this ?

{"level":"info","time":"2026-01-28T09:00:23Z.948","message":"starting ctrld v1.4.9"}
{"level":"info","time":"2026-01-28T09:00:23Z.959","message":"os: linux 6.6.84+"}
{"level":"info","mode":"cd","time":"2026-01-28T09:00:24Z.533","message":"fetching Controld D configuration from API: vlcmcopp3p"}
{"level":"debug","time":"2026-01-28T09:00:24Z.536","message":"Initialize new OS resolver with default nameservers"}
{"level":"debug","time":"2026-01-28T09:00:24Z.538","message":"resolving "api.controld.com" using bootstrap DNS ["127.0.0.1:53" "192.168.1.1:53" "192.168.1.30:53" "[::1]:53"]"}
{"level":"debug","time":"2026-01-28T09:00:24Z.538","message":"os resolver query for api.controld.com. with nameservers: [127.0.0.1:53 192.168.1.1:53 192.168.1.30:53 [::1]:53] public: []"}
{"level":"error","error":"read udp 127.0.0.1:60786->127.0.0.1:53: i/o timeout\nread udp 192.168.1.3:64445->192.168.1.1:53: i/o timeout\nread udp 192.168.1.3:37204->192.168.1.30:53: i/o timeout\nread udp [::1]:31841->[::1]:53: i/o timeout","time":"2026-01-28T09:00:26Z.543","message":"could not lookup "AAAA" record for domain "api.controld.com""}
{"level":"debug","time":"2026-01-28T09:00:26Z.544","message":"os resolver query for api.controld.com. with nameservers: [127.0.0.1:53 192.168.1.1:53 192.168.1.30:53 [::1]:53] public: []"}
{"level":"error","error":"read udp 127.0.0.1:32675->127.0.0.1:53: i/o timeout\nread udp 192.168.1.3:32536->192.168.1.30:53: i/o timeout\nread udp [::1]:62691->[::1]:53: i/o timeout\nread udp 192.168.1.3:37344->192.168.1.1:53: i/o timeout","time":"2026-01-28T09:00:28Z.544","message":"could not lookup "A" record for domain "api.controld.com""}
{"level":"warn","time":"2026-01-28T09:00:28Z.545","message":"No IPs found for api.controld.com, use direct IPs: [147.185.34.1 2606:1a40:3::1]"}
{"level":"debug","time":"2026-01-28T09:00:28Z.545","message":"dialing to 147.185.34.1:443"}
{"level":"debug","time":"2026-01-28T09:00:29Z.124","message":"connected to 147.185.34.1:443"}
{"level":"info","mode":"cd","time":"2026-01-28T09:00:29Z.715","message":"generating ctrld config from Control-D configuration"}
{"level":"info","mode":"cd","time":"2026-01-28T09:00:29Z.715","message":"using defined custom config of Control-D resolver"}
{"level":"info","time":"2026-01-28T09:00:29Z.727","message":"writing config file to: /etc/controld/ctrld.toml"}
{"level":"debug","time":"2026-01-28T09:00:29Z.729","message":"control server started: /var/run/ctrld_control.sock"}