JP2009194883A - Name resolution requesting device, name resolution repeating device, and name solving method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a name resolution repeating device for decentralizing the processing load on a name solving device which manages a large amount of name resolution information without changing a name resolution object that a communication device transmits. <P>SOLUTION: The name resolution repeating device which is connected to a plurality of name resolving devices that manage different zones respectively and answers addresses corresponding to a hierarchical domain identifier included in a name resolution request including the hierarchical domain identifier comprising a plurality of domain identifiers, generates a name resolution request and, when an identifier of a predetermined zone change object is included in a sub-domain identifier included in the hierarchical domain identifier included in the generated name resolution request, changes a domain identifier to be referred to when a name resolution device which resolves the name of the hierarchical domain identifier is selected among the domain identifiers included in the hierarchical domain identifier into a domain identifier corresponding to a name resolution device managing a zone as a change destination, and transmits the name resolution request to a corresponding name resolution device. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a name resolution request apparatus, a name resolution relay apparatus, and a name resolution method for making a name resolution request by DNS.

Conventionally, when performing communication on a computer network, there is a method of performing name resolution by DNS (Domain Name System) as a method for specifying the address of another communication device with which the communication device communicates. Such DNS is defined in RFC (Request for Comments) 1034 (Non-Patent Document 1) and RFC 1035 (Non-Patent Document 2) as a standard name resolution mechanism in a TCP / IP (Transmission Control Protocol / Internet Protocol) network. Has been widely used.
In such a DNS, a name resolution device (DNS server) manages name resolution information belonging to a specific domain and name resolution information of subdomains of the domain. Here, the management of the name resolution information of the subdomain may be delegated to other name resolution devices, and a plurality of name resolution devices hierarchized in this way function as a distributed database system to realize DNS Is done. Here, the management unit and management area of the name resolution information by the name resolution device are called zones.

  In addition, networks that employ DNS can perform name resolution as a series of processes using domain names obtained by linking domain names of different networks in layers. For example, when connecting a domain B network in which another name resolution device performs zone management to a domain A network in which a certain name resolution device performs zone management, a hierarchical domain identifier that links domain B as a subdomain of domain A Domain B belonging to domain A can be expressed by “domain B. domain A”.

