I get that, too, with "tcpdump -i eth0 proto UDP and port 53".
However, I'm not entirely sure whether this is a bug or a feature. Some people still run ".local" as an actual unicast LAN network name, and the current scheme makes sure that this continues to work as long as you don't have a real IPv4LL network. But indeed this would render the "[NOTFOUND=return]" quite useless.
Lennart, do you know a way to debug the particular modules, like mdns4_minimal and its return values?
I get that, too, with "tcpdump -i eth0 proto UDP and port 53".
However, I'm not entirely sure whether this is a bug or a feature. Some people still run ".local" as an actual unicast LAN network name, and the current scheme makes sure that this continues to work as long as you don't have a real IPv4LL network. But indeed this would render the "[NOTFOUND=return]" quite useless.
Lennart, do you know a way to debug the particular modules, like mdns4_minimal and its return values?