From owner-freebsd-net@FreeBSD.ORG Sat Aug 26 09:22:37 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5B5CD16A500; Sat, 26 Aug 2006 09:22:37 +0000 (UTC) (envelope-from fli+freebsd-net@shapeshifter.se) Received: from mx1.h3q.net (manticore.shapeshifter.se [212.37.5.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id D603843D53; Sat, 26 Aug 2006 09:22:36 +0000 (GMT) (envelope-from fli+freebsd-net@shapeshifter.se) Received: from localhost (localhost [127.0.0.1]) by mx1.h3q.net (Postfix) with ESMTP id 643691A78D; Sat, 26 Aug 2006 11:22:32 +0200 (CEST) Received: from mx1.h3q.net ([127.0.0.1]) by localhost (mx1.h3q.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 63187-09; Sat, 26 Aug 2006 11:22:31 +0200 (CEST) Received: from [192.168.1.100] (217-208-33-252-o926.tbon.telia.com [217.208.33.252]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.h3q.net (Postfix) with ESMTP id DCB211A72A; Sat, 26 Aug 2006 11:22:30 +0200 (CEST) Message-ID: <44F012D2.1090207@shapeshifter.se> Date: Sat, 26 Aug 2006 11:22:26 +0200 From: Fredrik Lindberg User-Agent: Thunderbird 1.5.0.4 (X11/20060727) MIME-Version: 1.0 To: Pat Lashley References: <72BA6AF827AADB0CFEB845DA@2EEC3F7CCB6B8A97580F632A> <44EE9D66.80105@shapeshifter.se> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at h3q.net Cc: freebsd-net@freebsd.org, Doug Barton Subject: Re: Zeroconfig and Multicast DNS X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Aug 2006 09:22:37 -0000 Pat Lashley wrote: >> > No, I don't think that there's any good reason to restrict mDNS service >> > discovery to .local; when you're using some other domain on the LAN, >> you >> > still want to easily do the dynamic service advertisement, even if >> the A >> > records are being handled by a traditional unicast DNS server and >> static >> > IP allocation. >> >> Well, this would cause an authority conflict if it's on by default as >> anyone on the local network would be able to announce SD records in >> a domain they do not have authority over. > > The normal use of SD requires the ability of non-privileged users to > announce services on the FQDN of the host upon which they are running. > (Think iTunes playlist sharing.) > >> Do do SD updates to an DNS zone you would need to enable dynamic updates >> on that name server, just as the Service Discovery specifications says. > > What makes you think that there even IS a unicast DNS server for the > (sub)domain in question? I would expect anyone using a real domain (as in using a real TLD, and a name registered at a domain registrar) to have a unicast DNS server. Otherwise they have no "right" to use that name, even if it is only in a local network. >> I don't say that we shouldn't support it, but it should not be on by >> default. And it will actually boil down to what the mdns nss module >> allows. > > I agree that it should not be on by default. But there should be one > simple knob in rc.conf to cause service advertisements to be published > for both .local and the host domain. Any thing more complex would > require editing mdns.conf. > Publishing announcements is one thing, what the nss mdns module allows a host to resolve is what will limit its initial usage. Fredrik Lindberg