Date: Thu, 24 Aug 2006 15:21:41 -0700 From: Chuck Swiger <cswiger@mac.com> To: Fredrik Lindberg <fli+freebsd-net@shapeshifter.se> Cc: freebsd-net@freebsd.org Subject: Re: Zeroconfig and Multicast DNS Message-ID: <B70BC65E-A460-4BC8-8363-A5835E65A276@mac.com> In-Reply-To: <44EE23E7.2010800@shapeshifter.se> References: <F77EE4452C54A9609A58CD03@garrett.local> <44EE1E48.6000006@shapeshifter.se> <D2886A30-B6C5-4F53-995B-91B96CD58592@mac.com> <44EE23E7.2010800@shapeshifter.se>
next in thread | previous in thread | raw e-mail | index | archive | help
On Aug 24, 2006, at 3:10 PM, Fredrik Lindberg wrote: >> Queries to 254.169.in-addr.arpa MUST return NXDOMAIN (or RCODE 3, >> to choose a non-BIND specific term). > > We're talking about mDNS here, not DNS. I would argue that because > mDNS is link-local it makes perfect sense to be able to resolve > 254.169.in-addr.arpa using mDNS. True, agreed-- that's in part (b) of what I quoted. The specific part is: "Names that are resolvable only on the local link (such as through use of protocols such as Link Local Multicast Name Resolution [LLMNR]) MUST NOT be used in off-link communication." What this means is that the hostname-to-address mapping for 254.169.in-addr.arpa addresses must be unique per interface. If you have two interfaces which are connected to different LLA subnets, 169.254.1.1 might map to hostnameA on one, and that same IP might be hostnameB on the other. -- -Chuck
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B70BC65E-A460-4BC8-8363-A5835E65A276>