Archived from groups: microsoft.public.win2000.dns,microsoft.public.windows.inetexplorer.ie6.browser,comp.protocols.tcp-ip.domains (
More info?)
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
<blockquote cite="miduUhXnpBmEHA.3968@TK2MSFTNGP11.phx.gbl" type="cite">
<pre wrap="">srv records currently have one drawback - current INET clients such as IE,
ftp, telnet, ping, etc, don't understand them.
</pre>
</blockquote>
Misleading (especially in the case of <code>ping</code>). Better
expressed: The drawbacks are <br>
<ul>
<li>that they are only currently defined for
some, not all, services; <br>
</li>
<li>that for some of those services the
definitions are <em>de facto</em>, not <em>de jure</em>; and <br>
</li>
<li>that some service client applications have yet to catch up.
</li>
</ul>
Three cases in point:<br>
<ul>
<li>Location of LDAP services via <code>SRV</code> resource records
has a <em>de jure</em> definition, and is widely used. It's one of
the foundations of Active Directory, for example. It's also the
cornerstone of the operation of <a
href="http://www.openldap.org./faq/data/cache/393.html">the OpenLDAP
"root" server</a>.<br>
</li>
<li>Location of HTTP services via <code>SRV</code> resource records
has <a href="http://www.anta.net./nic/draft-andrews-http-srv-01.shtml">a
<em>de facto</em>
definition</a>, but none of the major web browser or proxy HTTP server
manufacturers has actually pulled
its finger out and implemented it (despite one of them having had <a
href="http://bugzilla.mozilla.org./show_bug.cgi?id=14328">a work item
to do so</a> for 5 years already, and another of them even <a
href="http://microsoft.com./resources/documentation/windows/2000/server/reskit/en-us/tcpip/part2/tcpch05.mspx">using
<code>_http._tcp</code> resource records as examples in its
documentation</a>).</li>
<li>Location of WHOIS services via <code>SRV</code> resource records
has <a
href="http://ripe.net./ripe/mail-archives/dns-wg/2002/msg00083.html">a
<em>de facto</em> definition</a>, but most WHOIS client
applications still use the older and clunkier methods of either having
long lists of servers hardwired on millions of separate machines
(making modifying or creating a WHOIS server the same nightmare that
there used to be with <code>HOSTS.TXT</code>) or using <code>whois-servers.net.</code>
and thus relying upon a single organization and being unable to cope
with registries associated with non-top-level domains (such as <code>co.uk.</code>,
which the <code>SRV</code> resource record mechanism actually handles
quite happily, in contrast).<br>
</li>
</ul>
</body>
</html>