For example, FIG. 7 is a diagram showing an example of a hierarchical structure of domains and zones managed by the name resolution device. The name resolution device 1200-1 uses the domain “abc.com” as a management area (zone), and delegates management of the domain “isp.abc.com” to the name resolution device 1200-2. The name resolution device 1200-2 includes name resolution information of the domain “isp.abc.com”, its subdomain “jp”, subdomain “org”, subdomain “net”, and subdomain “com”. Is managing. Further, the name resolution device 1200-1 delegates the management of the subdomain “group.abc.com” to the name resolution device 1200-3.
RFC1034, [online], [searched on December 11, 2007], Internet URL: http://www.ietf.org/rfc/rfc1034.txt?number=1034 RFC1035, [online], [December 11, 2007 search], Internet URL: http://www.ietf.org/rfc/rfc1035.txt?number=1035

  However, as described above, since name resolution information belonging to a specific domain is managed by a specific name resolution device, the name resolution information belongs to a domain managed by the name resolution device even if the name resolution information belongs to a large amount. The resolution apparatus cannot be divided, and the load of the name resolution information storage area and the load of the name resolution processing for transmitting the name resolution result in response to the name resolution request cannot be distributed. For this reason, a name resolution device that manages a zone of a large-scale network, in particular, manages a large amount of name resolution, which causes pressure on hardware resources of the name resolution device, a reduction in processing speed, and complicated management. it is conceivable that.

  For example, when the name resolution information belonging to the subdomain “jp” increases when the subdomain “jp” is connected to the lower layer of the domain “isp.abc.com” as in the example of FIG. For example, the name resolution device that manages the domain of the subdomain “www1” can be added to the lower layer of the subdomain “jp”. If the management of the subdomain “www1.jp.isp.abc.com” is delegated to the added name resolution device, the management burden of the name resolution device that performs zone management of the subdomain “jp” can be distributed. .

  On the other hand, if name resolution information belonging to the domain “isp.abc.com” increases, it is possible to add a subdomain “z” to the domain “isp.abc.com” to distribute the load. In this case, it is necessary to add “z” to the domain names of all subdomains belonging to “isp.abc.com” (“jp.z.isp.abc.com”, “com.z.isp.com”). abc.com "). As described above, when the subdomain “z” is added to the domain “isp.abc.com”, the influence extends to all subdomains that are lower layers of the domain “isp.abc.com”. Also, since it is necessary to change the name resolution target sent by all communication terminals that use all the subdomains, avoid adding subdomains to higher layer domains such as “isp.abc.com”. Is desirable.

  Therefore, when a large number of domains that do not include “.” Are registered in a specific zone, the name resolution processing of a large number of domains can be stabilized by improving the hardware capability of the name resolution device that manages the zone. However, there is a limit to the name resolution ability by improving the hardware ability.

  The present invention has been made in view of such circumstances, and for distributing the processing burden of a name resolution device that manages a large amount of name resolution information without changing the name resolution target transmitted by the communication device. A name resolution request device, a name resolution relay device, and a name resolution method are provided.

  In order to solve the above-described problem, the present invention manages different zones and receives a name resolution request including a hierarchical domain identifier composed of a plurality of domain identifiers. A name resolution request unit connected to a plurality of name resolution units that respond to corresponding addresses, and that generates a name resolution request including a hierarchical domain identifier composed of a plurality of domain identifiers, and a name resolution request unit An identifier determination unit that determines whether or not a predetermined zone change identifier is included in a subdomain identifier included in the hierarchical domain identifier included in the name resolution request generated by the name resolution request, and the identifier determination unit includes the hierarchical domain identifier If it is determined that the sub-domain identifier included in includes a predetermined zone change identifier Among the domain identifiers included in the hierarchical domain identifier, the domain identifier referred to when selecting a name resolution device that performs name resolution of the hierarchical domain identifier is the domain identifier corresponding to the name resolution device that manages the zone to be changed And an identifier conversion unit that converts to a name resolution request including the hierarchical domain identifier converted by the identifier conversion unit.

  In addition, the present invention provides a communication device that transmits a name resolution request including a hierarchical domain identifier composed of a plurality of domain identifiers and a zone included in the name resolution request when each manages a different zone and receives the name resolution request. A name resolution relay device connected to a plurality of name resolution devices that respond to addresses corresponding to domain identifiers, including a reception unit that receives a name resolution request from a communication device, and a name resolution request received by the reception unit An identifier determining unit that determines whether or not a predetermined zone change target identifier is included in the subdomain identifier included in the read hierarchical domain identifier, and the identifier determining unit includes the hierarchical domain identifier If it is determined that the sub-domain identifier included in includes a predetermined zone change identifier, Of the domain identifiers included in the layer domain identifier, the domain identifier referred to when selecting a name resolution device that performs name resolution of the hierarchical domain identifier is changed to a domain identifier corresponding to the name resolution device that manages the zone to be changed. An identifier conversion unit for conversion, and a name resolution relay unit that transmits a name resolution request including a hierarchical domain identifier converted by the identifier conversion unit to a corresponding name resolution device.

  Further, according to the present invention, the name resolution relay device described above stores a corresponding identifier stored in advance by associating a predetermined zone change target identifier with a domain identifier corresponding to the name resolution device that manages the change destination zone. The identifier determination unit reads a predetermined zone change target identifier stored in the corresponding identifier storage unit, and makes a determination based on the read zone change target identifier.

  In the present invention, the name resolution relay unit described above receives the name resolution result from the name resolution device in response to the name resolution request transmitted to the name resolution device, and receives the name resolution result received by the name resolution relay unit. , Further comprising a name resolution result transmitter for transmitting to the communication device

  In addition, the present invention manages a plurality of different zones, and when receiving a name resolution request including a hierarchical domain identifier made up of a plurality of domain identifiers, responds with a plurality of addresses corresponding to the hierarchical domain identifier included in the name resolution request. A name resolution method for a communication device connected to a name resolution device, wherein the name resolution request unit generates a name resolution request including a hierarchical domain identifier composed of a plurality of domain identifiers, and the identifier determination unit includes a name A step of reading out a hierarchical domain identifier included in the name resolution request generated by the resolution request unit and determining whether or not a predetermined zone change target identifier is included in the subdomain identifier included in the read hierarchical domain identifier And the identifier conversion unit performs the sub-step included in the hierarchical domain identifier by the identifier determination unit. When it is determined that the main identifier includes a predetermined zone change target identifier, the domain identifier included in the hierarchical domain identifier is referred to when selecting a name resolution device that performs name resolution of the hierarchical domain identifier. A domain identifier corresponding to a name resolution device that manages a zone to be changed, and a name resolution device corresponding to a name resolution request that includes a hierarchical domain identifier converted by the identifier conversion unit. And the step of transmitting to.

  As described above, according to the present invention, when the sub-domain identifier of the hierarchical domain identifier included in the name resolution request includes a predetermined zone change target identifier, the domain identifier included in the hierarchical domain identifier Of these, the domain identifier referenced when selecting a name resolution device that performs name resolution of the hierarchical domain identifier is converted into a domain identifier corresponding to the name resolution device that manages the zone to be changed, and the converted hierarchical domain identifier is Since the included name resolution request is transmitted to the corresponding name resolution device, the name resolution device that transmits the name resolution request can be changed according to the identifier included in the subdomain identifier of the hierarchical domain identifier.

