<?xml version='1.0'?>

<reference anchor='RFC2517'>

<front>
<title abbrev='Building Directories from DNS'>Building Directories from DNS: Experiences from WWWSeeker</title>
<author initials='R.' surname='Moats' fullname='Ryan Moats'>
<organization>AT&amp;T</organization>
<address>
<postal>
<street>15621 Drexel Circle</street>
<city>Omaha</city>
<region>NE</region>
<code>68135-2358</code>
<country>US</country></postal>
<email>jayhawk@att.com</email></address></author>
<author initials='R.' surname='Huber' fullname='Rick Huber'>
<organization>AT&amp;T</organization>
<address>
<postal>
<street>200 Laurel Avenue South</street>
<street>Room C3-3B30</street>
<city>Middletown</city>
<region>NJ</region>
<code>07748</code>
<country>US</country></postal>
<email>rvh@att.c</email></address></author>
<date month='February' year='1999' />
<abstract>
<t>There has been much discussion and several documents written about
the need for an Internet Directory.
Recently, this discussion has
focused on ways to discover an organization's domain name without
relying on use of DNS as a directory service.
This memo discusses
lessons that were learned during InterNIC Directory and Database
Services' development and operation of WWWSeeker, an application that
finds a web site given information about the name and location of an
organization.
The back end database that drives this application was
built from information obtained from domain registries via WHOIS and
other protocols.
We present this information to help future
implementors avoid some of the blind alleys that we have already
explored.
This work builds on the Netfind system that was created by
Mike Schwartz and his team at the University of Colorado at Boulder.</t></abstract></front>

<seriesInfo name='RFC' value='2517' />
</reference>
