JP6442545B2 - DNS server, black list generation method in DNS server, and black list generation program used for DNS server - Google Patents

Description

  The present invention relates to a DNS server, a black list generation method in a DNS server, and a black list generation program used for the DNS server for executing name resolution processing while suppressing processing load in a dual stack environment.

  In recent years, communication using an IP network may be performed in a dual stack environment in which protocols of IPv4 and IPv6 are mixed.

  In a dual stack environment, when accessing a network of a different protocol, for example, a user terminal in an IPv6-compatible closed network (hereinafter referred to as “IPv6 closed network”) is connected to an IPv4-compatible wide area network (hereinafter referred to as “IPv4”). When accessing a Web server in a "wide area network"), the user terminal once queries the DNS (Domain Name System) server in the IPv6 closed network for name resolution, and sends a Refused response (rejection response) to this. When received, the ISP-DNS server in the IPv4 wide area network is accessed.

  As described above, even when accessing the IPv4 wide area network, if the DNS server in the IPv6 closed network performs processing for the inquiry, there is a problem that the processing load of the DNS server in the IPv6 closed network increases. Therefore, there is a technique of installing a hardware detection device for detecting and filtering access from hardware (user terminal) that is a target of a Refused response, upstream of the DNS server in the IPv6 closed network.

  This hardware detection apparatus holds in advance a DNS black list in which domain names that reject processing related to name resolution are registered. Then, when an IPv4 address name resolution inquiry request is made, if the address includes a domain name registered in the DNS blacklist, the requesting terminal is accessed without accessing the DNS server. Send a Refused response.

  With this configuration, it is possible to reduce the processing load on the DNS server in the IPv6 closed network.

JP 2005-229234 A Japanese Patent Laid-Open No. 2015-220483

  In the hardware detection apparatus described above, the capacity of information stored in the DNS blacklist is limited, and the number of domain names that can be registered and the size of information are limited. For this reason, only the common part of the domain name subject to the Refused response is registered as the minimum information to be detected for filtering, and a name resolution inquiry request for the domain name including the registered common part is made. Refused is responding when it is broken.

  However, if only information on the minimum common part is registered in the DNS blacklist in this way, the common part may be included in the domain name registered as the name resolution processing target in the DNS server. is there. In this case, in the hardware detection device, it is necessary to individually set the domain name so as to permit access to the DNS server without making a Refused response. By performing the setting in this way, it is possible to achieve consistency between the processing executed in the DNS server and the processing executed in the hardware detection device.

  However, since the DNS server and the hardware detection device are configured independently, the period from when the common part of the domain name is registered in the DNS blacklist until the access permission is set in the hardware detection device. In some cases, a period in which processing consistency is not achieved in both apparatuses may occur. When this period occurs, there is a problem that a Refused response is made without executing the process even if a name resolution process related to a domain name registered as a name resolution process target is requested to the DNS server.

  Also, since registration of the DNS blacklist is performed manually, there is a problem that it takes time.

  The present invention has been made in view of the above circumstances, and in a dual stack environment, a DNS server, a black list generation method in a DNS server, and a DNS server for efficiently and reliably executing a name resolution process with a reduced processing load, An object of the present invention is to provide a black list generation program used for a server.

In order to solve the above problems, the DNS server of the present invention stores, as DNS record information, correspondence information between a domain name and an IP address registered for performing a name resolution process for resolving an IP address from a domain name. A DNS record information storage unit, a response log information storage unit for storing log information of a response process for a DNS query transmitted to designate a domain name and request a name resolution process, and the DNS record information storage unit DNS that acquires stored DNS record information, and adds a negative value of an absolute value larger than the maximum value of the number of response log information that can be stored in the response log information storage unit as a point value to each DNS record information Record information acquisition unit and rejection of response log information stored in the response log information storage unit for each domain name at predetermined time intervals From the match list generated by the match list generation unit and the match list generated by the match list generation unit, a domain name is generated using the number of answers as a point value and the DNS record information acquired by the DNS record information acquisition unit. Generates tree structure information that shows multiple domain names with a common end character string, with each character of as a node, the common character at the end of the domain name as the highest node, and the first character as the lowest node. The point value of the corresponding domain name is added as the point value of the corresponding node to each lowest node in the information of the tree structure, and the total value of the point values of the latest lower nodes is added to each node other than the lowest node From the tree structure information generated by the tree structure information generation unit and the tree structure information generation unit For a node whose point value is a positive value and the point value of the nearest higher node is a negative value, extract the common character string part including the node and its higher node, and the common character string part is A blacklist generation unit that generates a blacklist and a blacklist storage unit that stores a blacklist generated by the blacklist generation unit as rejection partial domain information that is a target of a rejection response to a DNS query that is generated thereafter. It is characterized by providing.

