EP2052526A2

EP2052526A2 - Server and method for managing domain names in a network

Info

Publication number: EP2052526A2
Application number: EP07766024A
Authority: EP
Inventors: Daniel Migault
Original assignee: France Telecom SA
Current assignee: Orange SA
Priority date: 2006-05-17
Filing date: 2007-05-10
Publication date: 2009-04-29
Also published as: CN101444072A; CN101444072B; US20090113075A1; WO2007132112A2; US9130990B2; WO2007132112A3

Abstract

This domain server comprises a zone file comprising distribution rules which define a partition of all the sub-folders of this domain into a plurality of sub-zones. The DNS data of each of these sub-zones is hosted by a partition server. This domain server is able to obtain, from zone files, information which makes it possible to identify the partition server capable of responding to a request, transmitted by a client, with a view to obtaining a DNS folder.

Description

SERVER AND METHOD FOR MANAGING DOMAIN NAMES

IN A NETWORK

BACKGROUND OF THE INVENTION The present invention relates to the general domain of domain name servers in a telecommunication network.

In known manner, the management of the domain names in a network is carried out by the DNS architecture (in English "Domain Name System") defined by the RFC 1034 (in English "Request For Comments") of I ¹ IETF ("Internet Engineering Task Force ").

This architecture introduces the notion of "domain", to designate a group of machines on the network.

Figure 1 shows such an architecture. In known manner the domains., .Fr, .corn, ft.com and rd.ft.com contain subdomains.

For example, the domain ft.com has in this example three subdomains, namely www.ft.com, rd.ft.com and user.ft.com.

The domains that appear underlined in Figure 1 are called "terminal domains". In known manner, a terminal domain: - can represent one or more physical machines, this is for example the case of the terminal domain www.rd.ft.com;

- but also not to represent a physical machine, it is for example the case of the terminal domain user.ft.com which in this example is constituted by personal information of the user "user". In known manner, 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. In known manner, 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.

In this document, the term "information" refers in particular to the Internet Protocol (IP) address of a domain, a text box, or any field (CNAME, ...) associated with a domain. With the growing popularity of the Internet, domain name servers are becoming increasingly difficult to administer.

In particular, the update operations, which are added to the traditional reading operations (directory function), considerably increase the number of transactions handled by these servers. In addition, these transactions require synchronization operations of the master and slave servers, which also consume resources on the network.

In addition, domain name servers are hosting more and more data, and larger and larger areas.

Previously, the domain names had as little information as IP addresses, this data not exceeding twenty bytes. Today, DNS hosts much larger profiles (about 200 bytes), as in the case of ENUM services (as described in IETF RFC 2916), for example.

A known solution to this problem is to create subdomains, the name servers of these subdomains thus created hosting part of the data that was hitherto hosted by the domain from which they came. But this solution adds an extra level in the domain hierarchy, which results in a complication of the newly created subdomain name,

However, this complexity in the name of the subdomain can be perceived as a disadvantage, especially when the name of this subdomain is used for commercial or advertising purposes.

Object of the invention

The invention aims to respond to the problem mentioned above. For this purpose, it proposes, in a first aspect, 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",

means for obtaining, from the zone file, sufficient information, to identify the appropriate partition server capable of responding to the request; and

means for sending the useful information to the client device in response to the request.

In general, one speaks of zone to designate all the data hosted within a server, and of domain to designate the logical entity. Nevertheless, the terms "zone" and "domain" are often interchangeable in the literature.

In the remainder of this document, it will be considered that for the purposes of the invention, 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.

Of course, 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.

Very advantageously, 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:

lines defining at least one distribution rule of all the subdomains of the domain in a plurality of sub-areas;

- Lines comprising identifiers of a plurality of servers, called "partition servers", each of them hosting the DNS data of a sub-area. In practice, 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. itself, Also, 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.

For example, 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

- an alias of the appropriate partition server.

If the useful information is the dispatch rule, the client device, or its administrator, must interpret the distribution rule to determine the name of the partition server. Also, and according to a third aspect, 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.

Once it knows the name or alias of the partition server, 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.

Preferably, the useful information further comprises the address of the partition server associated with at least one of the aforementioned elements. In a preferred embodiment, the distribution rule for identifying the partition server is a regular expression, and 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.

