Open jlounds opened 11 months ago
I was able to workaround the issue by changing the .env config line
BIND_DNS_RESOLVER=8.8.8.8,8.8.4.4
to
BIND_DNS_RESOLVER=192.168.0.1
Of course, this won't work when I start using a LAN with a different gateway/DNS IP.
Unfortunately, my workaround stopped working so I'm back to square one. Any help would be greatly appreciated!
I've been having this issue for quite a while. See #1004
I was able to workaround this issue by setting up a VPN (I use ProtonVPN) and running that first. Then all connections to the internet from the devilbox are magically restored.
I think it might have something to do with my ISP using Carrier Grade NAT, but I haven't been able to confirm that. They gave me a dedicated static IP which was supposed to fix that problem, but it didn't make any difference in this problem.
Have you already looked into this bug?
(Optional) Error message
No response
What went wrong?
From within the devilbox container shell, nslookup commands are returning strange 198.18.. addresses:
Expected behaviour
When I run the same commands from MacOS Terminal, I receive the following
How can we reproduce the bug?
Go to devilbox folder and run
And run "nslookup" for any external FQDN.
Host Operating System
Linux
Host Platform (amd64, arm64, other)
amd64
(Linux only) Is SELinux enabled?
Yes, SELinux is enabled
Docker version
Docker version 24.0.6, build ed223bc
Docker Compose version
Docker Compose version v2.23.0-desktop.1
Devilbox version
Devilbox v3.0.0-beta-0.3 (2023-01-02)
Have you removed stopped containers before starting?
Yes
Have you pulled latest Docker images before starting?
Yes
Devilbox start command
docker-compose up
Config: .env file
Config: docker-compose.override.yml
No response
Config: ./check-config.sh
Log: docker-compose logs
(Optional) Additional information
I can work-around the problem by using the EXTRA_HOSTS .env config, but that is very tedious and prone to becoming stale as IP addresses change.
If I enable the setting BIND_LOG_DNS_QUERIES and run "nslookup github.com", the following entry appears in the log