On Sun, 22 Dec 2024 09:42:40 +0700 Max Nikulin <maniku...@gmail.com> wrote:
> On 21/12/2024 10:12, Charles Curley wrote: > > Because of the NATting for the VMs I have defined an alias for the > > cache in bind per the auto-apt-proxy man page. This works as > > expected, even on the non-virtual trixie machine. > > Disclaimer: I have never tried this tool. > > 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. However, I tried setting up a SRV record, but could never get it to work. I did, however, successfully alias apt-proxy: root@cdtest:~# host apt-proxy apt-proxy.localdomain is an alias for issola.localdomain. issola.localdomain has address 192.168.100.12 root@cdtest:~# This works on all machines, including the machine where auto-apt-proxy fails. > > Does this tool use multicast DNS? Is it configured on your trixie > machine and on bookworm ones? The man page for auto-apt-proxy indicates that it will try MDNS, but I have not tried to set it up. > > grep hosts: /etc/nsswitch.conf > 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 root@tiassa:~# As a point of comparison, from one of the bookworm machines (on all of which auto-apt-proxy works): root@hawk:/usr/local/sbin# grep hosts: /etc/nsswitch.conf hosts: files mdns4_minimal [NOTFOUND=return] dns mymachines root@hawk:/usr/local/sbin# Just for the halibut, I took the mdns entry out of tiassa's nsswitch.conf: root@tiassa:~# grep hosts: /etc/nsswitch.conf hosts: files dns root@tiassa:~# and auto-apt-proxy still fails. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