It is recalled that, in known manner, 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.

Correlatively, 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, the 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",

a step of obtaining, from the zone file, sufficient information to identify the partition server capable of responding to the request; and

a step of sending said useful information to the client device in response to the request.

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.

According to a preferred implementation, the different steps of the management method and the method of obtaining are determined by instructions of computer programs. Accordingly, 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. For example, 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.

On the other hand, 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.

Alternatively, 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.

Brief description of the drawings

Other features and advantages of the present invention will become apparent from the description given below, with reference to the appendices and drawings which illustrate an embodiment of this embodiment devoid of any limiting character and in which:

- 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; and

FIG. 4 represents, in flowchart form, the main steps of a method for obtaining data according to the invention in a preferred embodiment.

Detailed description of an embodiment

FIG. 2 represents a telecommunications network 1 and an nsl domain name server managing a domain (or zone) zl.com. As mentioned above, to implement the invention, this zone zl.com is divided into several sub-zones. To do this, we use a distribution rule, which in this example divides the subdomain names of the zl.com domain as follows:

- the subdomain names whose first letter begins with a letter between "a" and "m" are hosted by the child server nsl-partl; and

- the subdomain names whose first letter begins with a letter between "n" and "z" are hosted by the child server nsl-part2. Thus, when a CLl client queries the nsl parent server to obtain a DHS data relating to the subdomain domain2.zl, com, this client receives, in response to this request, useful information that redirects it to the partition server nsl-partl, since the first letter of the name of this subdomain (domain2.zl, com) is the letter "d", included between the letters "a" and "m". For the client CL1 and for each of the nsl, nsl-partl and nsl-part2 domain name servers, 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.

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.

Similarly, 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.

We will assume that 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

IP (domaine2.zl.com)

This request may for example be of the type;

DIG 10.193.161.50 + norecurse domain2.zl.com, DIG (Domain Information Groper) being the tool known to those skilled in the art to query the domain name servers in the DNS architecture.

This request is received in step E10 of FIG. 3 by the means 10 for receiving the nsl domain name server.

Those skilled in the art will recognize that since 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.

After the step ElO for receiving the request from the client CL1, 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.

The lines conforming to the DNS standard and known to those skilled in the art will not be described here.

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.

Those skilled in the art will recognize, at line L9, that the address of the server nsl-partl. zl.com on the network 1 is 10.193.161.73 (field A), and that server 1 is an alias (CNAME field) of the partition server nsl- part2.zl.com, the address of this partition server on the network 1 being

10.193.161.30, as shown online LlL

In addition, 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.

Specifically, 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.

According to the invention, 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.

Only lines L6 and L7 differ from zone file FZ1. area of Annex 1.

This zone file differs from the previous one in that the redirection indication is placed in the field "regexp", ie "replacement" field being empty.

Alternatively, one could also decide to specify a new service, in order to avoid any interpretation on the nature of the distribution rule ("service" is the logic that the client must adopt in order to correctly resolve the request). Thus, by choosing the "D2NS" sign (Domain to Name Server), the NAPTR (Naming Autority Pointer) field would be as follows:

class type flags service regexp replacement nsl IN NAPTR "a""D2NS""i ^Λ [am]! πsl-partl.zl.com.!"

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. In this variant, 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.

Alternatively, one could also decide to specify the name of the distribution rule as an argument of the function of the service, in order to avoid any interpretation on the nature of the distribution rule. Thus, by choosing the "D2NS" sign (Domain to Name Server), the NAPTR field would be the following one:

class type flags service regexp replacement

IN NAPTR «a» «D2NS! Nsl!» «! ^A [am]! Nsl-partl.zi.com.! "

Alternatively, it could also be decided to specify the name of the distribution rule in the regexp field, in order to avoid any interpretation as to the nature of the distribution rule. So, in choosing the "D2NS" (Domain to Name Server) acronym, the NAPTR field would be for example the following:

class type fags regexp service replacement

IN NAPTR «a» «D2NS! Nsl!» «! ^Λ [am]! \\: nsl: nsl ~ partl.zl.com.! "

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. .

It is then preferable that 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. Traditionally, the following interrogation relates to the field with the type A. In the invention, the interrogation relates to the NAPTR type field.

According to the traditional DNS, 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.

