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/50—Address allocation
  • H04L61/5061—Pools of addresses

Definitions

• the present invention relates to the general domain of domain name servers in a telecommunication network.
• This architecture introduces the notion of "domain”, to designate a group of machines on the network.
• Figure 1 shows such an architecture.
• the domains., .Fr, .corn, ft.com and rd.ft.com contain subdomains.
• the domain ft.com has in this example three subdomains, namely www.ft.com, rd.ft.com and user.ft.com.
• terminal domains The domains that appear underlined in Figure 1 are called "terminal domains".
• a terminal domain - can represent one or more physical machines, this is for example the case of the terminal domain www.rd.ft.com;
• a domain that includes at least one subdomain is associated with a "domain server", otherwise called "name server”.
• This domain server has a zone file.
• the domains are logically connected to one another, which makes it possible, by querying the name servers step by step, starting with the root server (in English "root server"), to obtain the DNS data of any domain.
• information refers in particular to the Internet Protocol (IP) address of a domain, a text box, or any field (CNAME, 7) associated with a domain.
• IP Internet Protocol
• CNAME any field
• update operations which are added to the traditional reading operations (directory function) considerably increase the number of transactions handled by these servers.
• these transactions require synchronization operations of the master and slave servers, which also consume resources on the network.
• domain name servers are hosting more and more data, and larger and larger areas.
• the invention aims to respond to the problem mentioned above.
• a domain server in a telecommunications network adapted to manage DNS queries relating to the domain comprising means for receiving, from a client device, a request to obtain a DNS data of this domain.
• the server includes:
• a zone file comprising at least one distribution rule defining a partition of all the subdomains of the domain into a plurality of sub-areas, the DNS data of each of the sub-areas being hosted by a server, called a "partition server",
• zone designate all the data hosted within a server
• domain designate the logical entity
• the partition servers are "child servers" of the domain name server, otherwise designated by the expression "parent server”.
• the invention thus makes it possible to host the data of a domain in a plurality of child servers that define a partition of the subdomains of this domain.
• the parent server can keep part of the data of his domain. The skilled person will understand that it is not, as the
• DNS already allows it, to manage the same zone in its entirety by several servers, but to fragment a domain in small zones more easily administrable by the servers of domain names.
• the invention makes it possible in particular to separate the data management logic of a domain from its implementation.
• the heart of the invention lies more precisely in the zone file read by the server. Also, the invention aims, according to a second aspect, a data structure constituted by a computer file that can be read by a domain server in a telecommunications network (1).
• This file contains:
• partition servers each of them hosting the DNS data of a sub-area.
• the administrator of a zone defines a logical partition of a domain, which amounts to distributing the subdomains of this domain into different groups, each group being hosted either by a child server or by the parent server.
• the computer file according to the invention mainly comprises a list of the identifiers of the partition servers (that is to say the child servers and possibly the parent server), and a distribution rule to identify a particular partition server adapted to provide the desired DNS data.
• the useful information returned by the server to redirect its client can be of different types.
• it can include at least one of:
• the at least one distribution rule accompanied by the names or aliases of the partition servers, the name of the appropriate partition server, and
• the invention also relates to a client computer system of a domain name server in a telecommunications network, comprising means for sending to said server a request to obtain a DNS data of this domain.
• This client computer system comprises means for interpreting a regular expression received in response to the request, this interpretation enabling it to obtain the name of a partition server capable of responding to the request.
• the client device can query this server to obtain the data sought, progressing step by step as is customary in the use of the DNS architecture.
• the useful information further comprises the address of the partition server associated with at least one of the aforementioned elements.
• the distribution rule for identifying the partition server is a regular expression
• the domain name server includes means for interpreting this regular expression to obtain the address of the partition server and send the partition server to the client device.
• a regular expression can be defined as a line of computer code defining the search for a pattern ("pattern" in English) within a string of characters.
• This particularly advantageous feature greatly facilitates the task of users who do not have a client device according to the invention, suitable for interpreting regular expressions.
• the invention relates to a method for managing DNS queries relating to a domain in a telecommunications network comprising a step of receiving, from a client device, a request to obtain a DNS data item of this domain.
• the process comprises;
• a step of reading a zone file comprising at least one rule defining a partition of all the subdomains of the domain in a plurality of sub-zones, the DNS data of each of the sub-zones being hosted by a server, called "partition server”,
• the invention also relates to a method of obtaining a DNS data of a domain in a telecommunications network, this method comprising a step of sending a request to obtain the data.
• This method comprises a step for interpreting a regular expression received in response to the request, and for obtaining, from this interpretation, the name of a partition server capable of responding to the request.
• the different steps of the management method and the method of obtaining are determined by instructions of computer programs.
• the invention also relates to computer programs on an information medium, these programs being capable of being implemented in a computer, in a domain name server or in a client device, these programs comprising instructions adapted to the implementation of a method of managing domain names or a method of obtaining data as briefly mentioned above.
• These programs can use any programming language, and be in the form of source code, object code, or intermediate code between source code and object code, such as in a partially compiled form, or in any other form desirable shape.
• the invention also relates to a computer-readable information medium or a domain name server, and comprising instructions of at least one computer program as mentioned above.
• the information carrier may be any entity or device capable of storing the program.
• the medium may comprise storage means, such as a ROM, for example a CD ROM or a microelectronic circuit ROM, or a magnetic recording medium, for example a floppy disk or a disk. hard.
• the information medium can be a transmissibie medium such as an electrical or optical signal, which can be conveyed via an electrical or optical cable, by radio or by other means.
• the program according to the invention can be downloaded in particular on an Internet type network.
• the information carrier may be an integrated circuit in which the program is incorporated, the circuit being adapted to execute or to be used in the execution of the method in question.
• Appendices 1 and 2 represent the main lines of a zone file of a father domain name server according to the invention in two embodiments;
• Appendix 3 shows the main lines of a zone file of a child domain name server according to the invention in a preferred embodiment
• FIG. 1, already described, represents an example of a tree of DNS domains known to those skilled in the art
• FIG. 2 represents a telecommunications network comprising a parent domain name server according to the invention and two partition servers;
• FIG. 3 represents, in flowchart form, the main steps of a domain name management method according to the invention in a preferred embodiment
• FIG. 4 represents, in flowchart form, the main steps of a method for obtaining data according to the invention in a preferred embodiment.
• FIG. 2 represents a telecommunications network 1 and an nsl domain name server managing a domain (or zone) zl.com.
• this zone zl.com is divided into several sub-zones.
• a distribution rule which in this example divides the subdomain names of the zl.com domain as follows:
• FIG. 2 shows means 10 for receiving and sending data on the telecommunications network 1, these means being example constituted by a network card associated with drivers managing the http protocol (Hyper Text Transfer Protocol), and conventional processing means 20 of a computer, namely in particular a processor, a memory containing computer programs, and a random access memory to temporarily store the necessary variables of execution of these programs.
• http protocol Hyper Text Transfer Protocol
• the processing means of the server ns1 are adapted to execute the instructions of a computer program implementing the main steps ElO to E50 of the management method according to the invention shown in FIG. 3.
• the means 20 for processing the client device CL1 are adapted to execute the instructions of a computer program implementing the main steps F10 to F30 of the method of obtaining DNS data according to the invention shown in FIG. figure 4.
• step FlO of FIG. 4 the client CL1 sends (step FlO of FIG. 4), using the communication means 10, a request to the domain name server nsl of the IP address 10.193.161.50 to obtain the IP address of the subscript. domain.zl.com domain, also rated
• This request may for example be of the type
• This request is received in step E10 of FIG. 3 by the means 10 for receiving the nsl domain name server.
• the DIG command does not include a type, it means that the data sought by the client is a data of type A, namely the IP address of domain domain2.zl.com.
• the name processing means 20 of the server ns1 are adapted to read, during a step E20, the zone file FZ1. zone defining the zl.com zone management by this nsl server.
• This zone file FZl.zone can for example be stored in a memory 30 of the server nsl. It can also be stored in another machine.
• the main lines of this FZl.zone zone file are given in Appendix 1.
• This file comprises in particular lines L9 and LlO having the identifiers nsl-partl and nsl-part2 partition servers that manage the DNS data zone zl.com.
• lines L6 and L7 of the zone file FZl.zone include a distribution rule for, in this example, to redirect the client CLl: - to the server nsl-partl.zl.com for any request to obtain a data associated with a subdomain whose first letter is between "a" and "m", and - to the server nsl-part2.zl.com for others.
• the "regexp" field contains a regular expression to which the request issued by the client must be substituted. This result is the next request to be issued by the client.
• the regular expression is constituted by a test which then makes it possible to indicate the name of the server which hosts the data sought.
• Appendix 2 comprises the main lines of a zone file FZlb.sys of the server nsl according to the invention in a second embodiment.
• This zone file differs from the previous one in that the redirection indication is placed in the field "regexp", ie "replacement” field being empty.
• NAPTR Noise Autority Pointer
• the "service” field is defined in RFC 3403. This is a string of characters that allows the client to identify the processing that must be done by him.
• the service D2NS is introduced in order to inform the client how the fields of the rule stated in the NAPTR field should be interpreted.
• the NAPTR field would be the following one:
• the NAPTR field would be for example the following:
• the advantage of not including the name of the rule as a domain name is to guarantee that the set of rules will be at the root of the zone, and to avoid a misinterpretation of the domain name relating to the rule. .
• the client can determine if the name referred to by the NS type field is a domain name or distribution rule.
• the interest of including the rule as a domain name is to specify the name of the domain on which the next query will be made.
• the following interrogation relates to the field with the type A.
• the interrogation relates to the NAPTR type field.
• the ns field of the server managing the partitions points to a domain name that must follow a query on a type A field. This is no longer the case in the zone files according to the invention.
• the field ns refers to an NAPTR type field, in which the distribution rules (lines L6 and L7) are located.
• the creation of a new type of field could be considered instead of using the NAPTR field as described in this embodiment.
• the processing means of the server nsl are adapted to interpret (step E30) the regular expressions of the lines L6 and L7 to obtain, from the name domain2.zl.com, the nsl-partl name of the partition server that hosts the desired DNS data.
• the processing means 10 of the server nsl are adapted to obtain, during a step E40, useful information to redirect the client CLl to the partition server nsl-partl .
• This useful information can be of different types. It may for example include the rule of distribution l_6, L7.
• the useful information obtained by the server nsl can also include the name (nsl-partl, zl.com) of the partition server.
• alias of this server may be part of the useful information to redirect the CLl client to the partition server hosting the data. this field, namely in this case nslpart2.zLcom.
• the useful redirection information also includes the IP address 10.193161.30 of a partition server, associated at least with one of the distribution rule L6, L7, the name nsl-part2 of the partition server. partition server or the server alias of this server.
• a response comprising the useful information obtained during steps E30 and E40 is sent, during a step E50, by the server of name ns1 to the client CL1.
• the quote CL1 receives this response during a step F20 shown in FIG. 4,
• the response to the DIG query mentioned above can take one of the following forms;
• QUERY status: IMOERROR, id: 21511 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 4 ;; QUESTION SECTION: Domain, zl.com, IN
• the processing means 20 of the client device CL1 are adapted to interpret, if necessary, the distribution rule L6, L7 contained in the response.
• the client device CL1 determines by this interpretation that the name of the partition server containing the data sought is nsl-partl.
• the useful redirection information contained in the response is handled by the CLl client which recognizes that it must query the nsl-partl.zl.com server for the IP address of the domain2.zl domain. com.
• it transmits (step FlO) a request that is received, during a step ElO, by the communication means 20 of the son server nsl-partl.
• zone file FZl-partl.zone that manages the partition of the nsl-partl server is given in Appendix 3.
• the child server nsl-partl reads (step E20) the zone file FZl-partl.zone and obtains (step E40) the address 10.193.161.33 domain domain2.zl.com (see line L13 of Annex 3). This address is sent during the step E50 to the CLl client.
• the zone file In the embodiment described here, the zone file
• FZl.partl.zone of the nsl-partl child server also contains the information to redirect the CLl client if it has incorrectly interrogated the nsl-partl server, for example to obtain data associated with a subdomain name whose the letter begins, for example, with the letter "t".
• the nsl-partl child server returns information that allows the CLl client to query the correct server, namely nsl-part2.
• the response of the server nsl-partl is in this case of the form:
• nsl IN NAPTR 100 50 «a» «D2NS» «! ⁇ [am] »nsl-partl .zl.com.
• nsl IN NAPTR 100 50 "a""D2NS""S ⁇ [n-2]" nsl-part2.zl.com.
• class type oorrddeerr pref flags service regexp replacement // LS nsl IN NAPTR 100 50 'a''D2NS''i ⁇ [am] insl-partl.zl.com.'"// L6 nsl IN NAPTR 100 50 « a » « "I ⁇ [ ⁇ -z] 'nsl part2 zl.com. ⁇ »IM

Landscapes

• Engineering & Computer Science (AREA)
• Computer Networks & Wireless Communication (AREA)
• Signal Processing (AREA)
• Computer And Data Communications (AREA)
• Information Transfer Between Computers (AREA)
• Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Applications Claiming Priority (2)

Publications (1)

Family

ID=37709492

Family Applications (1)

Country Status (4)

Families Citing this family (14)

Family Cites Families (20)

• 2007
  • 2007-05-10 EP EP07766024A patent/EP2052526A2/de not_active Withdrawn
  • 2007-05-10 WO PCT/FR2007/051244 patent/WO2007132112A2/fr active Application Filing
  • 2007-05-10 US US12/300,939 patent/US9130990B2/en not_active Expired - Fee Related
  • 2007-05-10 CN CN2007800174533A patent/CN101444072B/zh not_active Expired - Fee Related

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events