Hereinafter, an embodiment of the present invention will be described with reference to the drawings.
FIG. 1 is a diagram showing the concept of zones managed by a name resolution system using a name resolution relay device according to the present invention. In this embodiment, the name resolution device 200-4 that performs zone management of the domain “abc.com” and the name resolution device 200- that performs zone management of the subdomain “isp.abc.com” of the domain “abc.com”. 1 and a name resolution device 200-2 that performs zone management of the subdomain “isp2.abc.com” of the domain “abc.com”, and a zone of the subdomain “group.abc.com” of the domain “abc.com” A hierarchical domain is formed by the name resolution device 200-3 that performs management.
Here, the name resolution device 200-1 performs zone management of the subdomain “jp” and the subdomain “org” for the domain “isp.abc.com”, and the name resolution device 200-2 also has the domain “isp.abc”. The sub-domain “net” and the sub-domain “com” for “.com” are zone-managed. Such a zone range is determined, for example, by a predetermined domain range stored in a zone file stored in the storage area of the name resolution device 200.

  Next, an embodiment for performing name resolution of a hierarchical domain identifier indicating the domain hierarchy described in FIG. 1 will be described. FIG. 2 is a block diagram showing the configuration of the name resolution system according to this embodiment. The name resolution system according to the present embodiment includes a name resolution relay device 100, a name resolution device 200-1, and a name resolution device 200-2 (hereinafter, in the description, when any one of them is shown as a representative, the name resolution Device 200), name resolution information cache device 400, line termination device 500-1, line termination device 500-2 (hereinafter, in the description, when any one of them is shown as a representative, line termination device 500. And an information terminal 600-1 and an information terminal 600-2 (hereinafter, in the description, when any one of them is shown as a representative, it is referred to as an information terminal 600). The name resolution device 200, the line termination device 500, and the information terminal 600 will be described by taking two units as an example, but a configuration in which three or more units are used may be applied.

The information terminal 600 makes a name resolution request to the name resolution device 200 via the name resolution relay device 100 connected via the line termination device 500.
The information terminal 600-1 is a computer terminal used by a user, and includes an input unit, an output unit, a control unit, a calculation unit, and a storage unit. The information terminal 600-1 is provided with an identifier indicating that the communication service provider contracted in advance uses the network of the provider, and is input and stored by the user. Here, the identifier given to the information terminal 600-1 is “user@youro.ne.jp”. “User” is an identifier of a user who uses the information terminal 600-1, and “youro.ne.jp” is a network identifier of a communication service provided to the user. Specifically, a PC (personal computer), a PDA (Personal Digital Assistant), or the like is applied to the information terminal 600-1.
The information terminal 600-2 has the same configuration as the information terminal 600-1, and the identifier given by the service provider is “user@miyazaki.com”.

  The line termination apparatus 500-1 is an apparatus that connects the name resolution relay apparatus 100 and the information terminal 600-1 via a line, and includes a name resolution request transmission unit 501-1. The line terminator 500-1 includes a line identifier “eX” indicating the type of the line to which the line terminator 500-1 is connected, and an area identifier “osaka” indicating the area where the line terminator 500-1 is installed. In addition, a connection identifier of a service identifier “isp” indicating the type of service provided by the line and a management identifier “abc.com” indicating the management domain of the network is stored in advance.

  When the power is turned on or when a network connection request is received from the information terminal 600-1, the name resolution request transmission unit 501-1 of the line termination device 500-1 specifies the address of the gateway device to be connected, for example. In order to do this, a two-digit number indicating the number of characters of the label is added to the beginning of each label (identifier) included in the network identifier “youro.ne.jp” stored in the information terminal 600-1, The domain identifier “05youro02ne02jp” obtained by concatenating and converting “.” Is generated and labeled. Then, the line terminating device 500-1 connects the generated domain identifier and the previously stored connection identifier with a dot “.” To form a hierarchical structure, and forms a hierarchical domain identifier “05yo020202jp.eX.osaka as shown in FIG. .Isp.abc.com ". The name resolution request transmission unit 501-1 transmits a name resolution request to the name resolution information cache device 400 using the generated hierarchical domain identifier as a name resolution target. The hierarchical domain identifier generated here is FQDN. The FQDN is a fully qualified domain name, and is a domain name completely described from a host name to a TLD (Top Level Domain) in a name space in DNS (Domain Name System). In DNS, such a FQDN is configured to uniquely identify its corresponding address.

  The line termination apparatus 500-2 is an apparatus that connects the name resolution relay apparatus 100 and the information terminal 600-2 via a line. Like the line termination apparatus 500-1, a line identifier “eX” that indicates a line domain is used. In addition, a regional identifier “osaka” indicating a regional domain, a service identifier “isp” indicating a service domain, and a management identifier “abc.com” indicating a network management domain are stored in advance as connection identifiers. When the name resolution request transmitting unit 501-2 of the line termination device 500-2 generates a name resolution request in order to specify the address of the gateway device 700 to be connected, the name resolution request transmission unit 501-2 uses the same rules as the line termination device 500-1. , A name resolution request is made with the hierarchical domain identifier “08miyazaki03com.eX.osaka.isp.abc.com” as the name resolution target.

  The name resolution information cache device 400 performs a cache that temporarily stores information related to name resolution. That is, the name resolution information cache device 400 associates the name resolution target hierarchical domain identifier transmitted from the line termination device 500 with the address included in the name resolution result transmitted from the name resolution relay device 100 in association with its own device. If the address corresponding to the hierarchical domain identifier to be resolved included in the name resolution request received from the line termination device 500 is stored in the storage area of the local device, the address is The name resolution result is transmitted to the line terminating device 500 without transmitting the name resolution request to the name resolution relay device 100. On the other hand, the name resolution information cache device 400 transfers a name resolution request to the name resolution information cache device 400 when the address corresponding to the hierarchical domain identifier of the name resolution target is not stored in the storage area of the name resolution information cache device 400. . Also, the correspondence information between the hierarchical domain identifier and the address stored in the storage area of the name resolution information cache device 400 is deleted after a predetermined period of time has passed.

  The name resolution relay device 100 relays the name resolution communication between the line termination device 500 and the name resolution device 200, and the name resolution relay communication unit 101, the identifier conversion unit 102, the identifier determination unit 103, and the name resolution result transmission unit. 104, a session management unit 105, a name resolution request reception unit 106, and a correspondence identifier storage unit 107.

The name resolution request receiving unit 106 receives a name resolution request transmitted from the line termination device 500.
Correspondence identifier storage unit 107 stores, as a zone change target identifier, correspondence information that associates each subdomain identifier with a domain identifier of a domain that is an upper layer for each of a plurality of predetermined subdomain identifiers. . FIG. 4 is a diagram illustrating a data example of correspondence information stored in the correspondence identifier storage unit 107. In the present embodiment, the correspondence identifier storage unit 107 stores an identifier indicating the TLD included in the network identifier and a service identifier that is a higher layer domain in association with each other.

  Here, the TLD is a TLD defined by IANA (Internet Assigned Numbers Authority). Here, IANA is an organization that manages domain names and addresses in DNS, and TLD is a domain name defined by IANA as a domain name indicating the highest domain. Examples of TLDs include gTLDs (generic TLDs) such as “com” and “net”, sTLDs (sponsored TLDs) such as “aero” and “cop”, and ccTLDs such as “uk” and “jp” ( Country code TLD), iTLD (international TLD) such as “int”, and other special purpose TLD such as “gov” are defined.

  Here, as shown in FIG. 1, since the domain “net” belongs to the upper layer domain “isp2”, which is the service domain, as a subdomain, the domain identifier “net” is associated with the domain identifier “isp2”. It is done. Similarly, since the domain “com” belongs to the upper layer domain “isp2” as a subdomain, the domain identifier “com” is associated with the domain identifier “isp2”. The domains “jp” and “org” belong to the upper layer domain “isp” as subdomains, and this attribution is the same as the conventional configuration shown in FIG. Since there is no information, the correspondence information is not stored.

  The identifier determination unit 103 is an upper layer corresponding to the TLD included in the network identifier input by the user among the identifiers included in the hierarchical domain identifier indicating the name resolution target of the name resolution request received by the name resolution request receiving unit 106 It is determined whether the service identifier of the domain is stored in the correspondence identifier storage unit 107, and the determination result is output. Here, the identifier determination unit 103 determines whether or not the identifier of the upper layer domain corresponding to the TLD is stored in the corresponding identifier storage unit 107 using the identifier determined in the TLD in the DNS among the network identifiers as a key. To do.

  When the determination result output from the identifier determination unit 103 indicates that the upper layer domain identifier corresponding to the TLD is stored in the corresponding identifier storage unit 107, the identifier conversion unit 102 determines whether the upper layer The service identifier as the domain identifier is read, and the service identifier is converted into the service identifier read from the correspondence identifier storage unit 107 among the hierarchical domain identifiers included in the name resolution request.

  For example, when the name resolution relay device 100 receives a name resolution request from the line termination device 500-2 with the hierarchical domain identifier to be resolved as “08miyazaki03com.eX.osaka.isp.abc.com”, The identifier determining unit 103 determines that the TLD of the network identifier “08miyazaki03com” is “com” and the corresponding higher layer domain identifier is stored in the corresponding identifier storage unit 107. Then, the identifier conversion unit 102 reads the upper layer domain identifier “isp2” corresponding to the TLD “com” from the corresponding identifier storage unit 107, and among the hierarchical domain identifiers to be resolved, the service identifier indicating the type of the service domain “Isp” is converted into a service identifier “isp2” read from the corresponding identifier storage unit 107, and a hierarchical domain identifier “08miyazaki03com.eX.osaka.isp2.abc.com” is generated.

  When the session management unit 105 receives a name resolution request from the line termination device 500, the session management unit 105 performs session management for the name resolution. For example, the session management unit 105 registers and stores session information such as srcIP, srcPort, FQDN, query ID, authority section, and additional section of a DNS message, which is a name resolution request, in a storage area. Further, the session management unit 105 deletes the session information stored in the storage area when the name resolution relay device 100 transmits the name resolution result for the name resolution request to the line termination device 500.

The name resolution relay communication unit 101 transmits a name resolution request received from the line termination device 500 to the name resolution device 200. Further, the name resolution device 200 receives the name resolution result corresponding to the transmitted name resolution request and transmits it to the line termination device 500. Here, the name resolution relay communication unit 101 performs processing such as holding a session of name resolution communication performed with the line termination device 500 or the name resolution device 200.
The name resolution result transmission unit 104 transfers the name resolution result received by the name resolution relay communication unit 101 from the name resolution device 200 to the line termination device 500.

The name resolution device 200-1 receives a name resolution request whose target is a hierarchical domain identifier, responds with an address corresponding to the hierarchical domain identifier included in the received name resolution request, and receives a name resolution information storage unit 201- 1 and a name resolution unit 202-1.
The name resolution information storage unit 201-1 stores in advance name resolution information in which a domain identifier managed by the own device is associated with an address corresponding to the domain identifier. In the present embodiment, the name resolution information storage unit 201-1 is a network identifier belonging to the domain “isp.abc.com”, and has a domain identifier and address whose TLD of the network identifier is “jp” or “org” And remember. The name resolution information storage unit 201-1 stores, for example, the address “1234 :: 1” corresponding to the domain identifier “05youro02ne02jp.eX.osaka.isp.abc.com”.

  When receiving the name resolution request including the name resolution target domain, the name resolution unit 202-1 performs name resolution from the name resolution information storage unit 201 on the address associated with the name resolution target domain included in the received name resolution request. The information is read from the information storage unit 201-1, and a name resolution result including information in which the read address is associated with the name resolution target domain is transmitted to the transmission source of the name resolution request. In this way, the name resolution device 200-1 manages the zone by making a name resolution response by the name resolution unit 202-1 with the name resolution information stored in the name resolution information storage unit 201-1 as a range.

  The name resolution device 200-2 has the same configuration as the name resolution device 200-1, and includes a name resolution information storage unit 201-2 and a name resolution unit 202-2, but the name resolution information storage unit 201- 2 is a network identifier belonging to the domain “isp2.abc.com”, and stores a domain identifier and an address whose TLD of the network identifier is “com” or “net”. The name resolution information storage unit 201-2 stores, for example, an address “1234 :: 2” corresponding to the domain identifier “08miyazaki03com.eX.osaka.isp2.abc.com”.

<First operation example>
Next, with reference to FIG. 5, an example of an operation in which the name resolution relay device 100 according to the present embodiment relays communication related to name resolution between the line termination device 500-1 and the name resolution device 200-1 will be described. .
First, when a connection request to the network is input from the user to the information terminal 600-1, the line terminating device 500-1 labels the network identifier stored in the information terminal 600-1 according to a predetermined rule. To generate a domain identifier “05ouro02ne02jp”. In this label, a line identifier “eX”, a region identifier “osaka”, a service identifier “isp”, and a management identifier “abc” stored in the line terminating device 500-1. .Com ”is connected with a dot“. ”To generate a hierarchical domain identifier“ 05youro02ne02jp.eX.osaka.isp.abc.com ”.

  Then, the name resolution request transmission unit 501-1 of the line termination device 500-1 transmits a name resolution request for the generated hierarchical domain identifier as a name resolution target to the name resolution relay device 100 (step S1). When the name resolution request receiving unit 106 of the name resolution relay device 100 receives the name resolution request transmitted from the line terminating device 500-1, the identifier determination unit 103 is included in the name resolution target domain of the name resolution request. It is determined whether or not an upper layer domain identifier corresponding to the TLD of the network identifier is stored in the correspondence identifier storage unit 107 (step S2).

  When the identifier determination unit 103 determines that the upper layer domain identifier corresponding to the TLD of the network identifier included in the name resolution target domain of the name resolution request is not stored in the correspondence identifier storage unit 107, the session management unit 105 Performs session registration of the name resolution request (step S3), and transmits the name resolution request to the name resolution device 200-1 (step S4). When receiving the name resolution request transmitted from the name resolution relay communication unit 101 of the name resolution relay device 100, the name resolution device 200-1 receives the hierarchical domain identifier included in the name resolution request from the name resolution information storage unit 201-1. An address “1234 :: 1” corresponding to “05youro02ne02jp.eX.osaka.isp.abc.com” is read (step S5).

As a response to the name resolution request, the name resolution device 200-1 transmits a name resolution result including the hierarchical domain identifier included in the name resolution request and the address read in step S5 to the name resolution relay device 100 (step S6). ). When the name resolution relay communication unit 101 receives the name resolution result transmitted from the name resolution device 200, the session management unit 105 deletes the session registered in step S3. Then, the name resolution result transmission unit 104 transmits the name resolution result received by the name resolution relay communication unit 101 in step S6 to the line terminating device 500-1 (step S8). When receiving the name resolution result transmitted from the name resolution relay device 100, the line termination device 500-1 starts communication with the address included in the received name resolution result as the destination.
In this way, the line terminating device 500-1 can receive the name resolution result for the name resolution request.

