When incus-os boots and checks for secure boot key updates, the request to images.linuxcontainers.org gets a timeout.
My dns server (pihole) that gets advertised by the routers dhcp is running inside an incus-os instance and that obviously only boots up after incus-os has started.
So I want to set a different dns server for incus-os than the dhcp assigned one:
Is $ incus network edit incusbr0 and then adding dns.nameservers: 9.9.9.9 under config not the correct way? Does that only advertise that dns server to instances that use the incusbr0 network? If so, how can I change the dns server that incus-os uses?
as recommended in their setup docs for systemd-resolved (which works flawlessly on my laptop), but the IncusOS server requests never show up in the logs.
Is it possible the #server-profileid.dns.nextdns.io part is silently ignored/not passed to resolved, and I get name resolution from the generic IPs? How can I verify which nameservers are used by IncusOS?