I can understand correctly what is 'whois server', now.
I am sorry for posting messages not associated with RRP.
Tank you for your answers : )
----- Original Message -----
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "'desperado'" <desperado@tt.co.kr>; <rrp@verisign-grs.com>
Sent: Tuesday, May 28, 2002 9:42 PM
Subject: RE: [VGRS-RRP] whois server
> This message has nothing to do with RRP, but I've provided some answers to
> your questions below.
>
> > -----Original Message-----
> > From: desperado [mailto:desperado@tt.co.kr]
> > Sent: Monday, May 27, 2002 5:06 AM
> > To: rrp@verisign-grs.com
> > Subject: [VGRS-RRP] whois server
> >
> >
> > Hello Everyone :)
> >
> > I cant find any protocol which tells about Whois Server.
> > I think, my company (Registrar) must have our own Whois
> > Server which keeps
> > information of our customers, and it will communicate with Registry.
> > Hmm.. do i misunderstand about whois server?
> > following is a copy of email that one of my fellows sent to VeriSign.
> > I hope to get some help here about this... thank you.
>
> Registrar whois servers don't generally talk to the VeriSign registry's
> whois servers when doing lookups - all of the information you need is kept
> in your own databases.
>
> > --------------
> > 1. Whois DB
> > This may sound quiet basic question.
> > However, I need make this clear .
> > When a internet user makes a whois look-up, how the look-up reache to
> > registrar's whois DB?
>
> A command line query using default parameters typically goes to the
> VeriSign-GRS whois server, which responds with inforamtion identifying the
> registrar's whois server. The user then has to issue a second query
> directly to the registrar's server. Registrars also typically provide a
> web-based user interface for direct use.
>
> > Guess 1. the look-up comes to registry's whois DB first and
> > the registry
> > sends a request again to registrar's whois DB for the same look-up?
> > otherwise
> > Guess 2. to both registrar's and registry's DB, the who is search is
> > requested at the same time?
> >
> > So, between registry's whois DB and registrar's one, which
> > has more accurate
> > information about a certain domain?
>
> Both wrong; see above. No referral or automated forwarding takes place.
> The registry's servers maintain the authoritative information about
> delegations, the registrar's servers maintain authoritative contact and
> registrant information.
>
> > 2. How does a registrar send the whois infomaion against
> > receiving whois
> > look-up ?
> > This question is relatied to question 1.
> > About making whois look-up, we are well understood.
> > However, on the contrary, how can we supply the whois
> > informaion for the
> > domains registered us, when someone send whois Look-up.
> > Do you have a specific Protocol or program, so you can
> > automatically be
> > ansered through a packet connection?
>
> The whois protocol is described in RFC 954.
>
> > 3. What information Should we keep and what we don't have to,
> > and how long.
> > Let's say the owner of a.com ( whose registrar is Today and Tomorrow)
> > applies to modify
> > the nameserver and contact e-mail of his. Then, as registrar,
> > do we keep the
> > previous - after
> > information regarding the change as history?
> >
> > For domain transererence, I find Registrar Reference Manual
> > empathy to keep
> > the registrarnt approval for the
> > transfererece for a certain year. Otherwise, I am not clear
> > with your policy
> > regarding these infomtion keeping.
> >
> > Do you have not any other rules regarding information keeping
> > except domain
> > transferene?
>
> I think these questions are all addressed by ICANN's accreditation
> requirements. References are available here:
>
> http://www.icann.org/registrars/accreditation.htm
>
> -Scott-
> ---------
> See http://www.verisign-grs.net/maillist/rrp/
> for message archives and subscription management information.
---------
See http://www.verisign-grs.net/maillist/rrp/
for message archives and subscription management information.
This archive was generated by hypermail 2.1.2 : Wed May 29 2002 - 02:58:04 EDT