WO2005093999A1 - Systemes et procedes d'enregistrement et d'utilisation de noms de domaine - Google Patents

Systemes et procedes d'enregistrement et d'utilisation de noms de domaine Download PDF

Info

Publication number
WO2005093999A1
WO2005093999A1 PCT/CA2005/000453 CA2005000453W WO2005093999A1 WO 2005093999 A1 WO2005093999 A1 WO 2005093999A1 CA 2005000453 W CA2005000453 W CA 2005000453W WO 2005093999 A1 WO2005093999 A1 WO 2005093999A1
Authority
WO
WIPO (PCT)
Prior art keywords
tld
name
address
server
icann
Prior art date
Application number
PCT/CA2005/000453
Other languages
English (en)
Inventor
Elias Assad
Original Assignee
Elias Assad
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 Elias Assad filed Critical Elias Assad
Priority to EP05714677A priority Critical patent/EP1784947A1/fr
Publication of WO2005093999A1 publication Critical patent/WO2005093999A1/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
    • H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
    • 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
    • H04L61/4552—Lookup mechanisms between a plurality of directories; Synchronisation of directories, e.g. metadirectories

Definitions

  • the present invention is related to domain names, and in particular to methods and systems for creating and using non-ICANN top-level domain names.
  • IP Internet Protocol
  • DNS Domain Name System
  • the DNS is a distributed database system that allows computer applications to map between domain names and IP addresses.
  • the DNS also provides electronic mail routing information and many other services. Individual components of the DNS distributed database can be cached locally, or stored on any of numerous distributed machines.
  • the DNS database data correlates each domain name to a specific numeric IP address. If a computer's local cache does not have the information to resolve a domain name into an IP address, it sends a request to other computers that may contain the resolution information.
  • the DNS affords a domain name some measure of independence from the physical location of a host. The host can be moved to a new location on the network, but it can still be accessed using the same domain name. As long as a user can remember the domain name, the host can always be located, even if the IP address changes over time.
  • the DNS comprises many servers and other computers or machines that run software and store data permitting computers to query the DNS database.
  • One such machine is the "root server.”
  • a root server is a server computer that maintains the software and data necessary to locate "name servers” that contain authoritative data for a specific domain, such as the ".com” top level domain.
  • Name servers are computers that have the software and data to resolve the domain name into an IP address.
  • the data accessible through the name server is often referred to as a "zone file.”
  • a "zone” is a subset of the total domain name space. The domain names in that subset are stored in the zone file for that name server. There is a zone file for each domain space (i.e., zone).
  • the DNS is organized in a hierarchical, tree structure.
  • a domain name is the label representing a specific domain within the total possible domain space available in the DNS.
  • the highest level in the DNS hierarchy is the "root,” which is technically unnamed but often referred to as the ".” or “dot.”
  • the level immediately below the root in the DNS hierarchy is the top-level domain, or "TLD.” It is called the "top-level domain” because it is the highest level in the hierarchy after the root.
  • the TLD appears furthest to the right in an English-language domain name. For example, "gov” in the "uspto.gov” domain name.
  • a second-level domain is the level in the DNS hierarchy immediately below the TLD.
  • An example of a second-level domain would be
  • SRS Shared Registration System
  • the SRS was created by Network Solutions, Inc. in 1999 to provide a registry backend through which multiple, globally diverse registrars could register domain names.
  • the term "registry” refers to the entity responsible for managing allocation of domain names within a particular name space, such as a TLD.
  • a registry is the NeriSign registry for the .com, .org, and .edu TLDs.
  • the term "registrar” refers to any one of several entities with authority to issue commands or requests to add, edit, or delete registrations to or from the registry for a name space.
  • ICANN Assigned Names and Numbers
  • an online user can utilize a web browser to access and view websites by entering an Internet address in the form of a domain name, such as www.domain-l.com, for example, or a Uniform Resource Locator (URL), such as http ://www.domain- 1.com/index.htm.
  • a domain name such as www.domain-l.com, for example, or a Uniform Resource Locator (URL), such as http ://www.domain- 1.com/index.htm.
  • URL Uniform Resource Locator
  • the browser extracts the Internet address, www.domain-l.com, from the URL, mentioned above, and transmits a look-up request, including the extracted address, to a Domain Name System server (DNS server).
  • DNS server Domain Name System server
  • the DNS server returns the IP address corresponding to the domain name to the browser.
  • the browser uses the IP address to access the corresponding computer. It may take a number of servers to locate the corresponding IP address. For example, a first name server for the "com" top-level domain stores the IP address for a second name server that stores the host names. A separate query is then made by the first name server to the second name server for the actual IP address for domain-1's web server.
  • Domain names or more specifically domain name registrations, have- become significant business (and personal) assets. Registration rights are now bought, sold, traded, bartered, auctioned and stockpiled in "inventories.” At the time of this writing, Verisign, Inc. — the company that maintains the .com, .net, and .org TLD registries - reports over 32 million registrations in its database. Industry statistics indicate, however, that only about 10% of the domain names registered are currently in actual use, including more than just a simple holding or redirection page. Many registrations are the work of speculators.
  • TLD time-dependent low-density diode
  • gTLD global top-level domain
  • GCT Generic top-level domain
  • a glo ⁇ bal TLD is one that can be registered by an entity regardless of the entity's geographic location or political boundary. New gTLDs are being added as the older ones ⁇ .com .net org—become saturated.
  • the realm of possible names under a given gTLD is not the problem, it is immense. (Names up to 67 characters long, plus the extension, apparently can be registered today.) The trouble is that popular, easy to remember or ea.sy to recognize names are relatively limited in number. Many of the most desirable domain names, those corresponding to well-known trademarks or generically describing commercial goods or services, are long since taken in the basic gTLD spaces.
  • TLDs in the current DNS system negatively i ⁇ rpacts the growth of the Internet because it does not fully meet the domain name needs of individuals, businesses and other organizations.
  • the scarcity of TLDs is directly responsible for the rise of speculation and "cyber-squatting".
  • IPv6 Internet Protocol
  • the current DNS may not meet the needs of hundreds of millions of users for convenient communication, in which a uniform and well understood naming mechanism plays a pivotal role.
  • an individual who wants to use their name for a domain name currently have to use the ".name” TLD, as in "Firstname.Lastname.name”, which could be considered less desirable to just using "Firstname.Lastname” as a domain name.
  • the ability, provided by this invention, to make practicable the assignment of a SLD name to an individual one benefit would be the use the domain name "Firstname.Lastname" as an email address.
  • the present invention is directed to methods and systems used to provide and use unlimited top-level domain names that are created on demand, in parallel with those specified by the Internet Corporation for Assigned Names and Numbers (ICANN) or other authority authorized to approve standardized top-level domain names.
  • ICANN Assigned Names and Numbers
  • a domain registration system uses a predefined function that maps the TLD name to an IP address, herein termed TLDIP address, which belongs to a set of IP addresses reserved a priori for a group of name servers. If the TLD name has not been registered before, the registration system assigns the TLDIP address to a network interface on a name server computer, which would then become the designated TLD name server for said TLD.
  • TLDIP address an IP address
  • a DNS extension software running on a client computer system uses the said predefined function when a user enters an Internet address containing a non-ICANN TLD name on a client computer in order to compute the IP address of the corresponding TLD name server and access it, and thereby enable browsers and other connectivity devices or systems to access and/or utilize non-ICANN top-level domains.
  • the registration and use of the Internet addresses utilizing the non-ICANN top-level domain (TLD) names can be performed using different embodiments of processes and systems in accordance with the present invention.
  • the user downloads the DNS extension software program to a client computer system that includes WinSock2 or equivalent service providing an interface to the Name Space Provider(s) and Layered Service Provider(s) to enable utilization of the non-ICANN domain addresses, as discussed in greater detail below.
  • the DNS extension software may be downloaded or installed from a floppy disk, CD- ROM, via a network, such as the Internet, or may be pre-installed on the client computer.
  • the downloaded DNS extension software processes non-ICANN address requests (those addresses that do not end in .com, net, .org, mil, an ICANN-defined two letter country code, or other ICANN specified TLDs) received from a browser or other application by computing the IP address of the TLD name server from the characters of the TLD name.
  • a user downloads the DNS extension software and then, using the browser, requests a non-ICANN address, such as John.Doe.
  • a non-ICANN address such as John.Doe.
  • the process begins with the browser requesting the operating system services to identify the numeric location of the requested website.
  • the operating system utilizes the DNS extension software, which resolves the domain name and returns the IP address that identifies the requested website.
  • Another embodiment provides a process for accessing the non-ICANN Internet addresses through the user's ISP.
  • This approach is performed in a manner transparent to the consumer, as it does not require the DNS extension software to be installed on the user's system.
  • utilizing such non-ICANN TLDs attracts more consumers.
  • the user enters or provides a browser with a non-ICANN Internet address (e.g., John.Doe) of a website or other network resource.
  • the browser in communication with the operating system, sends an IP address lookup request to the ISP's domain name system server. If the domain name system server implements the methods disclosed herein, applying a predefined function to compute the IP address of the TLD name server, it then locates the IP address representing the server of the requested page.
  • FIG. 1 illustrates an example process for creating a non-ICANN TLD name and an SLD name in accordance with one embodiment of the present invention
  • FIG. 2 illustrates an example process for creating a non-ICANN TLD name and an SLD name in greater detail using sample data
  • FIG. 3 illustrates an example process for using an Internet address comprising a non- ICANN TLD name to access a network resource in accordance with one embodiment of the present invention
  • FIG. 4 illustrates an example process for using an Internet address containing a non- ICANN TLD in greater detail
  • FIG. 5 illustrates an example process for using an Internet address containing a non- ICANN TLD using a proxy server in accordance with one embodiment of the present invention.
  • the present invention is directed to methods and systems used to provide and use unlimited top-level domain names that are created on demand, in parallel with those specified by the Internet Corporation for Assigned Names and Numbers (ICANN) or other entity having the governmentally or community granted authority to approve or create standardized top-level domain names.
  • ICANN Assigned Names and Numbers
  • one embodiment of the present invention provides systems and methods for registering a non-ICANN TLD name by mapping it to an IP address using a predefined mapping function, assigning the resulting IP address to a server system that acts as the name server for TLD name, and subsequently using the said predefined function when a user enters an Internet address containing said TLD name on a client computer in order to compute the IP address of the said name server and access it.
  • a webpage containing a registration form is transmitted f om a server to the client computer system of a person desiring to register a domain name.
  • the server herein termed Registrar Server
  • Registrar Server is optionally associated with an entity that registers, sells, and tracks non-ICANN TLD and SLD names, termed herein, a TLD company, or an entity that registers, sells, and tracks SLD based on non-ICANN TLD names, termed herein, a Registrar.
  • the TLD company further operates a group of servers comprising at least one Registry Server, at least one TLD Farm Server, and at least one TLD Name Server, the roles of which are clarified herein.
  • the person desiring to register a domain name uses a registration form to enter a desired non-ICANN TLD name and an SLD name, as in "SLD.TLD", and the desired the SLD's name server address, among other information.
  • the person then submits the registration form to the server by, for example, clicking a submit button on the Webpage containing the registration form.
  • the Registrar Server extracts at least the entered domain name ("SLD.TLD”) and the SLD's name server address and submits them to the Registry server using, for example, an Internet standard Registry-Registrar protocol.
  • the Registry server verifies the availability of the domain name in its database.
  • the Registry server If the "SLD.TLD" domain name is not available or otherwise cannot be registered, e.g., it has been registered to another person, the Registry server returns a message to that effect to the Registrar server, which in turn sends a corresponding message or Webpage to the person's computer.
  • the Registry server sends a registration request to the TLD Farm Server.
  • the TLD Farm Server uses a predefined function that maps the TLD name to an IP address, herein termed TLDIP address, which belongs to a set of IP addresses reserved a priori by the TLD company. If the TLD name has not been registered before, the TLD Farm Server assigns the TLDIP to a network interface on a server computer, which would then become the designated TLD name server for the said TLD name, and creates the TLD zone file on the TLD name server.
  • the TLD Farm Server will then use this TLDIP address to connect to the TLD name server and cause this and subsequent SLD registration functions to be carried out in accordance with standard DNS procedures.
  • the predefined mapping function maps the TLD name's character string to a numeric value representing an IP address that falls within a range of IP addresses used by the TLD company for the operation of its group of TLD name servers, which addresses might be IPv4 or IPv6 addresses.
  • the TLDIP function may use the first few characters of the TLD name, and maps each combination to a unique IP number having the subnet prefix of the subnet used by TLD company for its TLD name servers.
  • the TLDIP function may be implemented by starting with an initial value pair (Character string, IP address) and incrementing both while observing the rules of their respective domains until reaching the value for of the character string of the TLD name. For example, if the TLD name "aa" is made to correspond to "24.153.0.0", then
  • the TLDIP address may also be computed from the character string by way of an algorithm that uses the numeric code (e.g., ASCII) of the characters in the TLD name to compute the corresponding IP address, or by assigning IP addresses to ranges of character strings.
  • the TLDIP function may implement rules to generate IP addresses belonging to different subnets, as to allow multiple TLD companies to operate TLD name servers, or to allow for the possibility of changing subnets of the same TLD company.
  • the TLDIP function depends on several factors, including the actual IP addresses that would be available to the TLD name servers, the naming rules that would be supported by the TLD company for non-ICANN TLD names, and even business considerations.
  • the TLDIP function is updated periodically to change, if required, the subnet prefix or the algorithm it uses to compute IP addresses.
  • the TLDIP function would use the first 4 characters of the TLD name, it would generate a possible 1,874,161 TLD names (37 possible characters under RFC 1035, to the power 4), and if it were to map an IP address to each of these names, it would utilize a subnet prefix and mask of 255.224.0.0/32, providing 32 Class B IPv4 addresses, or
  • FIG. 1 illustrates an example process 100 where a domain name, including a non-ICANN
  • TLD name is created in accordance with the present invention.
  • the domain names are optionally required to be RFC 1035 compliant, in that they are restricted to the RFC 1035 defined character set, including characters selected from the set of the letters A-Z in upper and lower case, the numbers 0-9, and a hyphen "-".
  • a Registrant 102 enters in a registration form or otherwise provides registration data to the Registrar Server 104.
  • Registration data includes a non-ICANN TLD name, and an SLD name and its name server data.
  • the Registrar Server 104 extracts the non-ICANN TLD, and SLD name and its name server data and submits an "ADD SLD.TLD" request to the Registry Server 106 using, for example, Registry-Registrar Protocol (RFCs 2832 & 3632) or the Extensible Provisioning Protocol (an IETF Draft).
  • the Registry Server 106 queries the TLD Zone Database 112, which is used to store the zone data belonging to all TLDs in the system.
  • the Registry Server 106 then implements the following: if the domain name "SLD.TLD" is already present in the database 112, or is flagged in the data base as unavailable, it replies to the Registrar Server with the appropriate failure response code; otherwise, if TLD is already present in the database 112, it passes the registration data to the TLD Farm Server 108 with a request to add the SLD data to the TLD Zone file; otherwise (i.e., new TLD), it passes the registration data to the TLD Farm Server 108 with a request to create the TLD zone file and add the SLD data to it.
  • the TLD Farm Server uses the TLDIP function to compute an IP address from the TLD name. If the request from the Registry Server is to create a new TLD name, the TLD Farm Server 108 selects a server from the group of TLD name servers 110 (e.g., based on historical load or geographical location criteria) and binds the computed TLDIP address to an interface on the selected server, acting in a manner similar to a DHCP server - where a process on the selected server, in communication with the TLD Farm Server, receives the TLDIP address and does the binding.
  • a server from the group of TLD name servers 110 e.g., based on historical load or geographical location criteria
  • the TLDIP function is designed to produce a second IP address corresponding to the character string of the TLD name, allowing the TLD Farm Server to bind the second IP address to an interface on a second server possibly belonging to another subnet.
  • the TLD Farm Server 108 then adds the SLD data to the TLD Zone file 116. Otherwise, if the request from the Registry Server 106 is only to add the SLD to the TLD Zone file 116, the TLD Farm Server 108 uses the computed TLDIP address to connect to the TLD name server 110 that already has TLDIP assigned to it, and adds the SLD data to the TLD Zone file 116.
  • the Registrant 102 now writes the SLD Zone Data as usual to an SLD Zone File 118, making it available to the SLD name server 114.
  • an example process 200 for registering a TLD and an associated SLD is presented in greater detail using the sample domain name "JOHN.DOE".
  • the Registrar 104 having received a Registration Form from a registrant, submits the domain data and a request to add the domain name "JOHN.DOE" to the Registry Server, which queries the TLD Zone Database 112 at state 202. If there is a record for "JOHN.DOE" at state 204, the Registry Server returns a failure response code at state 206 to the Registrar Server, which sends an error message at state 208 to the registrant.
  • the TLD Farm Server computes the least significant pieces of an IP address from the string "DOE”, and concatenates them to a pre-assigned subnet prefix resulting, for example, in an IP address of "24.13.1.56".
  • the TLD Farm Server checks if "DOE" is present in the TLD Zone Database in the content of the request it received from the Registry Server at state 212. If "DOE" is not present, it selects, at state 214, a server "X" from the group of servers designated as TLD name servers, which selection may be based on load data it receives regularly from the TLD name servers.
  • the TLD Farm Server causes server "X” to bind the address of "24.13.1.56" to an interface on server "X". This binding may be performed by a message to a process running on server "X”.
  • the TLD Farm Server then writes the "DOE” Zone file to server "X" at state 218.
  • the TLD Farm Server writes "JOHN” domain data, including its name servers' data, to the "DOE” Zone file, and updates the TLD Zone Database at state 222 to reflect the registration of "JOHN.DOE".
  • DNS extension software can be downloaded via a webpage that may be hosted on any Web server.
  • Embedded on the webpage is downloadable DNS extension software, for example, a Java applet or ActiveX control, which may be digitally signed to ensure its authenticity and provide some measure of assurance that the author certifies that the DNS extension software is safe to run and that it has not been altered.
  • the user may be asked by their web browser whether the embedded DNS extension software should be permitted to run, assuming the browser verifies that the digital signature is valid and that the content has not been altered since the content was digitally signed.
  • Winsock short for Windows sockets, is an Application Programming Interface (API) for developing Microsoft Windows compatible programs that can communicate with other machines via the TCP/IP protocol, or the like. Of course other operating systems and APIs can be used as well.
  • API Application Programming Interface
  • the embedded program installs a Winsock2 Name Space Provider (NSP), also termed, in this example, the TLD NSP, to provide functionality for processing TLDs that are registered in accordance with this invention.
  • NSP Winsock2 Name Space Provider
  • WinSock2 utilizes the Windows Open Systems Architecture (WOSA) model, which separates the API from the protocol service provider.
  • the WinSock DLL provides the standard API, and each vendor's service provider layer is installed below the standard API.
  • the API layer communicates to a service provider via a standardized Service Provider Interface (SPI), and can multiplex between multiple service providers simultaneously.
  • Winsock2 contains a first NSP, termed herein a Default NSP, and the TLD NSP is added as a second NSP.
  • the default NSP is typically installed when Transmission Control Protocol/Internet Protocol (TCP/IP) support is installed.
  • TCP/IP Transmission Control Protocol/Internet Protocol
  • a Winsock2 NSP is a dynamic link library (DLL) that enables the conversion of alphanumeric names, such as www.domain-namel.com, to numeric addresses, such as 192.9.200.1, used to contact specific computers and their services.
  • DLL dynamic link library
  • the web browser uses Winsock2 or equivalent to perform the conversion of alphanumeric names to numeric addresses.
  • Winsock2 in turn, utilizes installed Name Space Providers to perform the conversion using the Winsock2 Service Provider Interface (SPI).
  • SPI Winsock2 Service Provider Interface
  • the TLD NSP once installed as described above, is listed in the Winsock2 service's catalog of Name Space Providers in addition to the default provider. Once the TLD NSP is listed in the Winsock2 NSP catalog, other applications gain access to the TLD NSP's services via Winsock2, as in the web browser example described above.
  • NSPs perform domain name conversions by using the DNS server lookup protocol to establish a connection with the user's domain name system servers and locate IP addresses which are typically provided by a user's Internet Service Provider (ISP).
  • ISP Internet Service Provider
  • a NSP sends the alphanumeric address to the DNS server and receives the IP address(es), or when appropriate, receives a response that the alphanumeric address is not valid. For example, if a user requests an Internet address with a non-ICANN TLD, such as www.john.doe, the default provider would not validate the address, unless the ISP has provisioned their DNS servers to recognize the non-ICANN TLDs, as described below. However, if the TLD name has been registered with the TLD company then, with the TLD NSP installed, the address will be resolved even if the ISP's DNS server does not implement the method disclosed herein.
  • the user initially enters or otherwise provides an Internet address containing a non-ICANN TLD name using a browser 302 or other Internet application.
  • the browser passes the domain name to Winsock2 304, which in turns contacts the Default NSP 308 and the TLD NSP 306 and requests the resolution of the domain name.
  • Winsock2 304 contacts the Default NSP 308 and the TLD NSP 306 and requests the resolution of the domain name.
  • the ISP DNS server returns an IP address to the Default NSP, allowing the browser to connect to the server represented by the IP address and to load the requested resource.
  • Such DNS server would also implement a response to a query sent periodically by the TLD NSP identifying its implementation, which would cause the TLD NSP to respond with a "Not Found” result to Winsock2, letting the Default NSP and the ISP's DNS perform the resolution function.
  • one embodiment of this invention provides a process for accessing the non-ICANN Internet addresses through the user's ISP, which does not require the DNS extension software to be installed on the user's system. Process 300 however assumes that the ISP's DNS does not implement the DNS extension software, which causes the Default NSP to return "Not Found" to Winsock2.
  • the TLD NSP 306 running on the client computer system now utilizes an instance of the same TLDIP function that is used by the TLD Farm Server mentioned above.
  • the TLD NSP extracts the non-ICANN TLD name from the domain name, and uses the TLDIP function to compute a TLDIP address; if the TLD name had been registered in accordance with this invention, the TLDIP address thus computed would have been bound to an interface on a TLD Name Server 310.
  • www.john.doe is entered in the browser address field, the TLD NSP extracts "doe" from it and uses the TLDJJP function to find the IP address (24.13.1.56) of the "doe" name server.
  • This latter server when requested by TLD NSP, retrieves the IP address of the SLD Name Server 314 from the TLD Zone File 312 and returns it to the TLD NSP.
  • the SLD Name Server 314 when requested by the TLD NSP, serves the IP address of the requested resource from the SLD Zone File 316 to the TLD NSP, which returns it to Winsock2, allowing the browser 302 to locate the website and display the requested resource.
  • FIG. 4 illustrates an example process 400 utilizing non-ICANN TLDs in greater detail.
  • Example process 400 can also be used with other Internet addresses using different protocols, such as FTP, Gopher, Telnet, or the like.
  • FTP FTP
  • Gopher Gopher
  • Telnet Telnet
  • the TLD NSP receives a domain name, "www.john.doe" from Winsock2, or equivalent, via SPI calls.
  • the TLD NSP verifies whether the ISP's DNS server uses TLDIP to resolve TLD names, in which case the TLD NSP at state 408 returns a "Not Found" response to Winsock2.
  • the TLD NSP examines the TLD name portion of the domain name to determine if it matches one of several predefined top-level domain names which are valid in the ICANN DNS namespace.
  • the TLD NSP is periodically updated by contacting a host server to update a list of the ICANN recognized or defined standard TLDs (e.g., ".com”, “.org”, “.mil”, “.gov”, “.info”, “.biz”, “.name”, or the two letter ending of a country such as ".uk”, “.de”, etc).
  • the TLD NSP at state 408 returns a "Not Found” response to Winsock2, again allowing the ISP's DNS server to supply name resolution to the Default NSP, which returns the result to Winsock2 at state 422.
  • a requested address such as www.ibm.com would cause a "Not Found” response to be sent by the TLD NSP, while it would be successfully resolved by the Default NSP using the standard DNS lookup process.
  • the TLD NSP at state 410 computes the IP address of the TLD name server by applying the TLDIP function to the TLD name.
  • the IP address "24.13.1.56” would be computed from the TLD name "DOE".
  • the rest is standard DNS process: the TLD NSP at state 412 would request resolution of "JOHN.DOE” from the TLD name server having the IP address "24.16.1.56", which would result in the IP address of the name server for the SLD JOHN.DOE, and then at state 414 request the resolution of WWW from the JOHN.DOE name server. If the entire domain name "www.john.doe" was resolved successfully, its IP address is returned to Winsock2 at state 420; otherwise a "Not Found” response is returned at state 418.
  • the original requestor in this case the Web browser, receives the results via the Winsock2 or equivalent programming interface, and accordingly either displays a "not found” page or uses the supplied IP address to retrieve the resource from the server "www.john.doe”.
  • process 400 allows non-standard addresses to be resolved to the corresponding IP addresses of network resources, such as computers, on the Internet. This enables a user to view webpages or other content (such as FTP data), regardless of whether the domain name is an ICANN registered one.
  • LSP Internet Services Provider
  • Winsock2 allows the creation of LSPs which can be stacked into chains.
  • the LSP is installed on top of a default Transport Service Provider (TSP).
  • TCP Transport Service Provider
  • One function of an LSP is to filter data, for a variety of reasons, communicated between two applications.
  • the LSP can be used to filter, by way of example, TCP and or UDP (User Datagram Protocol) traffic.
  • the LSP can then be used to monitor Internet addresses containing non-ICANN TLDs in accordance with one embodiment of the present invention.
  • the LSP can be used to provide filtering of traffic through the sockets. By monitoring socket traffic, use of an application-level protocol can be detected.
  • the LSP detects a non- ICANN address in the HTTP or proxy application level protocol, extracts the non- ICANN address and resolves it by computing the TLDIP address as outlined above and contacting the TLD Name Server and subsequently the SLD Name Server.
  • the LSP then replaces the non-ICANN address in the URL contained in the appropriate headers in the protocol with the corresponding IP address and forwards it to the proxy.
  • the LSP is periodically updated by contacting a host server to update a list of the defined ICANN TLD names. If a proxy server is used, the LSP intercepts the Internet address if the Internet address includes a non-ICANN TLD, as described above.
  • a proxy server is an Internet server that generally acts as a mediator between the client computer system and other servers hosting webpages.
  • the proxy server can, for example, sit on a firewall and protect the client systems from unauthorized access via the Internet, hi addition, the proxy can intercept and selectively block webpage requests coming from users within the firewall.
  • a firewall is a software program or hardware device that filters information coming through the Internet, for example, offensive websites.
  • the proxy server can also function as a caching server. Utilizing the proxy server's cached webpages, the proxy server will display previously accessed webpages to users without requiring outside access to the Internet, advantageously improving a network's performance.
  • a proxy server can be used without a firewall. Because of such benefits, many users access the Internet via a proxy server.
  • One embodiment of the DNS extension software is, therefore, compatible with users who access the Internet via a proxy server.
  • a proxy setup when a user sends a request for an Internet address, e.g. http://john.doe, the browser sends the string "http://john.doe/" directly to the IP address of the proxy.
  • the proxy then performs the DNS server lookup for the request, retrieves the requested resource and returns the results to the user.
  • the potential problem is the proxy server's DNS server may not have implemented the method of this invention to resolve non-ICANN domain names and would therefore fail to resolve the request for "john.doe".
  • an LSP provided by the TLD company, herein termed TLD LSP, is used to enable resolution of non-ICANN top-level domain names when a proxy server is used.
  • FIG. 5 illustrates an example process 500 wherein a TLD LSP is utilized to detect and resolve an Internet address containing a non-ICANN TLD before sending it to a proxy server.
  • a user enters or selects a non-ICANN Internet address.
  • the TLD LSP intercepts the Internet address. If the Internet address contains an ICANN TLD at state 506, then the TLD LSP transmits the request to the proxy server intact at state 508. Otherwise, at state 510, the TLD LSP computes the IP address, 24.13.1.56 that conesponds to TLD name "DOE".
  • the TLD LSP at state 512 uses this IP address to contact the "DOE" TLD name server to resolve "JOHN.DOE", resulting in another IP address that the TLD LSP uses at state 514 to contact "JOHN.DOE'"s SLD name server to resolve "WWW”.
  • the TLD LSP at state 520 replaces the domain name in the Internet Address with the IP address resulting from the resolution and transmits the changed request to the proxy server. If the domain name was not resolved successfully, then the TLD LSP transmits the request to the proxy server intact at state 508.
  • the TLD LSP By intercepting the requests being sent to a proxy server, the TLD LSP captures those Internet Addresses that are not sent to NSPs for resolution. The TLD LSP ignores those that are standard ICANN TLDs in order to let the existing DNS server used by the proxy perform the name resolution.
  • various embodiments of the present invention advantageously provide systems and methods for registering and resolving Internet addresses containing arbitrary non-ICANN TLDs. Further, systems and methods for translating Internet addresses containing non-ICANN TLDs using a proxy server are provided.
  • each step of the method may be executed on any general computer, such as an IBM mainframe, PC or the like and pursuant to one or more, or a part of one or more, program elements, modules or objects generated from any programming language, such as C, C++, Java or the like.
  • each said step, or a file or object or the like implementing each said step may be executed by special purpose hardware or a circuit module designed for that purpose. Accordingly, the scope of protection of this invention is limited only by the following claims and their equivalents.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Transfer Between Computers (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Computer And Data Communications (AREA)

Abstract

L'invention concerne des procédés et des systèmes d'enregistrement d'un nombre illimité de noms de domaine de premier niveau (TLD) hors ICANN créés sur demande, et d'utilisation de ces noms de domaine dans un environnement réseau parallèlement à ceux qui sont spécifiés par l'ICANN (Société pour l'attribution des noms de domaine et numéros sur Internet), ou par un autre organisme autorisé à approuver les noms de domaine de premier niveau standardisés. Un premier mode de réalisation de l'invention concerne des systèmes et des procédés d'enregistrement d'un nom de domaine hors ICANN TLD, qui consistent à mettre en correspondance le nom de domaine avec une adresse IP au moyen d'une fonction de mise en correspondance prédéfinie, à attribuer l'adresse obtenue à un système serveur qui joue le rôle d'un serveur de nom pour le nom TLD, puis, à utiliser ladite fonction prédéfinie lorsque l'utilisateur visite une adresse Internet contenant le nom TLD sur un ordinateur client pour calculer l'adresse IP du serveur de nom et y accéder. Par ailleurs, un autre mode de réalisation de l'invention est exploitable via des serveurs mandataires.
PCT/CA2005/000453 2004-03-29 2005-03-29 Systemes et procedes d'enregistrement et d'utilisation de noms de domaine WO2005093999A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP05714677A EP1784947A1 (fr) 2004-03-29 2005-03-29 Systemes et procedes d'enregistrement et d'utilisation de noms de domaine

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US55678804P 2004-03-29 2004-03-29
US60/556,788 2004-03-29

Publications (1)

Publication Number Publication Date
WO2005093999A1 true WO2005093999A1 (fr) 2005-10-06

Family

ID=35056543

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CA2005/000453 WO2005093999A1 (fr) 2004-03-29 2005-03-29 Systemes et procedes d'enregistrement et d'utilisation de noms de domaine

Country Status (3)

Country Link
EP (1) EP1784947A1 (fr)
CN (1) CN1985469A (fr)
WO (1) WO2005093999A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2012091950A1 (fr) * 2010-12-30 2012-07-05 Verisign, Inc. Systèmes et procédés permettant un échange de noms de domaine
WO2014000088A1 (fr) * 2012-06-25 2014-01-03 Crb Consulting Inc. Système et procédé de résolution d'un nom de domaine
CN103812956A (zh) * 2012-11-14 2014-05-21 中国电信股份有限公司 IPv4/IPv6应用转换方法、装置及智能移动终端
CN104052827A (zh) * 2013-03-15 2014-09-17 弗里塞恩公司 用于多租户通用顶级域部署的系统和方法

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2002015031A1 (fr) * 2000-07-31 2002-02-21 Trust & Obey Co., Ltd. Systeme de domaine virtuel
US20020065903A1 (en) * 1999-12-01 2002-05-30 Barry Fellman Internet domain name registration system
US20020073233A1 (en) * 2000-05-22 2002-06-13 William Gross Systems and methods of accessing network resources
US20030182447A1 (en) * 2001-05-31 2003-09-25 Schilling Frank T. Generic top-level domain re-routing system

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020065903A1 (en) * 1999-12-01 2002-05-30 Barry Fellman Internet domain name registration system
US20020073233A1 (en) * 2000-05-22 2002-06-13 William Gross Systems and methods of accessing network resources
WO2002015031A1 (fr) * 2000-07-31 2002-02-21 Trust & Obey Co., Ltd. Systeme de domaine virtuel
US20030182447A1 (en) * 2001-05-31 2003-09-25 Schilling Frank T. Generic top-level domain re-routing system

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2012091950A1 (fr) * 2010-12-30 2012-07-05 Verisign, Inc. Systèmes et procédés permettant un échange de noms de domaine
US9172673B2 (en) 2010-12-30 2015-10-27 Verisign, Inc Systems and methods for domain name exchange
AU2011352884B2 (en) * 2010-12-30 2015-11-05 Verisign, Inc. Systems and methods for domain name exchange
WO2014000088A1 (fr) * 2012-06-25 2014-01-03 Crb Consulting Inc. Système et procédé de résolution d'un nom de domaine
CN103812956A (zh) * 2012-11-14 2014-05-21 中国电信股份有限公司 IPv4/IPv6应用转换方法、装置及智能移动终端
CN104052827A (zh) * 2013-03-15 2014-09-17 弗里塞恩公司 用于多租户通用顶级域部署的系统和方法

Also Published As

Publication number Publication date
CN1985469A (zh) 2007-06-20
EP1784947A1 (fr) 2007-05-16

Similar Documents

Publication Publication Date Title
US20060218289A1 (en) Systems and methods of registering and utilizing domain names
US9659070B2 (en) Methods, systems, products, and devices for processing DNS friendly identifiers
US11606388B2 (en) Method for minimizing the risk and exposure duration of improper or hijacked DNS records
US9866523B2 (en) Method and system for increasing speed of domain name system resolution within a computing device
US7225272B2 (en) Method and apparatus for providing name services
US9231903B2 (en) System and method for resolving a DNS request using metadata
US20080235383A1 (en) Methods, Systems, Products, And Devices For Generating And Processing DNS Friendly Identifiers
US20020073233A1 (en) Systems and methods of accessing network resources
Aitchison Pro Dns and BIND 10
EP3114822A1 (fr) Authentification de mandataire transparente par l'intermédiaire d'un traitement de serveur de nom de domaine (dns)
CN114205330B (zh) 域名解析方法、域名解析装置、服务器以及存储介质
Aitchison Pro DNS and Bind
EP1784947A1 (fr) Systemes et procedes d'enregistrement et d'utilisation de noms de domaine
US20160087937A1 (en) Validating control of domain zone
US8117439B2 (en) Issuing secure certificate using domain zone control validation
Babakian et al. Internet Identifiers: A Survey of History, Challenges, and Future Perspectives
CN105245626A (zh) 在专网中使用快捷域名实现网站寻址的方法
US11233767B1 (en) System and method for publishing DNS records of a domain including either signed or unsigned records
Kabelova et al. DNS in action: A detailed and practical guide to DNS implementation, configuration, and administration
Ali et al. DNS Using BIND and DHCP
KR100994764B1 (ko) 도메인 네임 웹 관리방법
Wenzel et al. Guide to Administrative Procedures of the Internet Infrastructure
Ishioka The Domain Name System: An Integral Part of the Internet
Aitchison An Introduction to DNS
Everhart et al. Using DNS SRV to Specify a Global File Namespace with NFS Version 4

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG 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 MA MD MG MK MN MW MX MZ NA NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SM SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): BW GH GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LT LU MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
NENP Non-entry into the national phase

Ref country code: DE

WWW Wipo information: withdrawn in national office

Country of ref document: DE

WWE Wipo information: entry into national phase

Ref document number: 2005714677

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 200580017548.6

Country of ref document: CN

WWP Wipo information: published in national office

Ref document number: 2005714677

Country of ref document: EP