I am currently working on Rendezvous extension for KDE (mainly Linux,
also
BSD) with Apple's mDNSResponder as its foundation. Multicast DNS part
is
already working well with one exception: resolving hostnames containing
non-latin1 characters with nss_mdns. Reason: all IDN-aware
applications send
ACE-encoded queries (see RFC 3490) to resolver. It has to decode them
into
UTF-8 before resolving.
Unicast (wide area) DNS-SD is much worse because Posix daemon is
severely
limited compared to MacOSX version:
1) it doesn't read list of unicast DNS servers - because of this whole
uDNS-based service discovery is inactive. Attached patch adds this
functionality - it reads dns-sd.resolv.conf (format matching
resolv.conf)
and sets server list. SIGHUP causes daemon to reread configuration file
(important for GUI-based configurator). Simpler version of this patch
was
posted here earlier, but it haven't got any responses or comments.
Sorry for not responding to your earlier patch. Things are pretty
hectic right now at Apple with Mac OS X Tiger development, so everyone
is really busy. We haven't had time to evaluate your patch yet, but
we'll definitely consider it.
2) it doesn't read list of zones and keys for DynDNS updates. This
seems easy
to fix by just copying (with minor fixes) relevant functions from
MacOSX
daemon.
Yep, as you've noticed, all our work around Wide-Area Rendezvous is
focused on Mac OS X right now, but we fully intend to add support to
Posix and Windows in the near future.
3) how you can set default browsing domains? on MacOSX it is read from
system
configuration. In Posix daemon it probably should be read from config
file.
There's a few ways to discover the default browsing domains, one of
which is using DHCP, and from there, using DNS, or they can be read out
of a config file. All of these methods will be supported by Posix and
Windows soon.
4) IDN problems again. You cannot just send UTF-8 encoded domain names
to DNS
server. It has to be encoded according to RFC 3490.
Yep, this is on our list of things to consider. No decision yet.
I would be grateful for information if and how are you going to fix
these
issues.
We're going to fix them, however, they take a back seat to the core
functionally and to the Mac OS X platform support.
Or if enhancing Posix daemon is not a priority will you accept
patches for it?
Definitely. We're very open to taking patches. Please feel free to
submit patches to the list, and we'll consider each one. I don't think
we've denied a patch yet.
