Using DNS SRV records to locate whois servers
draft-sanz-whois-srv-01

Document Type Expired Internet-Draft (individual in gen area)
Last updated 2015-10-14 (latest revision 2004-04-05)
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream WG state (None)
Document shepherd No shepherd assigned
IESG IESG state Expired (IESG: Dead)
Consensus Boilerplate Unknown
Telechat date
Responsible AD Ted Hardie
Send notices to <miguel.sanz@rediris.es>

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-sanz-whois-srv-01.txt

Abstract

Whois servers are used to locate administrative, technical and security contacts for given IP addresses, domain names or other network objects associated with an organisation, e.g. AS numbers. While usually Top Level Domain (TLD) registries run a whois server, there is no generic name for it and it may not even be obvious that the TLD registry's whois server is the right one to ask, since there are TLDs where registration takes place under specialised second level domains (e.g. UK, AT). The Regional Internet Registries (RIR) also provide whois service as part of their coordination task. All this can be solved by central 'master' or 'meta' whois servers, which keep track of all new and changing servers and refer to the DNS registries' or RIRs' whois servers. This document proposes a DNS-based approach which eliminates the need for a central master repository and works down to lower levels in the hierarchy. It is the intent to locate a whois server as close to the target (in terms of hierarchy) as possible, while preserving the opportunity to locate higher level servers for escalation purposes.

Authors

Marcos Sanz (sanz@denic.de)
Gerhard Winkler (gerhard.winkler@univie.ac.at)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)