Description
Avahi version
avahi-daemon 0.8
Distribution
Debian 12.9
Describe the bug
The command avahi-resolve -a 192.168.1.42 to discover the hostname of the client omv in my network returns omv.fritz.box instead of omv.local:
root@pve:~# avahi-resolve -4a 192.168.1.42
192.168.1.42 omv.fritz.box
Allthough, the hostname omv.local can be resolved to the correct ip:
root@pve:~# avahi-resolve -4n omv.local
omv.local 192.168.1.42
To Reproduce
Create a home network with a Fritz!Box as a router. Add 2 Linux clients to the network. Install Avahi-daemon on the clients. Try to run avahi-resolve -a IP one any of the clients to resolve the hostname of the other one.
Expected behavior
avahi-resolve -4a 192.168.1.42 returns omv.local
Avahi config files if applicable
I didnt touch avahi config files after installation on any of the clients.
Avahi debug logs if applicable
(Debug logs can be turned on by passing --debug to avahi-daemon)
Additional context
- Fritzboxes are common routers in germany and are appaerently serving as regular DNS in the network
- But, the
/etc/nsswitch.conflooks as follows:
hosts: files mdns4_minimal [NOTFOUND=return] dns
networks: files
which from my understanding means, that the mDNS response from avahi should alsways be the preffered
answer ahaed of the answer of the regular DNS.
When creating an isolated virtual network without a connection to the fritzbox as a gateway, the avahi-resolve -a command works as expected and returns the hostname.local.