<Second operation example>
Next, an operation example in which the name resolution relay device 100 according to the present embodiment relays name resolution between the line termination device 500-2 and the name resolution device 200-2 will be described with reference to FIG.
When a connection request to the network is input from the user to the information terminal 600-2, the line terminating device 500-2 labels the network identifier stored in the information terminal 600-2 according to a predetermined rule. A domain identifier “08miyazaki03com” is generated, and a line identifier “eX”, a region identifier “osaka”, a service identifier “isp”, and a management identifier “abc.com” stored in the line terminating device 500-2 are generated on this label. "Is connected with a dot". "To generate a hierarchical domain identifier" 08miyazaki03com.eX.osaka.isp.abc.com ".

  Then, the name resolution request transmission unit 501-2 of the line termination device 500-2 transmits a name resolution request for the generated hierarchical domain identifier as a name resolution target to the name resolution relay device 100 (step S1). When the name resolution request receiving unit 106 of the name resolution relay device 100 receives the name resolution request transmitted from the line terminating device 500-2, the identifier determination unit 103 is included in the name resolution target domain of the name resolution request. It is determined whether or not an upper layer domain identifier corresponding to the TLD of the network identifier is stored in the correspondence identifier storage unit 107 (step S12).

  When the identifier determination unit 103 determines that the upper layer domain identifier corresponding to the TLD of the network identifier included in the hierarchical domain identifier to be resolved is stored in the correspondence identifier storage unit 107, the session management unit 105 Then, session registration for name resolution is performed (step S13), and the identifier determination unit 103 transfers the name resolution request to the identifier conversion unit 102 (step S14). The identifier conversion unit 102 reads the upper layer domain identifier “isp2” corresponding to the TLD “com” of the network identifier included in the hierarchical domain identifier of the name resolution target from the correspondence identifier storage unit 107 and sets the name resolution request as the name resolution target of the name resolution request. The service identifier “isp” of a certain hierarchical domain identifier “08miyazaki03com.eX.osaka.isp.abc.com” is converted into the service identifier “isp2” read from the corresponding identifier storage unit 107 (step S15).

  Then, the name resolution relay communication unit 101 transmits to the name resolution device 200-2 a name resolution request with the hierarchical domain identifier “08miyazaki03com.eX.osaka.isp2.abc.com” converted in step S15 as a name resolution target. (Step S16). When receiving the name resolution request transmitted from the name resolution relay communication unit 101 of the name resolution relay device 100, the name resolution device 200-2 is the name resolution target of the name resolution request from the name resolution information storage unit 201-2. The address “1234 :: 2” corresponding to the hierarchical domain identifier “08miyazaki03com.eX.osaka.isp2.abc.com” is read (step S18).

