From mboxrd@z Thu Jan  1 00:00:00 1970
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: Marc Boschma <marc@boschma.cx>
In-Reply-To: <3e9e24eac4cebcbec3805d16d0081dc5@mule>
Date: Sat,  2 Jan 2016 16:17:24 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <62E80203-4B7F-42FF-B75E-93B55D8FBE64@boschma.cx>
References: <383D8F53-3364-420A-93ED-E1034CB0C258@quintile.net>
	<E4A21AAA-FE61-4FE5-B3F2-E4CD500526DE@boschma.cx>
	<3e9e24eac4cebcbec3805d16d0081dc5@mule>
To: erik quanstrom <quanstro@quanstro.net>
Cc: 9fans@9fans.net
Subject: Re: [9fans] bonjour mDNS?
Topicbox-Message-UUID: 7d157318-ead9-11e9-9d60-3106f5b1d025

Still getting my head around Plan9 but wouldn=E2=80=99t mounting the =
unicast and multicast DNS file servers over the top of each other work? =
(I assume the order of the mount (bind) would lead to resolution =
order=E2=80=A6 but maybe no unified responses.

Marc

> On 2 Jan 2016, at 2:42 pm, erik quanstrom <quanstro@quanstro.net> =
wrote:
>=20
> On Fri Jan  1 19:32:25 PST 2016, marc@boschma.cx wrote:
>>=20
>>> On 2 Jan 2016, at 7:05 am, Steve Simon <steve@quintile.net> wrote:
>>> anyone done any work to implement mDNS / bonjour on plan9?
>>>=20
>>=20
>> No, but I have an interest; just starting out with Plan9 :)
>>=20
>>> my rough plan is to write a file server which generates =
/lib/ndb/mdns
>>> which can be included into your /lib/ndb/local.
>>>=20
>>> I fear the biggest hassle is the clash of UDP port use may mean
>>> mDNS must become part of dns(1) rather than a separate file server.
>>>=20
>>=20
>> Shouldn=E2=80=99t dns(1) only bind to unicast UDP port and thus mDNS =
could bind to the multicast UDP port?
>>=20
>> Are you only considering resolution or also publishing services?
>=20
> it would make sense to me to make a dnsudp request file server that =
manages requests, and
> fork (ha!) that task off to it.  this file server would not care if =
it's querying normal dns,
> or mdns.
>=20
> - erik