In the preferred embodiment described here, the field ns refers to an NAPTR type field, in which the distribution rules (lines L6 and L7) are located. Of course, the creation of a new type of field could be considered instead of using the NAPTR field as described in this embodiment.

The fact that the field ns associated with the domain name zl.com does not point to a field of type A is a characteristic element of a zone file according to the invention.

The presence of distribution rules is another. In a preferred 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.

Anyway, according to the invention, 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.

It can also include an alias of this server. Thus, assuming that the CLl client queries the nsl server with a domain name beginning with the letter "r", the alias "serverl" 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.

In a preferred embodiment, 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.

Returning to FIG. 3, 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,

Specifically, the response to the DIG query mentioned above can take one of the following forms;

; << >> DiG 9.3.1 << >> domain.zl.com ;; global options; printcmd ;; Got answer:

;; - »HEADER« - opcode; QUERY, status: IMOERROR, id: 21511 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 4 ;; QUESTION SECTION: Domain, zl.com, IN

;; ANSWER SECTION: domaine.zl.com. 300 IN A 212.78.202.252

;; AUTHORITY SECTION: zl.com. 80394 IN NS nsl

ADDITIONAL SECTION:

class type order pref flags service regexp replacement nsl IN NAPTR 100 50 "a""""! ^Λ [am]" nsl-partl. zl.com nsi IN NAPTR 100 50 "a""""! ^Λ [nz]" nsl-paιt2.zlxom

ns-partl.zLcom. IN A 10.193.161.73 nsl-part2.zl.com. IN CNAME serverl server! IN A 10.193.161.30

;; Query time: 91 msec; SERVER: 10.193.117.254 # 53 (10.193.117.254); WHEN: Fri Apr 22 16:14:46 2005 ;; MSG SIZE rcvd: 217

According to the invention, the processing means 20 of the client device CL1 are adapted to interpret, if necessary, the distribution rule L6, L7 contained in the response.

In this case, the client device CL1 determines by this interpretation that the name of the partition server containing the data sought is nsl-partl. Anyway, 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. For this purpose, it transmits (step FlO) a request that is received, during a step ElO, by the communication means 20 of the son server nsl-partl.

The zone file FZl-partl.zone that manages the partition of the nsl-partl server is given in Appendix 3.

Upon receipt of this request, 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.

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".

In this case, the nsl-partl child server returns information that allows the CLl client to query the correct server, namely nsl-part2.

Preferably, the response of the server nsl-partl is in this case of the form:

zl.com. IN ns nsl class type order pref flags service regexp Replacement 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.

nsl-partl, .zl xom. IN A 10.193, 161.73 nsl-part2, .zl .corn. IN A 10.193,, 161.30

Note that this case is a case of abnormal operation, because the client has read the distribution rule before querying the partition server, since the rule was communicated to him. ANNEX 1

FZl.zone

$ TTL 86400 // Ll zl.com. IN SOA local host. root, loca I host {} // L2

zl.com. IN ns nsl // L3 zl.com IN ns nsO // L4

class type order pref flags service regexp replacement // L5 nsl IN NAPTR 100 50 «a» «» ^w ! ^Λ [am] "nsl-partl.zl.com // L6 nsl IN NAPTR 100 50" a """"! ^A [nz] "nsl-part2, zlxom HU

nsl-partl .zl .corn. IN A 10. 193.161.73 // L9 nsl-part2 .zl .com. IN CNAME serverl // LlO

server IN A 10. 193.161.30 // LU nsO IN A 10, 193.161.30 // L12

ANNEX 2

FZlbis.zone

$ TTL 86400 // Ll zl.com, IN SC localhost.rootlocalhost {} IM

zl.com IN ns nsl IM zl.com IN ns nsO // L4

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

nsl-partl.zl.com. IN A 10.193.161.73 // L9 nsl-part2.2l.com. IN CNAME serverl // LlO

server IN A 10.193.161.30 // LU nsO IN A 10.193.161.30 IMl

ANNEX 3

FZl-partl.zone

$ TTL 86400 // Ll zl.com. IN SOA localhost.root.Iocalhost {// L2

} // L3

zl.com. IN ns nsl // L4