Further, the black list generation method in the DNS server of the present invention stores the correspondence information between the domain name and the IP address registered for performing the name resolution processing for resolving the IP address from the domain name as DNS record information. A DNS server comprising: a record information storage unit; and a response log information storage unit that stores log information of a response process for a DNS query transmitted to specify a domain name and request a name resolution process. DNS record information stored in the information storage unit is acquired, and for each DNS record information, a negative absolute value larger than the maximum number of response log information that can be stored in the response log information storage unit is a point value. And the rejection information for each domain name of the log information stored in the response log information storage unit at a predetermined time interval. Using the number as a point value, generate a match list that matches the acquired DNS record information. From the generated match list, each character of the domain name is a node, and the common character at the end of the domain name is the top node. Generate the tree structure information indicating multiple domain names with the same terminal character string with the character of the lowest node as the lowest node, and point value of the corresponding domain name to each lowest node in the tree structure information Is added as the point value of the corresponding node, and the total value of the point values of the latest lower nodes is added to each node other than the lowest node as the point value of the corresponding node. Is a positive value, and for the node whose point value of the nearest higher node is negative, the common statement including the node and its higher node Extracting a sequence part, generating the black list as rejection part domain information that is a target of a rejection response to a DNS query generated thereafter, and storing the generated black list To do.

The black list generation program used for the DNS server of the present invention is a DNS record that stores correspondence information between a domain name and an IP address registered in the DNS server in order to perform name resolution processing for resolving an IP address from the domain name. DNS record information storage function for storing information, a response log information storage function for storing log information of response processing for a DNS query transmitted to specify a domain name and request name resolution processing, and the DNS record information DNS record information stored by the storage function is acquired, and for each DNS record information, a negative absolute value larger than the maximum number of response log information that can be stored by the response log information storage function is used as a point value. DNS record information acquisition function to be added and the response log information storage function at predetermined time intervals A match list generation function for generating a match list matched with the DNS record information acquired by the DNS record information acquisition function, using the number of rejection responses for each domain name of the response log information stored as a point value; and the match From the match list generated by the list generation function, each character of the domain name is a node, a common character at the end of the domain name is the highest node, and the first character is the lowest node. Generate the tree structure information indicating the domain name of each, and add the point value of the corresponding domain name as the point value of the corresponding node to each lowest node in the information of the tree structure. Tree structure information generation that adds the total point value of the latest lower nodes to the node as the point value of the corresponding node. From the function and the tree structure information generated by the tree structure information generation function, for a node whose point value is a positive value and the point value of the most recent upper node is a negative value, A black list generation function that extracts a common character string portion including a node, and generates the black list as rejection partial domain information that is a target of a rejection response to a DNS query that is generated thereafter; And a black list storage function for storing the black list generated by the black list generation function.

  According to the DNS server, the black list generation method in the DNS server, and the black list generation program used in the DNS server of the present invention, it is possible to efficiently and reliably execute name resolution processing while reducing the processing load in a dual stack environment. It becomes possible.

1 is an overall view showing a configuration of a communication system using a DNS server according to a first embodiment of the present invention. It is a flowchart which shows the process performed when the DNS server by 1st Embodiment of this invention receives a DNS query. It is a flowchart which shows the process performed when the blacklist production | generation timing comes in the DNS server by 1st Embodiment of this invention. It is a table | surface which shows an example of the high-order domain list | wrist of the response log information produced | generated by the DNS server by 1st Embodiment of this invention. (A)-(d) is a table | surface which shows an example of the high-order domain list | wrist for every group produced | generated with the DNS server by 1st Embodiment of this invention. (A)-(c) is the state which stored the character which comprises each domain name in the high-order domain list | wrist of the predetermined group produced | generated with the DNS server by 1st Embodiment of this invention in the table for every domain level. It is explanatory drawing shown. It is a table | surface which shows an example of the black list produced | generated by the black list production | generation part of the DNS server by 1st Embodiment of this invention. It is a table | surface which shows an example of the existing black list memorize | stored in the black list memory | storage part of the DNS server by 1st Embodiment of this invention. It is a table | surface which shows an example of the collision list produced | generated by the collision list production | generation part of the DNS server by 1st Embodiment of this invention. It is a table | surface which shows an example of the DNS record information memorize | stored in the DNS server by 1st Embodiment of this invention. It is a table | surface which shows an example of the collision list updated by the black list update part of the DNS server by 1st Embodiment of this invention. It is a table | surface which shows the state which the counter value of the black list memorize | stored in the black list memory | storage part of the DNS server by 1st Embodiment of this invention was reset. It is a flowchart which shows the process performed when the new correspondence information is added to the DNS record information in the DNS server by 1st Embodiment of this invention. It is a general view which shows the structure of the communication system using the DNS server by 2nd Embodiment of this invention. It is a flowchart which shows the process performed when the blacklist production | generation timing comes in the DNS server by 2nd Embodiment of this invention. It is a table | surface which shows an example of the high-order domain list | wrist of the response log information produced | generated with the DNS server by 2nd Embodiment of this invention. It is a table | surface which shows an example of the DNS record information acquired with the DNS server by 2nd Embodiment of this invention. It is explanatory drawing which shows an example of the tree structure information produced | generated with the DNS server by 2nd Embodiment of this invention. It is a table | surface which shows an example of the black list produced | generated by the black list production | generation part of the DNS server by 2nd Embodiment of this invention.

