Hosting.com - First Name in Hosting

RFC1714 - Page 12


Page Navigation:

1  2  3  4  5  6  7  8  9  10  11  12  13  14  15  16  17  18  19  20  21  22  23  24  25  26  27  28  29  30  31  32  33  34  35  36  37  38  39  40  41  42  43  44  45  46 

Printable Version: RFC1714.PDF

<< Prev. Page     Next Page >>

RFC 1714            Referral Whois Protocol (RWhois)       November 1994


   badref    When a client receives a %referral response that does
             not work, it must report the bad referral to the server
             that issued the referral.  The referral is bad only if
             the referred server does not contain the SOA record for
             the authority area in question. It is not considered a
             bad referral if the server does not have an answer to
             the query, but responds positively to the -soa area
             directive.  This merely means that there is not an
             answer to the query.  When a -badref is sent to the
             referring server; it should log the bad referral so the
             administrator of that server can remove the reference
             if it is no longer correct.  This action should only be
             taken after receiving a negative response to the query
             and the SOA request.

   recurref  When a client receives a referral that results in a
             recursive action, the referring server must be
             informed.  The -recurref directive must be sent
             identifying the recursive loop.  This directive should
             only be sent to the server one level back, even if
             multiple server were involved in the referral.

   update    An RWhois primary server must be aware of its
             secondary servers.  If the data in the primary server
             changes, the primary server may choose to notify the
             secondary servers.  This allows the secondary servers
             to quickly reflect changes in the primary server's data.

   inssec    This action will inform the authority server that the
             server indicated in the argument will be a secondary
             for its authority area.  The server receiving this
             directive must determine if the secondary is
             acceptable.  If it is, the server should be added to
             the update list so that it will be informed if data in
             the authority area changes.

   delsec    This action will inform the server that the server
             indicated in the subsequent arguments will no longer be
             a secondary.  The server receiving this action must
             determine if the server is a secondary and if so,
             remove it from the update list.

   {action=badref|recurref <:>
                action=inssec|delsec|update
                <::>}






Williamson & Kosters                                           [Page 12]


	
<< Prev. Page     Next Page >>