WO2000001112A1 - Fonction d'attribution de noms decentralisee - Google Patents

Fonction d'attribution de noms decentralisee Download PDF

Info

Publication number
WO2000001112A1
WO2000001112A1 PCT/US1999/014631 US9914631W WO0001112A1 WO 2000001112 A1 WO2000001112 A1 WO 2000001112A1 US 9914631 W US9914631 W US 9914631W WO 0001112 A1 WO0001112 A1 WO 0001112A1
Authority
WO
WIPO (PCT)
Prior art keywords
machine
name
name server
server
virtual
Prior art date
Application number
PCT/US1999/014631
Other languages
English (en)
Inventor
Michael Emke
Original Assignee
Science Applications International Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Science Applications International Corporation filed Critical Science Applications International Corporation
Priority to AU48404/99A priority Critical patent/AU4840499A/en
Publication of WO2000001112A1 publication Critical patent/WO2000001112A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming

Definitions

  • the present invention relates network services, and more particularly to name services. Even more particularly, the present invention relates to a system and method for reducing bandwidth usage in the provision of name services in a highly distributed network environment, such as the Internet.
  • the Internet presents significant challenges and opportunities to providers of traditional network services including name services, such as domain name services, or other such services used to resolve machine names.
  • name services such as domain name services, or other such services used to resolve machine names.
  • the number of Internet users is growing rapidly, stimulating network traffic and in turn demand for new services.
  • IP Internet protocol
  • IP addresses take the form of four numbers, each between 0 and 255, separated by periods, and are used to uniquely identify each host on the Internet.
  • An example of an IP address is 204.216.142.198.
  • IP addresses are inherently “unfriendly” in that they are "machine-like” and “numerical” in nature and are thus difficult for users to remember.
  • a system of domain names has been developed in which textual names are associated with a host's IP address in order to identify the host by a textual name.
  • An example of a domain name is emke.com. Because, however, the use of domain names is not integral to the underlying protocol used on the
  • IP Internet Protocol
  • the originating host 100 when an originating host 100 connected to the Internet 102 uses a domain name to attempt access of a destination host 104 on the Internet 102, the originating host 100 first queries its local domain name server 106 or DNS (maintained by its Internet service provider or, ISP, which may be a commercial online service provider, a company network service provider, or other DNS provider) by sending the domain name of the destination host 104 with which the originating host 100 seeks to communicate to the local domain name server 106, in hopes that the local domain name server 106 has cached information regarding the IP address corresponding to the domain name of the destination host 104.
  • DNS maintained by its Internet service provider or, ISP, which may be a commercial online service provider, a company network service provider, or other DNS provider
  • the local domain name server 106 queries a root domain name server 108 for this IP address.
  • the root domain name server 108 may redirect the local domain name server's request to a generic top level domain, or gTLD, server 110 associated with a particular generic top level domain for which an IP address is sought. For example, if a ".co " domain is sought, the root domain server 108 may redirect the local domain name server's request to a gTLD server 110 for the ".com" domain.
  • the gTLD server 110 is generally located proximate to the root domain server 108 , both of which are generally located remotely from the originating host 100.
  • Each root domain name server 108 has its own set of gTLD servers 110.
  • the 110 may provide the local domain name server 106 with the IP address of the destination host 104, however, it may also redirect the local domain name server 106 to another local domain name server 112 that provides domain name services for the destination host 104 domain name.
  • the other local domain name server 112 provides the originating host's local domain name server 106 with the IP address of the destination host 104, and the local domain name server 106 provides the IP address of the destination host 104 to the originating host 100.
  • the originating host 100 then can communicate directly with the destination host 104 using the destination host's 104 address.
  • two long distance communications i.e., that between the local domain name server 106 and the root domain name server 108, and that between the local domain name server 106 and the generic gTLD server 110 take place before direct communication between the originating host's local domain server 106 and the destination host's local domain name server can occur 112.
  • These communications may, depending on the location of the originating host 100 and its local domain name server 106, require a pair or intercontinental communications 114, 116 (between the originating host's local domain name server 106 and the root domain name server 108, and between the originating host's local domain name server 106 and the gTLD server 110) , which at this time for foreign (i.e., non-U.S.) users can present significant a communications "bottleneck", not to mention the significant additional traffic this creates on the Internet 102.
  • the present invention advantageously addresses the above and other needs.
  • the present invention advantageously addresses the needs above as well as other needs by providing a decentralized name services approach suited particularly for provision of name services in a highly distributed environment.
  • One embodiment of the present invention can be characterizes as a method of resolving a machine name into a machine identifier.
  • the method has steps of communicating periodically machine name/machine identifier information from a root name server to a first local virtual name server; receiving, in the first local virtual name server, a machine name from an originating host; resolving, within the first local virtual name server, the machine name into a machine identifier for one of a second local virtual name server and a destination host; and resolving, within the second local virtual name server, in the event the machine identifier into which the machine name is resolved by the first local virtual name server is a machine identifier for the second local virtual name server, the machine name into a machine identifier for the destination host.
  • Another embodiment of the present invention can be characterized as a method of resolving a machine name into a machine identifier, having steps of receiving, in a first local virtual name server, a machine name from an originating host, the originating host and the first local virtual name server being in a first subnet; resolving, within the first local virtual name server, the machine name into a machine identifier for one of a second local virtual name server and a destination host; and resolving, within the second local virtual name server, in the event the machine identifier into which the machine name is resolved by the first local virtual name server, the machine name into a machine identifier for the destination host.
  • Yet another embodiment of the present invention can be characterized as a system for resolving a machine name into a machine identifier.
  • the system employs an originating host initiating communication with a destination host by transmitting a machine name of the destination host to a first virtual name server; the first virtual name server receiving the machine name and resulting the machine name into a machine identifier or one of a second virtual name server or the destination host; and initiating communication with the second virtual name server in the event the machine identifier into which the machine name is resolved is a machine identifier for the second virtual name server, transmitting the machine name of the destination host to the second virtual name server; and the second virtual name server receiving the machine name from the first virtual name server and resolving the machine name into the machine identifier of the destination host, and transmitting the machine identifier of the destination host to the fast virtual name server, the first virtual name server transmitting the machine identifier of the destination host, whether resolved in the first virtual name server or the second virtual name server, to the originating host.
  • FIG. 1 is a block diagram illustrating an originating host, the originating host's local domain name server, a root domain name server, a gTLD server, a destination host's local domain name server, and the destination host, with arrows illustrating traffic generated between these hosts as a result of a domain name lookup (worst case, i.e., non-cached, etc.) in accordance with the prior art;
  • FIG. 2 is a signal diagram illustrating data signals traveling between the originating host, the originating host's local domain name server, the root domain name server, the gTLD server, the destination host's local domain name server, and the destination host of FIG. 1 in accordance with the prior art
  • FIG. 3 illustrates an originating host, the originating host's local virtual gTLD server, a destination host's local virtual gTLD server, and the destination host, with arrows illustrating traffic generated between these hosts as a result of a domain name lookup in accordance with one embodiment of the present invention.
  • FIG. 4 is a signal diagram illustrating data signals traveling between the originating host, the originating host's local virtual gTLD server, the destination host's local virtual gTLD server, and the destination host of FIG. 3 in accordance with one embodiment of the present invention.
  • FIGS. 1 and 2 a block diagram and a signal diagram are shown of a current (prior art) approach to domain name lookup in an Internet environment. Shown is an originating host 100, the originating host's domain name server 106, a root domain name server 108, a generic top level domain (gTLD) server 110, a destination host's local domain name server 112 and the destination host 104.
  • gTLD generic top level domain
  • the architecture illustrated dictates that up to five communications 114, 116, 118, 120, 122 occur in order for the originating host 100 to contact the destination host 104 , two of which (114 and 116) are potentially intercontinental communications even when both the originating host 100 and the destination host 104 are in the same foreign, i.e., non-U.S., country.
  • 114 and 116 are potentially intercontinental communications even when both the originating host 100 and the destination host 104 are in the same foreign, i.e., non-U.S., country.
  • a great deal of network traffic occurs outside the originating host's subnet in order to resolve (i.e., look up) a domain name.
  • this arrangement is highly undesirable in that a great deal of communication occurs unnecessarily, thus wasting the precious little bandwidth available in many areas of the Internet, such as at routers providing intercontinental connections.
  • FIGS. 3 and 4 a block diagram and a signal diagram are shown illustrating an approach in accordance with one embodiment of the present invention.
  • This alternative approach eliminates both the root domain name server (at least in the sense employed by the prior art approach of FIGS. 1 and 2) and the gTLD server from the structure and method required by the prior art for resolution of a domain name into an IP address in a network transaction (i.e., from a single communication between the originating host 100 and the destination host 104) , leaving only the originating host 100, a local virtual gTLD server 300, a remote virtual gTLD server 302, and the destination host 104.
  • all domain name information is maintained locally by the originating host's local virtual gTLD server 300 (typically the local virtual gTLD server 300 would be maintained by an Internet service provider, or by a company having its own subnet) , and therefore no need to access a root domain server or other gTLD server 300 exists. If the Australian originating host wishes to access an Australian destination host, the originating host accesses its local virtual gTLD server 300 at which information regarding the IP address (or, in other embodiments, another such machine identifier) of the destination host 104 is stored.
  • This IP address information may be in the form of an IP address (or other machine identifier) for the remote virtual gTLD server 302 at the destination host 104, in which case a query is sent by the originating host's local virtual gTLD server 300 to the destination hosts's local virtual gTLD server 302, the response to which is the IP address (or other machine identifier) for the destination host 104 ; or this IP address information may be in the form of an IP address (or other machine identifier) for the destination host 104.
  • the originating host 100 communicates directly with the destination host 104 using its IP address as provided by the respective virtual gTLD server 300 or 302.
  • three communications 304, 306, 308 are required in order for the originating host 100 to communicate with the destination host 104, instead of five, as with the prior art approach of FIGS. 1 and 2.
  • none of the three communications are intercontinental .
  • a database of domain names and corresponding ID addresses is maintained on the local and remote gTLD servers 300, 302, and the local and remote virtual gTLD servers 300, 302 are maintained by a root domain name server 310, much like the root domain name server 108 in FIG. 1, on a periodic basis, such as daily, however, rather than on a per-transaction basis.
  • An entire database of domain names and corresponding IP addresses need not be downloaded to each virtual gTLD server on the Internet periodically. Instead, a delta file containing only the additions, changes and deletions to the root domain name server's databases since the last update of the virtual gTLD server, need be sent on the periodic basis.
  • This delta file requires minimum bandwidth, and only a single interchange between the root domain name server 310 and the virtual gTLD servers 300, 302 need take place.
  • This delta file can be compressed using any number of widely known compression approaches in order to further improve bandwidth efficiency.
  • This interchange between the virtual gTLD servers 300, 302 and the root domain name server 310 can be initiated by the virtual gTLD servers 300, 302, via a request or, alternatively, can be initiated by the root domain name server 310 by a "pusher".
  • This "pusher” can also be used in the event the root domain name server 310 has need to expire or otherwise change a domain name's status, and assure that all virtual gTLD servers throughout the Internet are updated.
  • the "pusher” is simply an additional process executing in the root domain name server 310.
  • domain name server updates are highly managed and centrally administered, yet the need for constant access to and communication with the root domain name server 310, on a per transaction basis, is not required.
  • Changes to domain names may be initiated by the virtual gTLD server 300 or 302 that "hosts" the changed domain name.
  • the virtual gTLD server 300 or 302 creates its own delta file to be transmitted to the root domain name server 310 during its next transaction with the root domain name server 310, or immediately.
  • This delta file assures that the root domain name server 310 is updated quickly after changes are made at the virtual gTLD server 300 or 302 to the hosted domain name, and that these changes will soon be propagated throughout the Internet within one update cycle to each other virtual gTLD server 300 or 302 on the Internet.
  • One side benefit that the present embodiment offers is that all domain name server lookup activity for any given originating host, and for that matter, for any given group of originating hosts, or any given subnet, is conducted through a single virtual gTLD server.
  • This virtual gTLD server is aware of all domain name lookup activity by the originating host or originating hosts that use the virtual gTLD server, and therefore can maintain logs of domain name server activity by such originating host.
  • companies or government entities maintaining their own virtual gTLD servers can monitor activities by employees and others on their subnet simply by viewing (or otherwise auditing) their virtual gTLD server logs.
  • This advantage of the present embodiment may prove highly desirable to some companies or government entities that wish to maintain a watch over their employees' Internet activities.
  • each virtual gTLD server can be programmed to deny domain name services to particular destination domains (i.e., hosts) as determined by their administrators.
  • destination domains i.e., hosts
  • companies or government entities wishing to block domain name server servicing for certain domain names need simply configure their virtual gTLD server to deny domain name lookup services to originating hosts within their network. This can be done on a per- originating-host basis, on the basis of a group of originating hosts, or on the basis of an entire subnet.
  • domain name services can be denied altogether for certain originating hosts in the event, for example, the originating host is to be denied access to servers outside a particular subnet or group of hosts.
  • the present invention has application outside the Internet, such as for example, on internets or other TCP/IP networks, or subnetworks.
  • the inventors envision that the present invention does not dictate that the entire Internet adopt teachings of the embodiment described above.
  • Individual Internet service providers (ISP's) or company subnets could adopt an approach in accordance with the embodiment described above, while others continue to operate in accordance with the teachings of the prior art, as also described above.
  • the inventors contemplate that the present invention can easily be applied to other network topologies employing machine name lookup and machine identifiers analogous to IP addresses.

Abstract

Une fonction d'attribution de noms de domaines est réalisée grâce à un système/procédé qui communique périodiquement des informations de nom/identificateur d'un hôte (100, 104) entre un serveur de nom racine (310) et un premier (300) et un second (302) serveur de nom virtuel local. Le premier serveur (300) reçoit un nom de machine de la part d'un hôte de départ (100) et résout le nom de machine sous forme d'un identificateur de machine pour le second serveur (302) et pour un hôte de destination (104). Si l'identificateur de machine est pour le second serveur (302), ce dernier résout le nom de machine pour l'hôte de destination (104). Dans une variante, le premier serveur (300) peut recevoir le nom de machine de la part de l'hôte de départ (100). Ils se trouvent tous deux sur le même sous-réseau. Le premier serveur (300) résout le nom de machine sous forme d'identificateur de machine pour le second serveur (302) et pour l'hôte de destination (104). En revanche, si l'identificateur de machine résolu est destiné au second serveur (302), ce dernier résout le nom de machine sous forme d'identificateur de machine pour l'hôte de destination (104).
PCT/US1999/014631 1998-06-29 1999-06-25 Fonction d'attribution de noms decentralisee WO2000001112A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU48404/99A AU4840499A (en) 1998-06-29 1999-06-25 Decentralized name services

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US10711398A 1998-06-29 1998-06-29
US09/107,113 1998-06-29

Publications (1)

Publication Number Publication Date
WO2000001112A1 true WO2000001112A1 (fr) 2000-01-06

Family

ID=22314912

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US1999/014631 WO2000001112A1 (fr) 1998-06-29 1999-06-25 Fonction d'attribution de noms decentralisee

Country Status (2)

Country Link
AU (1) AU4840499A (fr)
WO (1) WO2000001112A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6411966B1 (en) * 1998-09-21 2002-06-25 Microsoft Corporation Method and computer readable medium for DNS dynamic update to minimize client-server and incremental zone transfer traffic

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5777989A (en) * 1995-12-19 1998-07-07 International Business Machines Corporation TCP/IP host name resolution for machines on several domains
US5898830A (en) * 1996-10-17 1999-04-27 Network Engineering Software Firewall providing enhanced network security and user transparency

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5777989A (en) * 1995-12-19 1998-07-07 International Business Machines Corporation TCP/IP host name resolution for machines on several domains
US5898830A (en) * 1996-10-17 1999-04-27 Network Engineering Software Firewall providing enhanced network security and user transparency

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6411966B1 (en) * 1998-09-21 2002-06-25 Microsoft Corporation Method and computer readable medium for DNS dynamic update to minimize client-server and incremental zone transfer traffic

Also Published As

Publication number Publication date
AU4840499A (en) 2000-01-17

Similar Documents

Publication Publication Date Title
US6154776A (en) Quality of service allocation on a network
US6292838B1 (en) Technique for automatic remote media access control (MAC) layer address resolution
US6981029B1 (en) System and method for processing a request for information in a network
EP1303109B1 (fr) Résolution de noms virtuels de réseau
US6016512A (en) Enhanced domain name service using a most frequently used domain names table and a validity code table
JP4592184B2 (ja) 静的な識別子が付され、かつネットワークに断続的に接続される装置へのアクセス方法および装置
JP3725376B2 (ja) Ｄｎｓ問い合わせ装置、ｄｎｓ問い合わせ方法、および記録媒体
JPH0870299A (ja) ネットワークにおけるターゲット送信方法及びメッセージターゲット生成システム
US20070180120A1 (en) Automated management of network addresses in a broadband managed access environment
US20040143579A1 (en) Address query response method, program, and apparatus, and address notification method, program, and apparatus
CA2348490A1 (fr) Gestionnaire de serveurs
CA2287639A1 (fr) Liaison de reseau securise a l'aide du protocole de gestion d'annuaires ldap
JPH1127320A (ja) パケット中継制御方法，パケット中継装置およびプログラム記憶媒体
JPH1075244A (ja) アドレス自動配布システム
US7136858B2 (en) Network update manager
US7072980B2 (en) Method and system for route table minimization
US20020143946A1 (en) Software based internet protocol address selection method and system
JP4077351B2 (ja) 名前／アドレス変換装置
JP2000349747A (ja) 公開鍵管理方法
WO2001033364A1 (fr) Dispositif pour rechercher le nom d'un noeud de communication dans un reseau de communication
WO2013082791A1 (fr) Procédé, dispositif et système de mise à jour de ttl d'adresse et de rr de client dns
WO2001014989A1 (fr) Architecture d'ordinateur destinee a un service de gestion de reseau identifiant et localisant les utilisateurs et/ou des dispositifs a l'interieur d'un reseau d'entreprise
WO2000001112A1 (fr) Fonction d'attribution de noms decentralisee
KR20050003598A (ko) 이중화된 도메인 네임 서버를 이용한 도메인 네임 서비스제공 시스템 및 제공 방법
Cisco Configuring the Cisco SIP Proxy Server

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AL AM AT AU AZ BA BB BG BR BY CA CH CN CU CZ DE DK EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT UA UG UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW SD SL SZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP

WWW Wipo information: withdrawn in national office

Country of ref document: JP