On 23/12/2024 04:30, Charles Curley wrote:
On Sun, 22 Dec 2024 09:42:40 +0700
Max Nikulin wrote:
Have you compared results on machines where it works and where it
does not (with your actual domain)?
getent hosts _apt_proxy._tcp.YOUR.DOMAIN
None of my hosts return anything from this except an error code of two.
The man page says:
2 One or more supplied key could not be found in the database.
If you do not configure _apt_proxy._tcp record then it is expected.
However I am unsure what you tried instead of ".YOUR.DOMIAN" (perhaps
_apt_proxy._tcp is enough to take domain from DNS config) and whether it
matches "apt-proxy" name lookup.
root@cdtest:~# host apt-proxy
apt-proxy.localdomain is an alias for issola.localdomain.
issola.localdomain has address 192.168.100.12
This works on all machines, including the machine where auto-apt-proxy
fails.
It sounds like an auto-apt-proxy bug. I have no idea if it is possible
to increase verbosity of this tool. Otherwise strace or
tcpdump/wireshark are tools to debug what queries apt-auto-proxy sends.
getent hosts apt-proxy
and with domain as in the output of
hostname --fqdn
The man page for auto-apt-proxy indicates that it will try MDNS, but I
have not tried to set it up.
Do you mean that the apt-proxy machine does not advertise itself through
mDNS? At first I read it as mDNS is not configured on clients.
On the trixie machine where auto-apt-proxy works:
root@cdtest:~# grep hosts: /etc/nsswitch.conf
hosts: files dns
root@cdtest:~#
On the trixie machine where it doesn't work:
root@tiassa:~# grep hosts: /etc/nsswitch.conf
hosts: files mdns4_minimal [NOTFOUND=return] dns
you may compare
getent hosts apt-proxy.local
getent hosts _apt_proxy._tcp.local
root@tiassa:~# grep hosts: /etc/nsswitch.conf
hosts: files dns
root@tiassa:~#
and auto-apt-proxy still fails.
Perhaps the tool might call avahi directly.
