avahi provides incorrect IP address to pulseaudio

[Craig Harding]

Ubuntu 10.04
Packages avahi-daemon 0.6.25-1ubuntu6.2

I'm using an airport express with pulse audio and I believe avahi-daemon is providing/resolving the wrong IP address to pulse audio.

Using the following command, avahi-browse -r _raop._tcp

I get:

+ eth1 IPv4 00254B09A042@Base Station 09a043 AirTunes Remote Audio local
= eth1 IPv4 00254B09A042@Base Station 09a043 AirTunes Remote Audio local
   hostname = [Base-Station-09a043.local]
   address = [169.254.135.173]
   port = [5000]
   txt = ["sf=0x5" "fv=74200.9" "am=AirPort4,107" "vs=101.9" "tp=TCP,UDP" "vn=65537" "pw=false" "ss=16" "sr=44100" "da=true" "sv=false" "et=0,1" "ek=1" "cn=0,1" "ch=2" "txtvers=1"]

where the address (169.254.135.173) is incorrect. It should be a 192.168.1.X address which is already assigned to the APEX from the router using DHCP. I've had to specify the correct IP address to pulseaudio when I manually load the module_raop_sink module in order for it to properly stream music to it.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[IC Raibow (icrbow)]

This is still true for 14.04.

Even pinging it by hostname in a .local zone yields incorrect IP.

[Mike Wild (mikewild)]

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?

[deesnook (deesnook)]

The issue is still around with avahi 0.7+ and an Airport Express (1st Gen) even if pinging the device resolves the Airport-IP correctly. No streaming possible because Pulseaudio tries to use the wrong IP (169... rather than 192...)

[anquieta (anquieta)]

Yes. This issue seems to be limited to Airport devices for me too. While they are quite old now, any chance this incompatibility can be resolved in Avahi? Correct resolution is helpful to access a Time Capsule's network drive. Anything we can do to help debug and test? Thanks.