Comment 3 for bug 896688

I've just encountered this issue with Ubuntu 16.04 / avahi-daemon 0.6.32~rc+dfsg-1ubuntu2. I have an AirPort Time Capsule, however the problem is the same - pinging Airport-Time-Capsule.local resolves to an incorrect 169.254.x.x IP address. Now interestingly, none of my other devices (Apple or Android) have issues resolving this hostname. More interestingly, I can successfully resolve hostnames of other Apple devices from Ubuntu, just not the Time Capsule. This suggests there is a specific compatibility issues between avahi and the Apple AirPort's mDNS implementations.

I have a pcap of mDNS traffic after the Time Capsule was power-cycled. Is there anything else I can provide to help?