On 25 Nov, 2009, at 01:52, W.C.A. Wijngaards wrote:
* The rule that .local names MUST be sent to mdns(port 5353). I feel
this is a little too strong, there are sites out there that have
set ups
with .local in their unicast DNS. Propose: SHOULD.
I think you may be misreading this.
A statement of "MUST do X" does not imply "MUST NOT do NOT X".
A host implementing Multicast DNS, performing a Multicast DNS query,
MUST send that query to the Multicast DNS port, or it won't work.
There's no "SHOULD" about it. An implementation cannot choose to send
the Multicast DNS query to a different port and expect it to work.
A host implementing Multicast DNS generally implements a variety of
other name resolution mechanisms like standard unicast DNS, NetBIOS,
a local "/etc/hosts" file, etc., and names can be looked up via those
mechanisms too. Indeed, you will find that if you install iTunes on
your PC, even at a site that's set up a private DNS server for
"local", the sky does not fall. What happens is that Windows (and Mac
OS X too) look up dot-local names both ways.
Looking up names more than one way is not as efficient as it could
be, and it might be better if we didn't have to do that, but it does
work.
I will add some text explaining this.
Stuart Cheshire <cheshire(_at_)apple(_dot_)com>
* Wizard Without Portfolio, Apple Inc.
* Internet Architecture Board
* www.stuartcheshire.org
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf