Hello,
I've identified the root cause of this regression and created a patch to fix it.
Root Cause:
Commit c2d0159 ("Check for explicitly configured proxies before trying
the gateway") inadvertently removed the
DNS-resolving functions v4_explicit_proxy() and v6_explicit_proxy()
from the detection flow. The code now only
checks /etc/hosts statically via v4_explicit_proxy_etc_hosts and
v6_explicit_proxy_etc_hosts, skipping DNS lookups
entirely.
Fix:
I've submitted a pull request with a minimal one-line fix that
restores DNS hostname resolution while preserving
the intent of commit c2d0159:
https://github.com/terceiro/auto-apt-proxy/pull/4
The patch adds back the DNS-resolving functions to the detection
sequence, allowing configurations that rely on
DNS search domains to work again. This is particularly important for
portable laptop setups that need graceful
fallback when away from the home network.
Testing:
I've verified the fix works correctly on Ubuntu 25.10 (v17), restoring
the same behavior as v16.8 on Debian Trixie.
Please let me know if you need any additional information or testing.
Thank you!
- Kirt
