MDNS/Bonjour port 0 service registration broken on Solaris 11 Express

Question

I'm using Solaris 11 Express on x86-64, and found a pretty bad bug with registering mDNS/Bonjour services. Most service registration works fine, but registering a service that uses port 0 does not work. It claims to work, but the service never gets registered, and can't be browsed for.
It's easy to reproduce: in one window, run
$ dns-sd -B test.tcp
You should see 'Browsing for test.tcp', and no services found.
Then, in another window, run
$ dns-sd -R solaris test.tcp local. 0
to register a test.tcp service on port 0. It seems to succeed, but the first window doesn't show the new service.
Now, kill the 'dns-sd -R' registration process with ctrl-c, and run
$ dns-sd -R solaris test.tcp local. 1
This time, the first window will show the service. Registering on port 1 works fine, but port 0 does not.
Port 0 service registration works fine on every other OS, and many services use port 0 by convention if they aren't advertising an actual service. For example, netatalk can register a device-info.tcp service to mimic a certain Mac model (so your Solaris server shows up with an Xserve icon). This "service" uses port 0, and doesn't work on S11 Express unless the source is changed to a non-zero port.
Can someone test this out on Solaris 11 EA and other versions, to see if it's been fixed or not?
Edited by: 887058 on Sep 22, 2011 11:57 PM

Answer 1

It is registering fine with port 0. You can test by trying to register the same service on another host in the local network
with the same service name and port. You will see the service name automatically renamed.
For example:
root@estrada:~# dns-sd -R solaris test.tcp local. 0
Registering Service solaris._test._tcp.local. port 0
Got a reply for solaris._test._tcp.local.: Name now registered and active
root@testz:~# dns-sd -R solaris test.tcp local. 0
Registering Service solaris._test._tcp.local. port 0
Got a reply for solaris (2)._test._tcp.local.: Name now registered and active
^C
You can also query and see the SRV record for it:
# dns-sd -Q solaris._test._tcp.local. SRV
Timestamp A/R Flags if Name T C Rdata
23:38:58.949 Add 2 2 solaris._test._tcp.local. 33 1 21 bytes: 00 00 00 00 00 00 07 65 73 74 72 61 64 61 05 6C 6F 63 61 6C 00
It appears to me the service is not seen in the service browse call. These port 0 registrations are used to indicate the service
is not available on the host so this could be by design. I have tested the same on Mac OS X 10.6.8 and observe the same
results.
Rishi