<< First Embodiment >>
<Configuration of Communication System Using DNS Server According to First Embodiment>
A configuration of a communication system using a DNS server according to the first embodiment of the present invention will be described with reference to FIG. The communication system 1A according to the present embodiment is constructed in a dual stack environment in which an IPv6 closed network 10 and an IPv4 wide area network 20 are connected.

  The IPv6 closed network 10 includes a plurality of IPv6 closed network servers (first closed network server 11-1, second closed network server 11-2, and third closed network server 11-3), and user terminals. 12 and an IPv6 closed network DNS server 13A (hereinafter referred to as “closed network DNS server 13A”). Each of the first closed network server 11-1 to the third closed network server 11-3 is individually assigned an IPv6 address.

  Although FIG. 1 shows a case where one user terminal is connected to the IPv6 closed network 10 and three servers in the IPv6 closed network are connected, the number is not limited to this number, and more user terminals and IPv6 are connected. A server in the closed network may be connected.

  The user terminal 12 uses the first closed network server 11-1 to the third closed network server 11-3 or the web server in the IPv4 wide area network 20 as an access destination to set the host name or the mail address by the user. When the designation operation is performed, a DNS query for requesting name resolution processing for acquiring an IP address from the domain name of the access destination is generated and transmitted to the closed network DNS server 13A.

  The DNS server 13A includes a DNS record information storage unit 13a, a reception unit 13b, a domain determination unit 13c, a DNS application 13d, a response generation unit 13e, a transmission unit 13f, a response log information storage unit 13g, and an upper domain. It has a list generation unit 13h, a black list generation unit 13i, a black list storage unit 13j, a black list acquisition unit 13k, a matching list generation unit 13l, a DNS record information acquisition unit 13m, and a black list update unit 13n. .

  The DNS record information storage unit 13a stores, as DNS record information, correspondence information between a domain name and an IPv6 address, which is registered in advance for performing name resolution processing regarding devices in the IPv6 closed network 10.

  The receiving unit 13b receives a DNS query transmitted from the user terminal 12. The domain determination unit 13c determines whether or not the domain name specified by the DNS query received by the reception unit 13b corresponds to rejection domain part information in the black list stored in the black list storage unit 13j described later. To do. Here, if it is determined that the specified domain name corresponds to the rejection domain partial information in the black list, the DNS query is sent to the response generation unit 13e. If it is determined that the specified domain name does not correspond to the black list, the DNS query The query is sent to the DNS application 13d.

  When the DNS application 13d acquires the DNS query from the domain determination unit 13c, the DNS application 13d acquires an IPv6 address corresponding to the domain name specified by the acquired DNS query based on the DNS record information stored in the DNS record information storage unit 13a. And sent to the response generation unit 13e. Further, the DNS application 13d generates a response indicating that a Refused response should be made to the DNS query when the IPv6 address corresponding to the domain name specified by the acquired DNS query is not stored in the DNS record information storage unit 13a. Notification to the unit 13e.

  The response generation unit 13e generates a Refused response when acquiring a DNS query that determines that the domain name corresponds to the rejection domain partial information in the black list from the domain determination unit 13c, and generates a Refused response and transmits the user terminal 12 via the transmission unit 13f Send to. When the IPv6 address acquired by the DNS application 13d is acquired, the IPv6 address is generated as a response to the DNS query, and is transmitted to the user terminal 12 via the transmission unit 13f. The response generation unit 13e generates a Refused response when it is notified from the DNS application 13d that a Refused response should be made to the DNS query, and transmits the Refused response to the user terminal 12 via the transmission unit 13f.

  The response log information storage unit 13g stores log information (response log information) of response processing to the DNS query executed by the DNS application 13d, and counts the number of Refused responses for each domain name regarding the log information that has been Refused. Remember.

  The upper domain list generation unit 13h, at the black list generation timing that arrives at a predetermined time interval, from the response log information stored in the response log information storage unit 13g, a predetermined number of domain names having higher refused responses and the number of refused responses And an upper domain list of response log information is generated. Then, based on the upper domain list of the generated response log information, for each group including character strings common to each domain level, an upper domain list for each group including the corresponding domain name and the number of refused responses is generated. To do.

  The black list generation unit 13i extracts a common character string in the domain name as rejection domain part information for each upper domain list of each group generated in the upper domain list generation unit 13h, and also domain names in the corresponding group Is calculated as a count value of the rejection domain part information, and using the rejection domain part information and the count value, a blacklist which is a target of a Refused response for a DNS query to be generated thereafter Is generated.

  The black list storage unit 13j stores the black list generated at the past black list generation timing.

  The black list acquisition unit 13k acquires the black list stored in the black list storage unit 13j in response to a request from the matching list generation unit 13l.

  The matching list generation unit 13l matches the black list generated by the black list generation unit 13i with the existing black list acquired by the black list acquisition unit 13k, and sorts the rejection domain part information in descending order of the counter value. A matching list is generated with the upper predetermined number of pieces of rejection domain part information after sorting and its counter value.

  The DNS record information acquisition unit 13m acquires the DNS record information stored in the DNS record information storage unit 13a in response to a request from the black list update unit 13n.

  The black list update unit 13n includes the reject domain part information corresponding to the domain name in the DNS record information acquired by the DNS record information acquisition unit 13m from the match list generated by the match list generation unit 13l and its count value. Is deleted. Then, the black list in the black list storage unit 13j is updated with the upper predetermined number of pieces of rejection domain partial information after the corresponding information is deleted and its counter value.

  Further, the blacklist update unit 13n acquires new DNS record information via the DNS record information acquisition unit 13m when new correspondence information between the domain name and the IPv6 address is added to the DNS record information storage unit 13a. In addition, an existing black list is acquired via the black list acquisition unit 13k. Then, the rejected domain part information corresponding to the domain name in the acquired DNS record information and its counter value are deleted from the existing black list, thereby updating the black list in the black list storage unit 13j.

  A plurality of Web servers (first Web server 21-1, second Web server 21-2, and third Web server 21-3) and ISP (Internet Service Provider) -DNS server 22 are connected to the IPv4 wide area network 20. ing. Although FIG. 1 shows a case where three Web servers are connected to the IPv4 wide area network 20, the number is not limited to this, and more Web servers may be connected. Each of the first Web server 21-1 to the third Web server 21-3 is individually assigned an IPv4 address.

  When acquiring the DNS query from the user terminal 12, the ISP-DNS server 22 acquires an IPv4 address corresponding to the domain name included in the DNS query and transmits it to the user terminal 12 as a response thereto.