Then, as a response to the name resolution request, the name resolution device 200-2 transmits a name resolution result including the hierarchical domain identifier included in the name resolution request and the address read in step S18 to the name resolution relay device 100 ( Step S19). Upon receiving the name resolution result transmitted from the name resolution device 200-2, the name resolution relay communication unit 101 deletes the session registered in step S13 (step S19). The name resolution relay device 100 also converts the hierarchical domain identifier “08miyazaki03com.eX.osaka before converting the identifier in step S15 into the hierarchical domain identifier“ 08miyazaki03com.eX.osaka.isp2.abc.com ”included in the name resolution result. .Isp.abc.com "(step S20). Then, the name resolution result transmission unit 104 transmits the name resolution result received by the name resolution relay communication unit 101 to the line terminating device 500-2 (step S21). When the line termination device 500-2 receives the name resolution result transmitted from the name resolution relay device 100, the line termination device 500-2 starts communication with the address included in the received name resolution result as a destination.
In this way, the line terminating device 500-2 can receive the name resolution result for the name resolution request.

In the above operation example, the correspondence identifier storage unit 107 stores the TLD of the network identifier and the service identifier in association with each other. However, the identifier of the upper layer domain is associated with the identifier of the lower layer domain. If present, the network identifier is not limited to the TLD and the service identifier.
In the above example, the name resolution relay device 100 and the name resolution device 200 have been described as a single device. However, considering the network environment, the number of terminals in the domain, the number of records of name resolution information, and the like. It is good as an optimal configuration.

  In the present embodiment, the name resolution request transmission unit 501 of the line termination device 500 converts the network identifier (for example, “you.ne.jp”) into one label according to a specific rule (for example, “05you02ne02jp”). However, the present invention can also be applied to cases where such single labeling is not performed. As a result, when a large amount of name resolution information is registered in the name resolution device that performs specific zone management, multiple name resolution devices are prepared and distributed to each name resolution device. It is possible to register and manage. For example, if there is a name resolution device that performs zone management of 999 types of domains from “srv001” to “srv999” as host names, if the name resolution information included in the domain increases in large quantities, “srv001” To “srv500” and “srv501” to “srv999”, zone management can be distributed, and name resolution information can be managed by different name resolution devices.

