Ted Faber wrote:
On Tue, Jul 08, 2008 at 12:54:16PM +1000, Mark Andrews wrote:
"hk." is not a syntactically valid hostname (RFC 952).
"hk." is not a syntactically valid mail domain.
Periods at the end are not legal.
RFC 1035 has *nothing* to do with defining what is legal
as a hostname.
By RFC952 standards "hk" is a perfectly fine hostname.
By RFC1035 standards, if you look it or any other DNS name up using the
DNS resolver, that resolver will treat the name as relative unless it
ends with a dot. Arguing that hk is an unreliable hostname if you
look it up as a relative pathname is pretty much the same as arguing
that www.isi.deterlab.net is an unreliable hostname. Both of them are
subject to the search path without that trailing dot.
RFC1035 may recognize the trailing dot, but (for better or worse) many
applications do not recognize it, and some explicitly forbid it.
So far, the only distinction between the two is that hk is short.
I understand the assumption that getting a collision in the search path
with a 2-letter name is higher than getting one with a 20-letter name.
I believe that the 2-letter collisions are no harder to avoid in
principle than the 20-letter ones, and no harder to create should an
admin want to do so (e.g., to create local aliases). I think you
believe that search path collisions for short names are inherently
harder to avoid (and might rule out using the trailing dot notation in
applications to avoid them).
Is that basically what we disagree about?
No. There's more to this than just the possibility of name collisions
caused by the lookup using a search path.
For instance, there are also applications that try to distinguish
between an absolute DNS name and some other kind of name (DNS name
relative to the search path, or a name in /etc/hosts, NetBIOS, NIS, ...)
by checking to see whether the name contains a '.'. So for instance, if
the domain name contains a '.', the "search path" function might be
turned off during name lookup.
This behavior isn't necessarily prescribed in any specification, but
it's a useful heuristic - especially for an application (like email
addresses or URLs) where it's important that domain names be unambiguous
Ietf mailing list