Hydra: dns not resolveing #188

Closed
opened 2026-09-14 09:06:27 +02:00 by ahtlon · 4 comments
Owner


error fetching latest change from git repo at `https://git.dynamicdiscord.de/malobeo/infrastructure.git':
fatal: unable to access 'https://git.dynamicdiscord.de/malobeo/infrastructure.git/': Could not resolve host: git.dynamicdiscord.de
``` error fetching latest change from git repo at `https://git.dynamicdiscord.de/malobeo/infrastructure.git': fatal: unable to access 'https://git.dynamicdiscord.de/malobeo/infrastructure.git/': Could not resolve host: git.dynamicdiscord.de ```
Owner

temporary fix on albert:

ip addr del 192.168.1.115/24 dev eno2
networkctl reload
temporary fix on albert: ```bash ip addr del 192.168.1.115/24 dev eno2 networkctl reload ```
Owner

Even with the networkctl reload the gitea action runner does not resolve:

Error response from daemon: failed to resolve reference "docker.io/library/node:latest": failed to do request: Head "https://registry-1.docker.io/v2/library/node/manifests/latest": dial tcp: lookup registry-1.docker.io: no such host
Even with the `networkctl reload` the gitea action runner does not resolve: ``` Error response from daemon: failed to resolve reference "docker.io/library/node:latest": failed to do request: Head "https://registry-1.docker.io/v2/library/node/manifests/latest": dial tcp: lookup registry-1.docker.io: no such host ```
Owner

Same problem on Fanny. DNS not working. Cause of this autoupdate doesnt work, needs to be done manually.

Same problem on Fanny. DNS not working. Cause of this autoupdate doesnt work, needs to be done manually.
Author
Owner

Dns should be fine again (for now)

Dns should be fine again (for now)
Sign in to join this conversation.
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: malobeo/infrastructure#188