In the present embodiment, an example in which an IPv6 address such as “1234 :: 1” is stored in the name resolution information storage unit 201 of the name resolution device 200 has been described. The address to be stored may be an IPv4 address or both an IPv6 address and an IPv6 address.
In addition, it is not necessary to physically arrange each device and each functional unit described in the present embodiment as described above, and the person who implements the system can determine the number of users of the service, the maintenance system of the service, and the administrator. Can be configured flexibly in consideration of existing hardware resources.

In addition, the name resolution relay communication unit 101, the identifier conversion unit 102, the identifier determination unit 103,
The functional units of the session management unit 105 and the correspondence identifier storage unit 107 may be configured to be included in the line termination device 500, but each line termination device 500 is installed in a user's home or the like. If the name resolution relay device 100 is configured as in the present embodiment, it is considered that the present invention can be implemented at a lower management cost.

In the present embodiment, the zone is divided into the domain “jp” and the domain “org”, the domain “net”, and the domain “com”. However, the zone is divided into three or more, for example, “isp3. Management may be delegated to a name resolution device that performs zone management of “abc.com”.
Thus, according to the present invention, there is provided a name resolution relay device for distributing the processing burden of a name resolution device that manages a large amount of name resolution information without changing the name resolution target transmitted by the communication device. can do.

  Note that name resolution is performed by recording a program for realizing the function of the processing unit in the present invention on a computer-readable recording medium, causing the computer system to read and execute the program recorded on the recording medium. May be. Here, the “computer system” includes an OS and hardware such as peripheral devices. The “computer system” includes a WWW system having a homepage providing environment (or display environment). The “computer-readable recording medium” refers to a storage device such as a flexible medium, a magneto-optical disk, a portable medium such as a ROM and a CD-ROM, and a hard disk incorporated in a computer system. Further, the “computer-readable recording medium” refers to a volatile memory (RAM) in a computer system that becomes a server or a client when a program is transmitted via a network such as the Internet or a communication line such as a telephone line. In addition, those holding programs for a certain period of time are also included.

  The program may be transmitted from a computer system storing the program in a storage device or the like to another computer system via a transmission medium or by a transmission wave in the transmission medium. Here, the “transmission medium” for transmitting the program refers to a medium having a function of transmitting information, such as a network (communication network) such as the Internet or a communication line (communication line) such as a telephone line. The program may be for realizing a part of the functions described above. Furthermore, what can implement | achieve the function mentioned above in combination with the program already recorded on the computer system, and what is called a difference file (difference program) may be sufficient.

