Classifications

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

Definitions

• a method and system for intelligent delegation of domain name system (DNS) resolution for domain name system, or distributed DNS resolution Access to a server on the INTERNET (web server, video server, mail server or other) from a client computer is generally performed after a process known as DNS resolution of the name or mnemonic address of the latter, for example «Www.wanadoo.fr.
• DNS resolution of the name or mnemonic address of the latter, for example «Www.wanadoo.fr.
• IP address In an IP address (INTERNET address), generally consisting of four bytes "193.152.122.103" identifying the machine incorporating this server on the network
• INTERNET in order to allow the physical connection of the client station to this server.
• This DNS resolution process is implemented using the eponymous protocol (DNS protocol) and uses a recursion mechanism of the DNS resolution process.
• DNS protocol eponymous protocol
• the requesting client sends its request for resolution
• DNS to the DNS server of its INTERNET provider or company. If this server is not able to return an IP address corresponding to the server name to be resolved, it will in turn contact a parent DNS server (according to simple and well-known configuration rules) to ask this one to make the resolution and return the answer.
• the DNS resolution process conventionally makes it possible to return to the requesting client station and intermediate DNS servers either one or more response IP addresses, or an error message.
• the DNS servers having authority for a domain name, for which they ensure the resolution or final translation into an IP address are configured:
• IP address of the client station or subnet
• load servers for example.
• IP address of the client station or subnet
• These DNS systems are qualified as intelligent DNS systems, as they are able to return a response based on complex parameters and conditions, and not a single entry in a lookup table.
• the purpose of the DNS model is to define a consistent namespace for INTERNET resources to map a name to an IP address at a given time.
• This model is based on a tree system, capable of supporting high load growth and allowing each organization to manage its address space.
• each node is a domain and each domain is also a subdomain, except the root server.
• the servers managing the aforementioned model are classified according to three functional roles:
• - servers responsible for managing domains these servers are said to be iterative because they only answer questions about the areas they manage; - intermediate servers; still referred to as DNS caches, these optional servers are intended to store the most requested requests in order to speed up DNS resolution times;
• FIG. 1b The architecture of such a functional subdivision is shown in FIG. 1b.
• DNS queries present the data structure shown in Figure 1c.
• the OPCODE field is used by the client to indicate the nature of its request (name resolution, authentication), the RCODE field is used by the server to indicate if the client request was successful, and if not, the reason for failure.
• the data in the "referenced data" field corresponds to the name requested by a client or the name given by a server. This data is, in most cases, of the FQDN type for FuIIy Qualified Domain Name, ie a mnemonic address, www.francetelecom.fr for example.
• TTL parameter indicates the lifetime of the information. This data or parameter is used in particular by the DNS servers hidden to temporarily store the information.
• the data "class of registration" indicates the network in which the resource must be searched.
• the data "type of registration" allows to know the nature of the registration requested by the client or returned by the server.
• HINFO Home Information
• TXT for Text
• this type allowing a client or a DNS server to provide a free description, in the form of an ASCII character string.
• EDNSO a mechanism for extending DNS queries called EDNSO is defined by RFC 2671.
• This mechanism aims to remove some limitations of the DNS standard by creating new messages.
• the aforementioned extension mechanism is today mainly used to increase the maximum size of DNS queries and is essentially based on a modification of the OPCODE field and the use of a new type of resource called OPT.
• Bind the server developed by the Internet Software Consortium, whose members are behind several DNS extension protocols;
• Microsoft DNS server This server developed by Microsoft Corporation, became operational with the version supplied with the Windows 2000 ® operating system. This server easily integrating into a network local Microsoft is increasingly used in a corporate network context but remains less developed in the context INTERNET;
• this server is a royalty-free DNS server developed by NLnet Labs.
• NSD is a purely iterative server that has the particularity of compiling its zone files into automata. This compilation process allows him to respond immediately to a query, since all possible questions have been calculated and pre-established beforehand and all the answers have been pre-recorded.
• NSD is now more and more widespread and is used, in particular, as authoritative DNS for the management of high-level domains, Top Level Domains in English, that is to say domains roots whose extension is relative to a large area, country or group, such as ".fr”, “.ni” or other.
• the above-mentioned intelligent solutions enable the use of probes to measure different physical or network operating parameters ensuring the connection between a client and distributed server sites. Such as latency of the network, load of the sites servers proximity. Using these parameters, the aforementioned solutions evaluate, based on comparison criteria, in a group of responses, the one that appears most suitable for a given client and only return this response to the latter.
• CDN Content Delivery Networks in English
• the main players in this type of service being Akama ⁇ and Mirror Imager, for example;
• the main players being the companies F5 3-DNS server and CISCO for example.
• Intelligent servers able to find one or more IP addresses to solve a FQDN based on more or less complex algorithms, have the advantage of being able to respond to a client in an optimized and reliable manner but introduce the considerable disadvantage of managing from a centralized structure all the requests of the customers, and, therefore, to require a computation power proportional to both the transmission rate to ensure, the complexity of the resolution algorithm implemented and the parameters of resolutions involved, such as client IP address, server loads for example.
• Intermediate DNS servers also known as proxies, caches or relays, play only a role of resolution accelerator through Temporary storage mechanisms and execution of resolutions according to rules defined by RFC 1034 and 1035.
• the present invention relates to the implementation of an intelligent distributed DNS resolution method, at any extended intermediate relay server, with the aim of implementing the distributed DNS resolution method, and no longer only a process of distributing IP addresses between a relevant, authoritative parent server for a given domain name, and conventional DNS relay servers typically used between the client terminal and the relevant parent server.
• Another object of the present invention is, in addition to the implementation of the aforementioned method, the implementation of an extended intermediate relay server allowing, from a relevant parent server, the implementation of the distributed DNS resolution method. object of the invention, both the method and the aforementioned relevant parent server remaining fully compatible with the current standards in force and can advantageously complement them.
• Another object of the present invention is, finally, through the implementation of the method of the invention and a plurality of extended intermediary relay servers connected to an IP network, an INTERNET network or an enterprise network, to ensure a distribution of the computing power required for complex DNS resolutions on all or part of the deployed DNS server and relay relay tree, in order to make the data exchange traffic on the aforementioned tree structure more fluid.
• the distributed DNS resolution method of a DNS query comprising a domain name, transmitted between a client terminal and a relevant parent server, authoritative for the DNS resolution of this DNS request, object of the invention is remarkable in that it consists in transmitting from this client terminal to an extended intermediary relay server this DNS request for the DNS resolution of this request via this relevant parent server.
• this extended intermediate relay server in the absence of an earlier DNS resolution solution compatible with the domain name stored at this extended intermediate relay server, it consists of in addition to inserting in this DNS query a distribution extension variable of this DNS resolution to generate an extended DNS query and to transmit, from this extended intermediate relay server to this relevant parent server, the extended DNS request.
• the method of the invention is to search and / or establish a distributed DNS resolution agent and generate and transmit to this server intermediate relay extended an extended DNS response including at least this distributed DNS resolver.
• this extended intermediate relay server it finally consists in memorizing and executing this distributed DNS resolution agent to generate a DNS response comprising at least the IP address associated with this domain name and to transmit this DNS response to the client terminal.
• the extended intermediate relay server enabling the implementation of the distributed DNS resolution method of a DNS query comprising a domain name, object of the present invention, this DNS request being transmitted between a client terminal and a relevant parent server, is remarkable. in that it comprises at least one module for checking the presence of an earlier DNS resolution solution compatible with this domain name stored at this extended intermediate relay server, a storage and insertion module, in this DNS query, of a distribution extension variable of this DNS resolution making it possible to generate an extended DNS query, a transmission module of this extended DNS query to this relevant parent server, a storage and execution module of a distributed DNS resolver transmitted by this relevant parent server to this extended intermediate relay server, this execution allowing generating a DNS response comprising at least the IP address associated with this domain name, and a transmission module of this DNS response to this client terminal.
• the method and the extended intermediary relay server, objects of the present invention find application to the configuration of the architecture of the tree of servers and DNS relays deployed in the context of corporate networks or the INTERNET network. They will be better understood by reading the description and by observing the following drawings in which, in addition to FIGS. 1a to 1d relating to the prior art:
• FIG. 2 represents, by way of illustration, a general flowchart of the essential steps for implementing the distributed DNS resolution method, object of the present invention
• FIG. 3a represents, for purely illustrative purposes, a particular flow diagram of the steps for implementing the distributed DNS resolution method, object of the invention, in the case of a first situation where the DNS request is transmitted to the parent server. relevant via a relay server or conventional middle frame.
• FIG. 3b represents, for purely illustrative purposes, a particular flow diagram of the implementation steps of the distributed DNS resolution method that is the subject of the invention, in the case of a second situation where a prior solution of DNS resolution, compatible with the DNS request and in particular the domain name contained therein, is stored in a second higher level intermediate relay server higher than a first extended intermediary relay server in the tree of the relevant parent server in question;
• FIG. 3b represents, for purely illustrative purposes, a particular flow diagram of the implementation steps of the distributed DNS resolution method that is the subject of the invention, in the case of a second situation where a prior solution of DNS resolution, compatible with the DNS request and in particular the domain name contained therein, is stored in a second higher level intermediate relay server higher than a first extended intermediary relay server in the tree of the relevant parent server in question;
• FIG. 3b represents, for purely illustrative purposes, a particular flow diagram of the implementation steps of the distributed DNS resolution method that is the subject of the invention, in the case of
• 4a represents, by way of illustration, a particular flow chart for implementing the distributed DNS resolution method that is the subject of the invention, in the case where a first and then a second client terminal issue a DNS query relating to the same name of domain or to separate domain names that may however use known distributed sites and the distributed DNS resolution method object of the invention being implemented, for both situations, on a shared intermediate relay server and distributed distributed until at the lowest resolution level of extended intermediate relay servers vis-à-vis the relevant parent server;
• FIG. 4b represents, for purely illustrative purposes, a particular flow chart for implementing the distributed DNS resolution method that is the subject of the present invention, from a DNS Bind server specially adapted for implementing the aforementioned method; last to ensure maximum compatibility with existing traditional DNS servers;
• FIG. 5a represents by way of illustration a block diagram of an extended intermediate server, in accordance with the object of the present invention,
• FIG. 5b represents, for purely illustrative purposes, a functional flowchart representative of the operating mode of the extended intermediate server represented in FIG. 5a
• FIG. 5c represents, for purely illustrative purposes, a flowchart of the functional distribution steps of a distributed resolution agent A_R_D according to the subject of the present invention.
• - r_DNS a classic DNS request issued by the client from the aforementioned terminal T;
• SRE an extended intermediary relay server for implementing the method object of the present invention.
• an extended intermediate relay server SRE is a server having two new functionalities, namely a DNS resolution implementation signaling function distributed to any higher level intermediate relay server SRE, and than any relevant parent server SPP to perform the distributed DNS resolution, and a runtime function of a distributed resolution agent A_R_D established through the relevant parent server SPP mentioned above and under the conditions set by the latter, as well as it will be described later in the description.
• a DNS resolution implementation signaling function distributed to any higher level intermediate relay server SRE
• any relevant parent server SPP to perform the distributed DNS resolution
• a runtime function of a distributed resolution agent A_R_D established through the relevant parent server SPP mentioned above and under the conditions set by the latter, as well as it will be described later in the description.
• the method which is the subject of the invention concerns a request r_DNS comprising a domain name, that is to say a mnemonic designation of a machine still designated FQDN in English, this request being transmitted between the aforementioned terminal T, client terminal and of course, a relevant parent server SPP authoritative for the DNS resolution of the aforementioned request.
• step A of transmitting from the client terminal T to an extended intermediate relay server SRE the request r_DNS with a view to the DNS resolution of it through the relevant parent server SPP.
• step B When at the level of the intermediate intermediate relay server SRE there is no prior solution of DNS resolution compatible with the domain name contained in the request, internal solution stored at the level of the intermediate relay relay extended SRE, then, the method object of the It is particularly advantageous in a step B to insert in the request r_DNS a distribution extension variable, denoted EV, of this DNS resolution to generate an extended DNS request, which is denoted er_DNS.
• a distribution extension variable, denoted EV of this DNS resolution to generate an extended DNS request, which is denoted er_DNS.
• the insertion operation is represented by the relation r - DNS VE er DNS
• Operation B is then followed, at the SRE Extended Intermediate Relay Server, with a step C of transmitting the extended DNS query er_DNS from the SRE server to the relevant parent server SPP.
• the method which is the subject of the invention consists in executing a step D making it possible to evaluate the value of the extension variable VE of DNS resolution distribution at the true value.
• Step D itself then comprises an operation consisting of searching for and / or establishing a distributed DNS resolution agent, this agent being denoted by definition A_R_D.
• This agent advantageously consists of a software agent, as will be described later in the description.
• Step D is then followed by a step E executed at the server
• EA_DNS (A_R_D) and having at least the distributed DNS resolver, A_R_D.
• the method that is the subject of the invention then consists of a step F to be memorized and executed at the level of the aforementioned extended intermediary relay server.
• A_R_D resolution to generate a DNS response with at least the IP address designated @ IP associated with the previously mentioned domain name.
• the aforementioned DNS response is designated A_DNS (@IP).
• the method which is the subject of the invention then consists in a step G in transmitting the DNS response, A_DNS response (@IP) of the extended intermediate relay server SRE to the client terminal T.
• the terminal can then execute the connection requested by the client to the aforementioned address. This allows the execution of DNS resolution to be distributed at the extended relay server
• the distributed DNS resolution method which is the subject of the invention, is thus implemented by virtue of the definition of an extension of the conventional DNS protocol, this extension allowing the relays and DNS servers of indicate the support of the technology implemented, according to the method of the invention.
• the aforementioned extension is achieved by means of the distribution extension variable VE, this extension being able for example, without limitation, to reuse an existing type of resource, to take the form of a new OPT type DNS resource conforming to RFC 2671 or use a specific identifier in the OPCODE field of the request.
• the implementation of the aforementioned extension allows the relevant authoritative parent server SPP for a given FQDN to return a distributed resolution agent A_R_D, which may, by way of example nonlimiting, be realized in the form of a function written in Perl language to an intermediate intermediate relay server SRE which by definition allows the implementation of the method object of the invention.
• Each SRE extended intermediate relay server then makes it possible to implement the distributed DNS resolution by executing the distributed resolution agent A_R_D with each DNS request and in particular with each FQDN domain name associated with it being associated with a DNS agent.
• the main parent server SPP authoritative for the domain FQDN considered and implementing the method object of the invention executes a configuration method for defining which distributed resolution agent A_R_D must be returned to a DNS query, r_DNS, from a client to an SRE Extended Intermediate Relay Server.
• the functional diagram or situation presents the principle of implementation of the method that is the subject of the invention when none of the intermediate intermediate relay servers SRE has previously performed a DNS resolution, or when the resolution solution or A_R_D Resolver Resolved Lifetime has expired.
• FIG. 3a corresponds to a transmission situation of the DNS request r_DNS or, if appropriate, of an extended DNS request er_DNS via a conventional relay server designated for this reason SR, this type of server corresponding to a bin server for example.
• the method of the invention is to store and transmit the DNS query or the extended DNS request to the relevant parent server FPP. This makes it possible, of course, to ensure complete compatibility of the implementation of the method that is the subject of the present invention with the existing networks, the method that is the subject of the invention mentioned above being capable of being implemented independently of the number of relay servers.
• FIG. 3b shows a similar example in the case of a different client A 'using a first intermediate intermediate relay SRE1 and transmitting its DNS request after the client A in the case of Figure 3a to the intermediate intermediary relay server SR substituted by the intermediate server SREi mentioned above, the extended intermediate relay server SRE 2 of Figure 3b then playing the specific role of the SER server relay server extended intermediate of Figure 3a but in a different situation in which there is a priori resolution solution prior to the transmission of the request by the client A '.
• FIGS. 4a and 4b Various technical results obtained and a detailed description of a specific mode of implementation of the method of the invention will now be given in connection with FIGS. 4a and 4b.
• the method which is the subject of the invention makes it possible to propagate not only conventional DNS resolutions, ie one or more IP addresses, but, on the contrary, distributed resolution agents A_R_D .
• the aforementioned resolving agents are software agents written in a common programming language, grammar and rules, and respecting the RFC 1034 and 1035 documents in the construction of the DNS responses, in particular as regards the duration life of the resolutions.
• Distributed resolution agent propagation thus reduces the load on intelligent central DNS servers by offloading the computational load required for resolution to lower-level DNS servers and / or relays.
• distributed resolutions agents A_R_D also makes it possible to offer a fine-resolution intelligence that makes it possible to take into account the IP address of the client when the distributed resolution agent A_R_D can be propagated to the first level of the network.
• DNS resolution that is to say the DNS relay of the ISP, for example, that no current DNS resolution solution is able to allow.
• a principle of recursion can be implemented in the distributed distributed resolution agents A_R_D, allowing them to deliver in their turn no only one or more IP addresses but also all or part of themselves, as shown in Figure 4a above. Referring to Figure 4a, we consider the situation of two customers
• DNS A 'A each transmitting a request by transactions V respectively 1".
• Each client A 'and A is assumed for the purposes of the disclosure and in a nonlimiting manner, to implement the method which is the subject of the invention, in accordance with the situation of FIG. 3b, that is to say with from a first intermediate intermediate relay server SRE-i, separate for each of the clients A 'and A "and a second intermediate intermediate relay server SRE 2 , playing substantially the same role as in the case of Figure 3b.
• steps 1, 3b, 3c are replaced by transactions 1 ', 3'b, 3'c, an additional transaction 3'd intervening between the intermediate relay server SRE 2 and the main parent server SPP for distributed execution of transactions 4a and 4b.
• the latter can then be adapted according to the characteristics of the domain name required by the client A" and specificity of the terminal of the latter, for then execute the aforementioned ARD distributed resolution agent at the intermediary relay server SREi involved in the transaction requested by the client A ".
• the method which is the subject of the invention can be implemented in a nonlimiting manner by means of a DNS Bind server.
• An SRE extended intermediary relay server implemented from a bind DNS server enables the implementation of the method that is the subject of the invention with the aid of the modifications or adaptations hereafter: 1.
• This type of recording integrates two coded parameters in the form of character strings and is advantageously used for the implementation of the method that is the subject of the invention.
• reception by an SRE server or by the server
• this agent means a compiled version of the latter, for example: implementation of a DNS request processing function making it possible to detect the presence of the variable VE in the HINFO record containing the value VE ⁇ "DNSLET" and thus to differentiate the extended DNS queries with respect to the DNS queries and respond to it either by a classical DNS response or by an extended DNS response, that is to say containing a distributed resolution agent A_R_D.
• a request processing function is implemented, which allows the call of a program (for example a program written in the TXT text language) upon receipt of a DNS request when such a program has been associated to the FQDN domain name to resolve.
• a program for example a program written in the TXT text language
• Table 4 below shows the correspondence between the steps in Figure 2 and the transactions implemented in this situation.
• the step of transmitting from the relevant parent server to the extended intermediate relay server SRE at least the distributed DNS resolution agent also consists in transmitting a variable representative of the lifetime of this distributed DNS resolver, in order to ensure sound management of computing resources and memory space of any SRE extended intermediate relay server implemented in accordance with the object of the present invention.
• the relevant parent server SPP may be constituted by a conventional server, known to those skilled in the art, and for this reason, will not be described in detail.
• an SRE server can be implemented from a relay server Bind. Consequently, the server SRE comprises, as represented in FIG. 5a, all the conventional elements of a aforementioned server and in particular a SCPU server central unit connected to an input I / O output unit which, of course, allows the interconnection of the server. server with any external machine, a RAM RAM and of course a mass storage unit, permanent memory unit such as hard disk or other.
• the latter advantageously comprises a programmable memory nonvolatile protected write / read, designated P_MEM and a base of correspondence between a plurality of names domain and at least one distributed DNS resolution agent, correspondence base denoted B2, and a correspondence base B1 between a plurality of domain names and at least one IP address.
• P_MEM programmable memory nonvolatile protected write / read
• B2 correspondence base
• B1 correspondence base between a plurality of domain names and at least one IP address.
• the permanent hard disk-type memory comprises software modules, which make it possible to implement all the functionalities of the SRE server both with regard to the process of inserting the variable VE c that is, the HINFO resource indicating the extended DNS distribution and more particularly the declaration of availability for implementation of the distributed DNS resolution method at the aforementioned SRE extended intermediate relay server when the variable VE is at the true value .
• the above-mentioned software modules also make it possible to implement the process of constructing an extended query er_DNS or an extended response EA_DNS under the conditions that have been explained in the description above.
• the intermediate intermediate relay server SRE object of the invention may advantageously include a module for checking the presence of a prior DNS resolution solution compatible with the domain name and stored at the extended intermediate relay server, a module of storing and inserting in the DNS query of the DNS resolution distribution extension variable EV to generate an extended DNS request, query er_DNS, a transmission module of the extended DNS request to the relevant parent server, a module for storing and executing a distributed DNS resolver transmitted by the relevant parent server SPP to the intermediate relay relay server SRE as shown in FIGS. 5a and 5b.
• This makes it possible to generate the DNS response including at least the IP address associated with the aforementioned domain name FQDN.
• a module for transmitting the DNS response to the client terminal T is also provided.
• the aforementioned modules are software modules, from which the central computing unit SCPU and the input-output unit I / O make it possible to transmit the corresponding messages in the format as described above in the description for example.
• modules for checking the presence of an earlier DNS resolution solution modules for storing and inserting the DNS query of a distribution extension variable VE
• these modules also relate to modules specific software stored in the aforementioned permanent memory, which are executed by the central computing unit SCPU.
• agent A_R_D via the computing resources of the server SRE namely, the working memory RAM and the central computing unit
• A_R_D or any piece of information to compile the latter.
• a test 102 is provided to verify the existence of a previous stored resolution.
• a test 102a is called, consisting in building the answer A_DNS for transmission to the terminal T.
• a step 104 is called, which consists in constructing an extended request er_DNS, this step consisting, for example, in a step 105 of insertion of the resource HINFO indicating the extended DNS distribution, c that is, the insertion of the variable VE.
• the operating mode of the server SRE is then considered in the case where a DNS request to another server / DNS relay is received in step 106 and then receiving an extended response containing of course an algorithm, that is to say that is, a distributed resolution agent A_R_D.
• a test 108 is provided to verify that the aforementioned extended response contains an algorithm.
• the process of the operating mode is returned to the test of the step 102.
• the step 104 of construction of a request makes use of the correspondence base B1 allowing the setting in correspondence with the FQDN domain name and at least one IP address compatible with the latter.
• test 109 On a positive response to the test 108, as well as on a positive response to the aforementioned test 101, that is to say in the presence of at least one algorithm that is a distributed resolution agent A_R_D, a test 109 is called, consisting in checking the presence of the extension variable VE.
• a step 110 is called the execution of the algorithm after compilation of the latter, that is to say the distributed resolution agent A_R_D, this step 110 being followed by a step 111 of constructing the response.
• A_DNS that is to say communication in fact the IP address @IP compatible with the FQDN domain name and constituting the desired DNS resolution.
• step 111 the construction of the response involves the communication of either an algorithm or an algorithm and an IP @ IP address.
• the DNS response 1 A_DNS can then be transmitted at step 112 to the terminal T.
• a step 113 is called, which may consist of executing the distributed resolution agent A_R_D without transmission. This step 113 is then followed by the call to step 102 for the construction of the response.
• This last mode of operation can correspond to that described previously in the description, in connection with FIG. 4a in which the execution of the distributed resolution agent A_R_D 'makes it possible to distribute portions of algorithm or distributed resolution agent.
• the distribution process of the distributed DNS resolver A_R_D it may advantageously be constituted by a program module executable by a computer comprising, for example, as represented in FIG. extract from a DNS query or an extended DNS query parameters or conditions related to the initiator of the request, the client user, or environmental such as time of issue of the request, existence at the true value of the resolution distribution extension variable, client IP address @ 1P_C for example.
• the executable program module allowing the distribution of the distributed resolution agent A_R_D comprises a test 201 of support for implementing the method which is the subject of the invention, which can for example, to verify the true value of the DNS resolution distribution extension VE variable.
• a step 202 is called to return the distributed resolution agent A_R_D to the extended intermediate relay server SRE, author and user of the extended DNS request.
• a process of diversification of the DNS response from environmental parameters can advantageously be implemented.
• a first test 203 may consist of discriminating the value of the client address associated with the FQDN domain name in a specific range of values, the values 0.0.0.0 and 192.0.0.0 for example.
• the domain name associated with the Internet address is a first diversified value @IPi for example.
• a new test 204 is provided, which makes it possible to discriminate the time of transmission of the DNS query with respect to at least one hour threshold value, 12h00 in the example given.
• the domain name associated with the Internet address in step 206 is a second diversified value @IP 2 for example.
• the domain name associated with the Internet address in step 205 is a third diversified value @IP 3 for example. It is conceivable that the diversification of the domain name transmitted to the client user in the DNS response advantageously makes it possible to take account of the usual access conditions of the customer to distinct domain names according to the aforementioned environmental parameters.

Landscapes

• Engineering & Computer Science (AREA)
• Computer Networks & Wireless Communication (AREA)
• Signal Processing (AREA)
• Data Exchanges In Wide-Area Networks (AREA)

Applications Claiming Priority (2)

Publications (1)

Family

ID=34953507

Family Applications (1)

Country Status (3)

Families Citing this family (14)

Family Cites Families (7)

• 2005
  • 2005-08-25 US US11/664,694 patent/US20080288470A1/en not_active Abandoned
  • 2005-08-25 WO PCT/FR2005/002144 patent/WO2006037865A1/fr active Application Filing
  • 2005-08-25 EP EP05798592A patent/EP1797696A1/de not_active Withdrawn

Non-Patent Citations (2)

Also Published As

Similar Documents

Legal Events