<Operation of Communication System Using DNS Server According to First Embodiment>
Next, the operation of the closed network DNS server 13A in the IPv6 closed network 10 of the communication system 1A according to the present embodiment will be described with reference to FIGS. In the present embodiment, the DNS record information storage unit 13a in the IPv6 closed network 10 stores the devices in the IPv6 closed network 10 (the first closed network server 11-1, the second closed network server 11-2, and the first 3), correspondence information between domain names and IPv6 addresses registered in advance for performing name resolution processing is stored in advance as DNS record information.

  During normal operation, when an operation for specifying a host name or mail address as an access destination is performed in the user terminal 12, a DNS query for requesting a name resolution process for obtaining an IP address from the domain name of the access destination Is generated and transmitted to the closed network DNS server 13A.

  In the closed network DNS server 13A, as shown in the flowchart of FIG. 2, when the DNS query transmitted from the user terminal 12 is received from the reception unit 13b (“YES” in S1), the domain determination unit 13c performs the DNS query. It is determined whether or not the domain name specified in (1) corresponds to reject domain part information in the black list stored in the black list storage unit 13j described later (S2).

  If it is determined that the determined domain name is, for example, the domain name of the IPv4 address and corresponds to the rejected domain partial information in the black list (“YES” in S2), the response generation unit 13e generates a Refused response to the DNS query. Then, it is transmitted from the transmission unit 13f to the user terminal 12 (S3). As described above, the Refused response process is performed in the preceding stage of the DNS application for the DNS query corresponding to the rejection domain part information in the black list. At this time, the count value indicating the number of refused responses related to the corresponding domain partial information stored in the black list is updated.

  In the user terminal 12, the DNS query is retransmitted to the ISP-DNS server 22 in the IPv4 wide area network 20 by receiving the Refused response. In the ISP-DNS server 22, for example, IPv4 of the Web server 21-1 is acquired based on the acquired DNS query and notified to the user terminal 12. In the user terminal 12, access processing is executed on the Web server 21-1 using the notified IPv4 address.

  If it is determined in step S2 that the domain name determined by the domain determination unit 13c does not correspond to the reject domain partial information in the black list (“NO” in S2), the DNS query is sent to the DNS application 13d. The In the DNS application 13d, it is determined whether or not an IPv6 address corresponding to the domain name specified by the received DNS query is stored in the DNS record information stored in the DNS record information storage unit 13a (S4). As a result of the determination, when the IPv6 address corresponding to the domain name specified by the received DNS query is stored in the stored DNS record information (“YES” in S4), the IPv6 address is acquired (S5). ).

  Then, in the response generation unit 13e, the acquired IPv6 address information is generated as a response to the DNS query, and is transmitted from the transmission unit 13f to the user terminal 12 (S6). Here, the response of the IPv6 address to the DNS query by the DNS application 13d is stored in the response log information storage unit 13g (S7).

  The user terminal 12 performs access processing to the first closed network server 11-1 using the notified IPv6 address.

  In the above-described processing, when the user terminal 12 performs an operation of designating a host name with the terminal having a domain name not stored in the black list, for example, the Web server 21-3 in the IPv4 wide area network 20 as an access destination The process proceeds from “NO” in step S4 to step S8. Then, the DNS application 13d notifies the response generation unit 13e that a Refused response should be made to the DNS query. In the response generation unit 13e, a Refused response is generated and transmitted to the user terminal 12 (S8). Here, it is stored in the response log information storage unit 13g that the DNS application 13d makes a Refused response to the domain name of the IPv4 address included in the DNS query. Further, the number of Refused responses of the corresponding domain name stored in the response log information storage unit 13g is updated (S9).

  A blacklist generation process executed at predetermined time intervals in the closed network DNS server 13A during operation as described above will be described with reference to FIGS.

  When the preset blacklist generation timing arrives (“YES” in S11), the upper domain list generation unit 13h sets a predetermined number of higher Refused responses from the response log information stored in the response log information storage unit 13g. Domain name and the number of refused responses are extracted, and an upper domain list of response log information is generated (S12). Here, as an example, from the response log information shown in FIG. 4, the domain names up to the top 10 Refused responses and the number of Refused responses shown in bold lines are extracted, and an upper domain list is generated. Here, the size of the number of Refused responses in the list shown in FIG. 4 is A> B> C> D> E> F> G> H> I> J.

  Next, in the upper domain list generation unit 13h, for each group α, β, σ, γ including character strings common to each domain level, based on the upper domain list of the response log information shown in FIG. Four upper domain lists a), (b), (c), and (d) are generated (S13). The upper domain list for each group includes the corresponding domain name and the number of refused responses.

  Next, the black list generation unit 13i extracts the common character string portion of the domain name in the upper domain list for each of the groups α, β, σ, and γ. As an example, a case will be described in which the common character string portion of the domain name is extracted from the upper domain list of the group α shown in FIG.

  In the upper domain list of group α, three domain names “aaaaa.co.jp”, “aa.co.jp”, and “aaaa.co.jp” are stored as domain names that have been frequently responded to Refused. . These domain names are each divided into a first level domain (top level domain), a second level domain, and a third level domain, and each domain level is shown in a table as shown in FIGS. Indicated.

  FIG. 6A is a table showing the first level domain of each domain name in the group α. In the first row, “jp” which is the first level domain of the domain name “aaaaa.co.jp” is shown. One character is stored in each column, and the first level domain “jp” of the domain name “aa.co.jp” is stored in each column in the second row, and the first character of each domain name “aaaa.co.jp” One-level domain “jp” is stored in each column, one character at a time.

  FIG. 6B is a table showing the second level domain of each domain name, and is the second level domain of each domain name in the first to third lines in the same manner as in FIG. 6A. “Co” is stored one character in each column.

  FIG. 6C is a table showing the third level domain of each domain name. In the first row, “aaaaa”, which is the third level domain of the domain name “aaaaa.co.jp”, is one character in each column. In the second row, “aa”, which is the third level domain of the domain name “aa.co.jp”, is stored in each column, one character at a time, and in the third level domain of the domain name “aaaa.co.jp” A certain "aaaa" is stored in each column, one character. These pieces of information are stored in each column with right justification in each row.

  Next, based on the generated table for each domain level, the first level domain and the second level domain match in all the columns among the plurality of domain names, and the third level domain has a plurality of columns from the right. A combination of common character strings having the same is extracted. 6A to 6C, the first level domain “jp” is defined between three domain names “aaaaa.co.jp”, “aa.co.jp”, and “aaaa.co.jp”. "And the second level domain" co "match, and the two columns from the right of the third level domain are common to" aa ", so the character string" aa.co.jp "combining them is extracted .

  Then, “* aa.co.jp”, in which “*” indicating an arbitrary character string of 0 or more characters is added to the head of the extracted character string, is a target of a Refused response to a DNS query to be generated thereafter. Rejected domain part information. Also, the sum of the number of Refused responses for the domain names “aaaaa.co.jp”, “aa.co.jp”, and “aaaa.co.jp” corresponding to this rejection domain partial information “* aa.co.jp” Is calculated as the counter value a of the rejection domain partial information “* aa.co.jp”. That is, counter value a = Refused response number A + D + G.

  Similarly, rejection domain partial information “* bbb.co.jp” is extracted from the upper domain list of group β shown in FIG. 5B, and its counter value b is calculated (counter value b = Refused response number B + I). ). Further, the rejection domain partial information “* cc.co.jp” is extracted from the upper domain list of the group σ shown in FIG. 5C, and the counter value d is calculated (counter value d = Refused response number Refused response). Number E + F + J). Further, rejection domain partial information “* ddd.co.jp” is extracted from the upper domain list of the group γ shown in FIG. 5D, and its counter value c is calculated (counter value c = Refused response number C + H). .

  Then, the four pieces of extracted rejection domain partial information are rearranged in descending order of the counter value, and a black list is generated as shown in FIG. 7 (S14). In the black list of FIG. 7, the rejection domain partial information is “* aa.co.jp”, its counter value a, “* bbb.co.jp”, its counter value b, “* ddd” in descending order of the counter value. .co.jp "and its counter value c," * cc.co.jp "and its counter value d are held.

  If the blacklist generation process is the first time and there is no existing blacklist in the blacklist storage unit 13j (“YES” in S15), the blacklist updated in step S14 is the blacklist. The data is stored in the list storage unit 13j, and the process returns to step S11 (S16).

  In step S11, when a preset period (for example, several days) elapses and the next blacklist generation timing comes (“YES” in S11), the processes of steps S12 to S14 are executed as described above.

  In the present embodiment, the second and subsequent book list generation processes are executed (“NO” in S15), and the black list acquisition unit 13k acquires the existing black list stored in the black list storage unit 13j. (S17). An example of an existing black list is shown in FIG. The black list in FIG. 8 includes a counter value x indicating the number of Refused responses regarding the rejection domain part information with the rejection domain part information “* yy.co.jp”, and rejection domain part information “* jjj.co, jp”. And its counter value y, rejection domain partial information “* zzzzzz.ne.jp”, and its counter value z are held.

  Next, the blacklist generated by the blacklist generation unit 13i and the existing blacklist acquired by the blacklist acquisition unit 13k are collated by the matching list generation unit 13l, and the rejection domain partial information in descending order of the counter value. A reconciliation list is generated (S18). For example, the black list shown in FIG. 7 and the existing black list shown in FIG. 8 are collated, and the coincidence list shown in FIG. 9 is generated.

  When the match list is generated, the DNS record information acquisition unit 13m acquires the latest DNS record information from the DNS record information storage unit 13a in response to a request from the black list update unit 13n (S19). For example, as shown in FIG. 10, DNS record information including “aaa.ne.jp”, “bbbbb.co.jp”... “Ccc.ne.jp” is acquired.

  The blacklist update unit 13n then rejects domain part information corresponding to the domain name in the DNS record information acquired by the DNS record information acquisition unit 13m from the match list generated by the match list generation unit 13l. The count value is deleted (S20). For example, from the matching list generated as shown in FIG. 9, “bbbbb.co.jp” in the DNS record information shown in FIG. The counter value b is deleted and updated as shown in FIG.

  Then, the upper predetermined number of pieces of rejection domain part information and the counter value thereof are extracted from the updated matching list, and the black list in the black list storage unit 13j is updated with the extracted information (S21). For example, from the updated matching list in FIG. 11, the top three rejection domain part information indicated by the bold line frame and its counter value (rejection domain part information “* aa.co.jp”, its counter value a, rejection Domain part information “* yy.co, jp” and its counter value x, rejection domain part information “* jjj.co.jp” and its counter value y) are extracted, and these pieces of information are stored in the blacklist storage unit 13j. The black list is updated.

  When the black list in the black list storage unit 13j is updated, the response log information stored in the response log information storage unit 13g is deleted, and all count values in the updated black list are as shown in FIG. To return to step S1. This is the end of the description of the black list generation process.

  Next, processing executed when correspondence information between a domain name and an IPv6 address for performing name resolution processing is newly added to the DNS record information storage unit 13a in the closed network DNS server 13A will be described with reference to FIG. This will be described with reference to the flowchart of FIG.

  When new correspondence information is added to the DNS record information in the DNS record information storage unit 13a ("YES" in S21), the DNS record information after the information is added by the DNS record information acquisition unit 13m is transferred from the DNS record information storage unit 13a. It is acquired and sent to the black list update unit 13n (S22). In response to a request from the blacklist update unit 13n, the blacklist acquisition unit 13k acquires the existing blacklist from the blacklist storage unit 13j (S23).

  Then, the black list is updated by deleting the rejection domain portion corresponding to the domain name in the acquired DNS record information and its counter value from the existing black list by the black list updating unit 13n (S24). .

  According to the first embodiment described above, in the closed network DNS server 13A in the IPv6 closed network 10, a DNS query related to the domain name of the IPv4 wide area network 20 that is frequently received is promptly performed in the preceding stage of the DNS application 13d. A Refused response is made, the processing load of the DNS application 13d is reduced, and the processing time can be shortened.

  In addition, when a frequently accessed destination from the user terminal 12 is added or changed, or when DNS record information is newly added, the black list is automatically updated in response to this, and the DNS record is automatically updated. The name resolution process for the domain name registered in the information can be surely executed.

