Is this urgent?
None
Host OS
No response
CPU arch
None
VPN service provider
Custom
What are you using to run the container
docker run
What is the version of Gluetun
Running version latest built on 2026-08-07T11:45:47.701Z (commit 7eed6ea) on Linux 6.12.74+deb13+1-amd64 (x86_64)
What's the problem 🤔
It appears that when a DNS query within the container timeout, the domain name leaks to the host in the form *.home.—for example, example.com.home., example.net.home., I'm not sure why, but after spotting numerous NXDOMAIN queries for *.home. in the host logs, I discovered they were originating from the gluetun container.
Share your logs (at least 10 lines)
DEBUG [dns] getting tls connection for request IN A example.com.: renewing dead connection: dialing tcp 1.1.1.1:853: dial tcp 1.1.1.1:853: i/o timeout
DEBUG [dns] getting tls connection for request IN A example.net.: renewing dead connection: dialing tcp 1.1.1.1:853: dial tcp 1.1.1.1:853: i/o timeout
Share your configuration
Is this urgent?
None
Host OS
No response
CPU arch
None
VPN service provider
Custom
What are you using to run the container
docker run
What is the version of Gluetun
Running version latest built on 2026-08-07T11:45:47.701Z (commit 7eed6ea) on Linux 6.12.74+deb13+1-amd64 (x86_64)
What's the problem 🤔
It appears that when a DNS query within the container timeout, the domain name leaks to the host in the form
*.home.—for example,example.com.home.,example.net.home., I'm not sure why, but after spotting numerousNXDOMAINqueries for*.home.in the host logs, I discovered they were originating from the gluetun container.Share your logs (at least 10 lines)
Share your configuration