It is a figure which shows the outline | summary of the zone division | segmentation of the name resolution system by one Embodiment of this invention. It is a block diagram which shows the structure of the name resolution system by one Embodiment of this invention. It is a figure which shows the name resolution object domain identifier contained in the name resolution request | requirement which the line termination apparatus by one Embodiment of this invention transmits. It is a figure which shows the example of data memorize | stored in the corresponding | compatible identifier memory | storage part by one Embodiment of this invention. It is a sequence diagram which shows the operation example of the name resolution system by one Embodiment of this invention. It is a sequence diagram which shows the operation example of the name resolution system by one Embodiment of this invention. It is a figure which shows the outline | summary of the zone division | segmentation by a prior art.

Explanation of symbols

DESCRIPTION OF SYMBOLS 100 Name resolution relay apparatus 101 Name resolution relay communication part 102 Identifier conversion part 103 Identifier determination part 104 Name resolution result transmission part 105 Session management part 106 Name resolution request reception part 107 Corresponding identifier memory | storage part 200 Name resolution apparatus 201 Name resolution information memory | storage part 202 Name Resolution Unit 300 Name Resolution Information Management Device 400 Name Resolution Information Cache Device 500 Line Termination Device 501 Name Resolution Request Transmitter 600 Information Terminal 1200 Name Resolution Device