class type order pref flags service regexp replacement // 15 nsl IN NAPTR 100 50 «a» «D2NS» «! ^A [am] >> nsl-partl.2l.com. // L6 nsl IN NAPTR 100 50 «a» «D2NS» «! ^Λ [nz] >> nsl-part2.zl.com. IM

nsl-partl.zl .corn. IN A 10. 193.161.73 // 19 nsl-part2.zl .com. IN A 10. 193.161.30 // LlO

$ ORIGIN zl. cornfieldel IN A 10.193.161 .31 // L12 c! omainne2 ÏN A 10.193.161 .33 // L13

Claims

A domain (nsl) server (zl.com) in a telecommunications network (1) adapted to manage the DNS queries relating to said domain (zl.com), comprising means (10) for receiving, from a client device (CLl), a request to obtain a DIMS data (IP (domaine2 .zl.com)) of this domain, said server being characterized in that it comprises: a zone file comprising at least one rule of partition defining a partition of all the sub-domains (domainel.zl.com, dornaine2.zl.com) of said domain (zl.com) into a plurality of sub-areas, the DNS data of each of said sub-areas being hosted by a server, called "partition server", - means (10) for obtaining, from said zone file, sufficient information, to identify the appropriate partition server capable of responding to said request; and

means (10) for sending said useful information to the client device (CL1) in response to said request.

2. Server according to claim 1, characterized in that said useful information comprises at least one of:

said at least one distribution rule (L6, L7) accompanied by the names (nsl-partl, nsl-part2) or aliases (serverl, server2) of said partition servers,

The name (nsl-part2) of said appropriate partition server, and

an alias (server2) of said appropriate partition server.

3. Server according to claim 2, characterized in that said useful information further comprises the address (10.193.169.73,

10.193.169.30) of said appropriate partition server.

4. Server according to any one of claims 1 to 3, characterized in that said distribution rule (L6, L7) is a regular expression for obtaining the address of said partition server adequate.

Computer file capable of being read by a domain server (nsl) (zl.corn) in a telecommunications network (1), characterized in that it comprises: lines (L6, L7) defining at least a distribution rule of the set of subdomains (domainei.zl.com, domatne2.zl.com) of said domain (zl.com) in a plurality of sub-areas;

lines (L9, LlO) comprising identifiers (nsl-partl, nsl-part2) of a plurality of servers, called "partition servers", each of them hosting the DNS data of a said sub-area .

A method for managing DNS queries relating to a domain (zl.com) in a telecommunications network (1) comprising:

a step (ElO) of receiving, from a client device (CL1), a request to obtain a DNS data (IP (domain2.zLcom)) of this domain; said method being characterized in that it comprises:

a step (E20) for reading a zone file (FZ1, zone), said file comprising at least one distribution rule defining a partition of all the subdomains (domainel.zl.com, domain2.zl .com) of said domain (zl.com) into a plurality of sub-areas, the DNS data of each of said sub-areas being hosted by a server, said "partition server",

a step of obtaining (E30, E40), from said zone file (FZ1, zone), sufficient information to identify said partition server capable of responding to said request; and

a step (E50) of sending said useful information to said client device (CL1) in response to said request.

A computer program comprising instructions for performing the steps of the management method according to claim 6 when said program is executed by a computer.

A computer-readable recording medium on which a computer program is recorded including instructions for executing the steps of the management method according to claim 6.

9. Client computer system (CLl) of a server (nsl) of domain names (zl.com) in a telecommunications network (1), comprising means for sending to said server (nsl) a request to obtain data DNS (IP (domaine2.zl.com)) of this domain, characterized in that it comprises means (20) for interpreting a regular expression (L6, L7) received in response to said request, this interpretation allowing it to obtain the name of a partition server (nsl-partl) capable of responding to said request.

10. A method for obtaining a DNS data of a domain (zl.com) in a telecommunications network (1), this method comprising a step of sending a request to obtain said data item, this method being characterized in that it comprises a step for interpreting a regular expression (L6, L7) received in response to said request, and for obtaining, from this interpretation, the name of a partition server (nsl-partl) capable of to respond to the said request.

A computer program comprising instructions for performing the steps of the method of obtaining data according to claim 10, when said program is executed by a computer.

12. A computer-readable recording medium on which is recorded a computer program comprising instructions for performing the steps of the method of obtaining data according to claim 10.