Docker container cannot resolve DNS - api.telegram.org and google.com

My Wispbyte server was working normally before, but now the Docker container cannot resolve any external domain. My Node.js Telegram bot fails with: FetchError: request to https://api.telegram.org/bot.../getMe failed, reason: getaddrinfo EAI AGAIN api.telegram.org I tested DNS inside the container: $ getent hosts google.com It waits and then exits with: Exit code: 2 I also tested: $ curl 4 https://api.telegram.org Result: curl: (6) Could not resolve host: api.telegram.org The container's /etc/resolv.conf shows: nameserver 127.0.0.11 options ndots:0 Based on host file: '/etc/resolv.conf' (internal resolver) ExtServers: [1.1.1.1 1.0.0.1] I also tried: $ ping c 3 1.1.1.1 Result: /entrypoint.sh: line 16: /bin/ping: Operation not permitted The server itself starts normally, but external DNS/network access from the container does not work. Wispbyte status page currently shows all nodes operational. I also received this Cloudflare error on the Wispbyte panel: SSL handshake failed Cloudflare is unable to establish an SSL connection to the origin server Error reference number: 525 Cloudflare location: Singapore Please check the Docker network/DNS resolver for my server/container and let me know if there is an infrastructure issue or if the container needs to be migrated/restarted on another node.