<< Second Embodiment >>
<Configuration of Communication System Using DNS Server According to Second Embodiment>
A configuration of a communication system using a DNS server according to the second embodiment of the present invention will be described with reference to FIG. The communication system 1B according to the present embodiment includes a black list generation unit 13i, a black list acquisition unit 13k, a matching list generation unit 13l, and a black list update unit 13n in the closed network DNS server 13A of the communication system 1A of the first embodiment. Instead, the closed network DNS server 13B has the same configuration as that of the first embodiment, except that it includes a match list generation unit 13p, a tree structure information generation unit 13q, a black list generation unit 13r, and a black list update unit 13s. Therefore, detailed description of portions having the same function is omitted.

  In the present embodiment, the DNS record information acquisition unit 13m in the closed network DNS server 13B acquires the DNS record information stored in the DNS record information storage unit 13a, and for each DNS record information, a response log information storage unit 13g. A value sufficiently smaller than the maximum value of the number of response log information that can be stored in is added as a corresponding point value. Here, −∞ is added as a point value to each DNS record information.

  The upper domain list generation unit 13h, at the black list generation timing that arrives at a predetermined time interval, from the response log information stored in the response log information storage unit 13g, a predetermined number of domain names having higher refused responses and the number of refused responses And an upper domain list of response log information is generated.

  The matching list generation unit 13p uses the number of Refused responses for each domain name in the upper domain list generated by the upper domain list generation unit 13h as a point value of the corresponding domain name, and the DNS acquired by the DNS record information acquisition unit 13m. Generate a reconciliation list matched with record information.

  From the match list generated by the match list generation unit 13p, the tree structure information generation unit 13q sets each character constituting the domain name as a node, and sets the common character at the end (right end) of the domain name as the highest node and the top ( Tree structure information indicating a plurality of domain names having a common terminal character string is generated with the leftmost character as the lowest node. Then, the point value of the corresponding domain name is added as the point value of the corresponding node to each lowest node in the information of the tree structure, and the point value of the latest lower node is added to each node other than the lowest node The value is added as the point value of the corresponding node.

  From the tree structure information generated by the tree structure information generation unit 13q, the black list generation unit 13r uses the node value for a node having a positive point value and a negative point value for the most recent upper node. And the common character string portion including the higher-order node are extracted, and the common character string portion is generated as rejection partial domain information that is a target of a rejection response to the DNS query to be generated thereafter.

  The black list update unit 13s updates the existing black list in the black list storage unit 13j with the black list generated by the black list generation unit 13r.

<Operation of Communication System Using DNS Server According to Second Embodiment>
Operation | movement of the closed network DNS server 13B of the communication system 1B by this embodiment is demonstrated with reference to FIGS. In the present embodiment, during normal operation, the name resolution process is executed based on a request from the user terminal 12 as in the first embodiment.

  When the blacklist generation timing set in advance is reached during the operation of the communication system 1B (S31 and “YES”), the upper domain list generation unit 13h uses the response log information stored in the response log information storage unit 13g. The predetermined number of domain names having the highest number of refused responses and the number of refused responses are extracted, and an upper domain list of response log information is generated as shown in FIG. 16 (S32).

  The DNS record information acquisition unit 13m acquires the DNS record information stored in the DNS record information storage unit 13a, and the maximum number of response log information that can be stored in the response log information storage unit 13g for each DNS record information. A value sufficiently smaller than the value is added as the corresponding point value. Here, as shown in FIG. 17, -∞ is added as a point value to each DNS record information (S33).

  Next, the DNS record information acquired by the DNS record information acquisition unit 13m, using the number of rejection responses for each domain name of the response log information stored in the response log information storage unit 13g as a point value by the matching list generation unit 13p, A matched list is generated (S34).

  Next, the tree structure information generation unit 13q generates tree structure information with each character of the domain name as a node, as shown in FIG. 18, from the match list generated by the match list generation unit 13p. This tree structure information is edged with the first domain terminal character (rightmost character) common to multiple domain names as the highest node, the rightmost character one by one on the left, and the corresponding nodes in turn as lower nodes. Configured in association with. Here, the character string part continuously common from the top node among multiple domain names is made the same node, and the information of multiple domain names in the matching list is stored by branching from the different characters at the edge. Is done.

  In addition, a point value of the corresponding domain name is added to each lowest node in the information of the tree structure (S35). Further, the total value of the point values of the lowest node (terminal node) having a common higher node is added as the point value of the corresponding higher node (S36). Furthermore, when there is a node to which no point value is added to the upper node (“YES” in S37), the nearest lower node to which a point value is added having a common upper node to which no point value is added Is added as the point value of the corresponding upper node (S38). This process is repeated until there are no nodes to which point values are not added.

  When the point value is added to all the nodes in the tree structure information (“NO” in S37), the black list generation unit 13r determines that the point value is a positive value from the tree structure information, and the highest For a node having a negative node point value, a common character string portion including the node and its upper node and the corresponding point value are extracted (S39). Then, among the extracted common character string portions, those having a corresponding point value larger than a predetermined value are further extracted. Here, if there is a subordinate node in the extraction target node, the subordinate node portion is set as “*” indicating an arbitrary character string of zero or more characters, and a rejection response target for a DNS query to be generated thereafter is set. To reject domain part information is generated. Then, the generated rejection part domain part information is listed as shown in FIG. 19 to generate a black list. Further, the black list update unit 13s updates the existing black list in the black list storage unit 13j with the generated black list (S40).

  According to the second embodiment described above, in the closed network DNS server 13B in the IPv6 closed network 10, a DNS query related to the domain name of the IPv4 wide area network 20 that is frequently received is promptly performed in the preceding stage of the DNS application 13d. A Refused response is made, the processing load of the DNS application 13d is reduced, and the processing time can be shortened.

  In the above-described embodiment, the case where the DNS server in the network corresponding to IPv6 has the function of generating and updating the blacklist has been described. However, the function is installed in the DNS server in the IPv4 network, and the IPv4 network You may make it reduce the processing load of the DNS server at the time of accessing the apparatus in an IPv6 network from the apparatus in an inside.

DESCRIPTION OF SYMBOLS 1 ... Communication system 10 ... IPv6 closed network 11-1 ... 1st closed network server 11-2 ... 2nd closed network server 11-3 ... 3rd closed network server 12 ... User terminal 13 ... DNS server 13a ... DNS Record information storage unit 13b ... Reception unit 13c ... Domain determination unit 13d ... DNS application 13e ... Response generation unit 13f ... Transmission unit 13g ... Response log information storage unit 13h ... Higher domain list generation unit 13i ... Black list generation unit 13j ... Black list Storage unit 13k ... Black list acquisition unit 13l ... Match list generation unit 13m ... DNS record information acquisition unit 13n ... Black list update unit 13p ... Match list generation unit 13q ... Tree structure information generation unit 13r ... Black list generation unit 13s ... Black list Update unit 20 ... IPv4 wide area network 21-1 ... 1Web server 21-2 ... first 2Web server 21-3 ... first 3Web server 22 ... ISP-DNS server

Claims (3)

A DNS record information storage unit that stores, as DNS record information, correspondence information between a domain name and an IP address registered for performing a name resolution process for resolving an IP address from a domain name;
A response log information storage unit for storing log information of a response process to a DNS query transmitted to specify a domain name and request a name resolution process;
The DNS record information stored in the DNS record information storage unit is acquired, and for each DNS record information, an absolute negative value that is larger than the maximum number of response log information items that can be stored in the response log information storage unit DNS record information acquisition unit for adding as a point value;
The match list matched with the DNS record information acquired by the DNS record information acquisition unit using the number of rejection responses for each domain name of the response log information stored in the response log information storage unit as a point value at a predetermined time interval A match list generator for generating
From the match list generated by the match list generation unit, each character of the domain name is a node, the common character at the end of the domain name is the highest node, the first character is the lowest node, and the common end character string is Generates tree structure information indicating multiple domain names, and adds the point value of the corresponding domain name as the point value of the corresponding node to each lowest node in the tree structure information. A tree structure information generation unit for adding the total value of point values of the latest lower nodes to each node as a point value of the corresponding node;
From the tree structure information generated by the tree structure information generation unit, a node whose point value is a positive value and whose point value of the nearest higher node is a negative value includes the node and its higher node. A black list generation unit that extracts a common character string part and generates the black list as rejection partial domain information that is a target of a rejection response to a DNS query that occurs thereafter.
A DNS server, comprising: a black list storage unit that stores the black list generated by the black list generation unit . A DNS record information storage unit that stores, as DNS record information, correspondence information between a domain name and an IP address registered for performing a name resolution process for resolving an IP address from a domain name;
  A DNS server comprising a response log information storage unit for storing log information of a response process to a DNS query transmitted to specify a domain name and request a name resolution process;
  The DNS record information stored in the DNS record information storage unit is acquired, and for each DNS record information, an absolute negative value that is larger than the maximum number of response log information items that can be stored in the response log information storage unit Is added as a point value,
  At a predetermined time interval, the number of rejection responses for each domain name of the response log information stored in the response log information storage unit is set as a point value, and a matching list is generated by matching the acquired DNS record information,
  From the generated match list, each domain name character is a node, the common character at the end of the domain name is the highest node, and the first character is the lowest node, indicating multiple domain names with a common end character string Generated tree structure information,
  The point value of the corresponding domain name is added as the point value of the corresponding node to each lowest node in the information of the tree structure, and the total value of the point values of the nearest lower nodes is added to each node other than the lowest node. Add as the point value of the corresponding node,
  From the generated tree structure information, extract the common character string part including the node and its higher-order node for the node whose point value is positive and the point value of the nearest higher-level node is negative. Then, a blacklist is generated using the common character string part as rejection part domain information for a rejection response to a DNS query generated thereafter,
  Memorize the generated blacklist
A black list generation method in a DNS server. A black list generation program for causing a computer to execute a function executed by the DNS server according to claim 1.

Images