Recently I made a forum post regarding DNS resolution problems even though DNS resolution and the VPN on the container worked.
Click for the logs (endlessly failing the resolve check and restarting wireguard)
2024-05-07 19:35:57,020 DEBG 'start-script' stdout output:
[debug] Having issues resolving name 'www.google.com'
[debug] Retrying in 5 secs...
[debug] 2 retries left
2024-05-07 19:36:00,906 DEBG 'watchdog-script' stdout output:
[debug] Having issues resolving name 'www.google.com'
[debug] Retrying in 5 secs...
[debug] 1 retries left
2024-05-07 19:36:02,051 DEBG 'start-script' stdout output:
[debug] Having issues resolving name 'www.google.com'
[debug] Retrying in 5 secs...
[debug] 1 retries left
2024-05-07 19:36:05,916 DEBG 'watchdog-script' stdout output:
[info] DNS failure, creating file '/tmp/dnsfailure' to indicate failure...
2024-05-07 19:36:05,935 DEBG 'watchdog-script' stdout output:
[debug] Waiting for iptables chain policies to be in place...
2024-05-07 19:36:05,987 DEBG 'watchdog-script' stdout output:
[debug] iptables chain policies are in place
2024-05-07 19:36:06,021 DEBG 'watchdog-script' stdout output:
[debug] VPN IP is 10.65.180.74
2024-05-07 19:36:07,059 DEBG 'start-script' stdout output:
[info] DNS failure, creating file '/tmp/dnsfailure' to indicate failure...
2024-05-07 19:36:07,080 DEBG 'start-script' stdout output:
[info] Application does not require external IP address, skipping external IP address detection
2024-05-07 19:36:07,091 DEBG 'start-script' stdout output:
[info] WireGuard interface 'up'
2024-05-07 19:36:07,098 DEBG 'start-script' stdout output:
[info] Application does not require port forwarding, skipping incoming port assignment
2024-05-07 19:36:36,034 DEBG 'watchdog-script' stdout output:
[debug] Checking we can resolve name 'www.google.com' to address...
2024-05-07 19:36:36,064 DEBG 'watchdog-script' stdout output:
[debug] Having issues resolving name 'www.google.com'
[debug] Retrying in 5 secs...
[debug] 11 retries left
I found out that the issue was due to the ldns package not being installed. /root/tools.sh uses it (drill) for DNS information. It quietly fails and tells us that the DNS could not be resolved, causing it to constantly restart the (working) wireguard VPN.
Wondering if this is a new issue. I know next to nothing about Arch or container creation.
The current workaround is installing the package, but this may need to be put in the Dockerfile of this project to fix the issue.
Hello,
Recently I made a forum post regarding DNS resolution problems even though DNS resolution and the VPN on the container worked.
Click for the logs (endlessly failing the resolve check and restarting wireguard)
I found out that the issue was due to the
ldns
package not being installed./root/tools.sh
uses it (drill) for DNS information. It quietly fails and tells us that the DNS could not be resolved, causing it to constantly restart the (working) wireguard VPN.Wondering if this is a new issue. I know next to nothing about Arch or container creation. The current workaround is installing the package, but this may need to be put in the Dockerfile of this project to fix the issue.