Claims (5)

A plurality of name resolution devices that manage different zones and respond with addresses corresponding to the hierarchical domain identifiers included in the name resolution request when a name resolution request including a hierarchical domain identifier including a plurality of domain identifiers is received. A name resolution requesting device connected to
A name resolution request unit that generates a name resolution request including a hierarchical domain identifier composed of a plurality of domain identifiers;
An identifier determination unit that determines whether or not a predetermined zone change identifier is included in a subdomain identifier included in the hierarchical domain identifier included in the name resolution request generated by the name resolution request unit;
When the identifier determination unit determines that the predetermined zone change identifier is included in the sub-domain identifier included in the hierarchical domain identifier, the hierarchy among the domain identifiers included in the hierarchical domain identifier An identifier conversion unit that converts a domain identifier referred to when selecting a name resolution device that performs name resolution of a domain identifier into a domain identifier corresponding to a name resolution device that manages a zone to be changed;
A transmission unit that transmits a name resolution request including the hierarchical domain identifier converted by the identifier conversion unit to the corresponding name resolution device;
A name resolution requesting device comprising: A communication device that transmits a name resolution request including a hierarchical domain identifier including a plurality of domain identifiers, and each managing a different zone, and when receiving the name resolution request, the hierarchical domain identifier included in the name resolution request A name resolution relay device connected to a plurality of name resolution devices that respond with corresponding addresses,
A receiving unit that receives the name resolution request from the communication device;
The hierarchical domain identifier included in the name resolution request received by the receiving unit is read, and it is determined whether or not a predetermined zone change target identifier is included in the subdomain identifier included in the read hierarchical domain identifier An identifier determination unit to perform,
When the identifier determination unit determines that the predetermined zone change identifier is included in the sub-domain identifier included in the hierarchical domain identifier, the hierarchy among the domain identifiers included in the hierarchical domain identifier An identifier conversion unit that converts a domain identifier referred to when selecting a name resolution device that performs name resolution of a domain identifier into a domain identifier corresponding to a name resolution device that manages a zone to be changed;
A name resolution relay unit that transmits a name resolution request including the hierarchical domain identifier converted by the identifier conversion unit to the corresponding name resolution device;
A name resolution relay device comprising: A correspondence identifier storage unit that prestores the identifier of the predetermined zone change target and the domain identifier corresponding to the name resolution device that manages the zone to be changed in advance;
3. The identifier determination unit reads the predetermined zone change target identifier stored in the corresponding identifier storage unit, and performs the determination based on the read zone change target identifier. The name resolution relay device described in 1. The name resolution relay unit receives a name resolution result from the name resolution device in response to a name resolution request transmitted to the name resolution device;
The name resolution according to claim 2, further comprising: a name resolution result transmission unit that transmits the name resolution result received by the name resolution relay unit to the communication device. Relay device. A plurality of name resolution devices that manage different zones and respond with addresses corresponding to the hierarchical domain identifiers included in the name resolution request when a name resolution request including a hierarchical domain identifier including a plurality of domain identifiers is received. A name resolution method for a communication device connected to
A name resolution request unit generating a name resolution request including a hierarchical domain identifier composed of a plurality of domain identifiers;
An identifier determining unit reads out the hierarchical domain identifier included in the name resolution request generated by the name resolution requesting unit, and is a predetermined zone change target identifier in the subdomain identifier included in the read out hierarchical domain identifier Determining whether or not is included;
When the identifier conversion unit determines that the predetermined domain change target identifier is included in the sub-domain identifier included in the hierarchical domain identifier by the identifier determination unit, the domain included in the hierarchical domain identifier Of the identifiers, converting a domain identifier referred to when selecting a name resolution device that performs name resolution of the hierarchical domain identifier into a domain identifier corresponding to a name resolution device that manages a zone to be changed; and
Transmitting a name resolution request including the hierarchical domain identifier converted by the identifier conversion unit to the corresponding name resolution device;
A name resolution method comprising:

Images