KR20120000897A - Query processing system and method using zone configuration - Google Patents

Abstract

PURPOSE: A specific query processing system and method thereof are provided to increase the performance of a network and a system and to reduce the process of unnecessary data by setting a zone in a DNS. CONSTITUTION: A DNS(Domain Name System)(200) confirms whether to include a predetermined zone from a client(100). If the query includes the specific zone, the DNS confirms whether the query includes a specific character string. If query does not include the specific character string, the DNS responds an Internet address of a keyword processing system(300) based on zone setting. The keyword processing system receives a keyword query from the client connecting through the internet address.

Description

Query Processing System and Method using Zone Configuration

The present invention relates to a technique for processing a specific query input from the client, and in particular, when a query including a specific DNS suffix is received from the client to the domain name server, the query is separated and processed according to the form of the query. It relates to a specific query processing system and a method through the zone setting to block the operation.

In order to access and use content or services such as web pages on the Internet, the Internet address of the content or service is necessary. Representative Internet addresses include IP address and domain name. In addition, there are mobile address, ENUM, keyword type internet address.

An IP address is the most basic Internet address. It is a machine-type internet address that identifies a host or server. There are two officially used IP addresses, IPv4 and IPv6.In the case of IPv4, four numbers represented by decimal numbers from 0 to 255 are represented by separated dots (.) Like 210.103.175.41. IPv6 expresses 8 parts separated by colon (:) by 16 bits in hexadecimal, for example, 21DA: D3: 0: 2F3B: 2AA: FF: FE28: 9C5A It is difficult to use.

The domain name is designed to solve the inconvenience of recognizing and using a numeric IP address. It is basically composed of a combination of alphabets, numbers, and hyphens. In the case of multilingual domain names using non-English characters, Depending on the coding method, non-English characters are converted to English characters. In the domain name, each step divided by a dot (.) Is composed of a hierarchical structure of inverse tree structure, and identification is sequentially performed from the right side. However, in fact, the IP address is used to connect the devices, and since the domain name is just a mapping of the IP address into characters, it cannot function as a domain name alone, and a domain name server that converts the domain name into an IP address is used. It is necessary.

A domain name server is a server that informs the IP address corresponding to the domain name. When a client inquires a domain name by clicking or clicking a domain name to access content or services, the domain name server is the domain in question. The client finds an IP address corresponding to the name and responds to the client. The client accesses the content or service using the received IP address. The domain name server does not store the information about all domain names, and finds the IP address corresponding to the domain name by sequentially querying each delegated name server according to the hierarchical structure.

Another Internet address is a keyword-type internet address, which is composed of keywords, and unlike a domain name, has a hierarchical structure rather than a hierarchy. In order to process a keyword type query, a separate system that responds to a URL or an IP address for a keyword is required, such as a domain name server that searches for and responds to an IP address for a domain name. However, in general, keyword type query processing is not supported by the general OS or browser, and it installs plug-in program in client to send query to the corresponding processing system or sets DNS suffix without installing plug-in program. By doing so, it can be processed to be transmitted to the domain name server in the form of DNS suffix to keyword type query. The domain name server processes the keyword type query by setting the system to process the keyword in response to a query with a specific DNS suffix sent from the client.

In order to process the keyword type query transmitted from the client as described above, the domain name server responds to the system for keyword processing in response to the query with a specific DNS suffix. There are many other things that are not appropriate due to various programs or errors. In addition, unnecessary network traffic is generated due to such inadequate data, and there is a problem in that the performance of the system is degraded by unnecessary load on the corresponding system.

Therefore, the technical problem to be achieved by the present invention is to reduce the unnecessary traffic of the network and the load of the corresponding system to reduce the performance and efficiency of the network and system by stopping further processing of inappropriate data other than keyword type queries transmitted from the client through zone setting. Height is to provide a system and method.

The present invention reduces the processing of unnecessary data and increases the performance and efficiency of the network and the system by setting a zone in the domain name server without additional system.

1 is a configuration diagram of an example of a system according to the present invention.
2 is a process flow diagram of an example method according to the present invention;

A domain name server is a server that provides an IP address corresponding to a domain name. In most cases, a domain name server must be supported by a domain name server to access a server for use of content or services on the Internet.

The keyword processing system is a system that functions to respond to a query or an address of a web server corresponding to a query.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings.

1 is a configuration diagram of an example system according to the present invention.

The client 100 inputs a query in the form of a keyword for the purpose of accessing a content or service such as a web page or obtaining a search result. The query in the form of a keyword input to the client is transmitted to the domain name server 200 as it is, or in the form of a specific query form or suffix added according to a condition such as a program or environment setting state installed in the client.

When the domain name server 200 receives a query from the client 100, the domain name server 200 searches for information such as an IP address corresponding to the received query and responds to the client 100. At this time, if information such as an IP address corresponding to the received query is stored in the domain name server 200, the stored information is returned to the client 100, and if not, the domain name root server ( 250) and the like to find the corresponding information and then respond to the client (100).

The domain name server 200 mechanically responds to the query of the client 100, but it is possible to set and process a specific rule for a specific domain name query. Creating a rule for a specific domain name query is possible by setting a zone file in the domain name server 200, and the system of the present invention is also implemented by a method of setting a zone file in the domain name server 200.

A zone file is a file that contains data describing a portion of a particular Internet domain name space. The zone file contains information needed to resolve domain names to IP addresses, that is, domain names and their associated domains, IP addresses, and mail servers. Information and the like. In the zone file, the relevant attribute information for the domain name is contained in the order of <Name> <TTL> <Class> <Type> <RDATA>, where <Name> is the domain name and <TTL> is how much to cache the data. The second value of whether to last long, <Class>, is now meaningless, but IN is used for the Internet, <Type> is the type of information (record), and <RDATA> is the data part. . For example, if the IP address of the domain name example.co.kr is 192.250.123.41, the example.com zone file

example.com IN A 192.250.123.41

The contents are described in the form as follows. Where example.com corresponds to <Name>, <TTL> is omitted, IN is <Class>, and A is <Type>, which indicates the attribute of the information linked to the domain name. It means that the content is an IPv4 address. If it is an IPv6 address, it is used as AAAA and text if it is TXT. In this way, the connection property for the zone or domain under the zone is set through the zone file.

In order for the zone file to be recognized and processed by the domain name server 200, the contents of the zone file must be set in the zone configuration file. For example, example.com.

zone "example.com" IN {

type master;

file "example.com";

}; It is expressed as The zone configuration file varies somewhat depending on the domain name server program. However, the most common domain name server program and the widely used BKE (Berkeley Internet Name Domain) are /etc/named.conf.

In order to transmit the keyword type query to the domain name server 200, a method of adding a specific DNS suffix to the query is used. In addition, the domain name server 200 sets a zone file for a specific DNS suffix in order to respond to the keyword processing system 300 in response to the keyword type query. The DNS suffix for the judgment processing of keyword type queries is a keyword or specific domain that is not a public top level domain (TLD) such as .com, .net, or .kr to prevent conflicts with existing domain names. It is preferable to use a name. For example, a keyword such as keyword or local rather than a public top-level domain name, or the domain name of a keyword processing system may be used as a DNS suffix. The DNS suffix may be set in the client 100 by using a DHCP server to assign a DNS suffix when allocating an IP address or by setting a user's network.

In the following description, a keyword, which is a keyword other than an authorized top-level domain name, is used as a DNS suffix. All of the keyword-type queries queried from the client 100 are added with a keyword, DNS suffix, and transmitted in the form of 'string.keyword', and the domain name server 200 adds a DNS suffix 'keyword' to process the transmitted query. To do this, create a zone file for the 'keyword' and set it in the zone configuration file. The zone configuration file

zone "keyword" IN {

type master;

file "keyword";

}

By adding the contents in the form of, the query ending with 'keyword' is processed by referring to the zone file named 'keyword'. If the IP address of the keyword processing system 300 is 123.123.123.123, the 'keyword' zone file

* .keyword IN A 123.123.123.123

It will be written as Here, '*' means all and means to answer 123.123.123.123, which is the IP address of the keyword processing system 300, to all queries ending with 'keyword'. However, in this case, the address of the keyword processing system 300 is replied by applying the same to the inappropriate queries generated by various programs or errors in addition to the keyword type query input by the user from the client 100. As a result, unnecessary network traffic and keyword processing system 300 load are generated.

In general, an error query generated from the client 100 causes a considerable interruption of service of a domain name existing or input of a domain name incorrectly. Since these queries are not keyword type queries, keyword processing is performed. Since it is difficult for the system 300 to respond to meaningful results, it may be difficult to respond to the query from the domain name server 200 to terminate the query rather than answering the address of the keyword processing system 300. desirable. To this end, in the present invention, a response to refer to a specific IP address or another name server, such as a local IP address, for a domain type query rather than a keyword query is set in the corresponding zone file. For example, for zone file 'keyword',

*. *. keyword IN A 127.0.0.1

* .keyword IN A 123.123.123.123

or

*. *. keyword IN NS ns.service.com

* .keyword IN A 123.123.123.123

Can be set as follows. Where 127.0.0.1 is the IP address representing the computer itself, and it is possible to reply to another IP address. ns.service.com is the address of another domain name server and should be a domain name server with no suffix handling. When zone file is set up like this, the zone does not have IP address or keyword processing function pointing to itself so that if the '.' Is included before the DNS suffix named keyword, it is not a keyword query. In response to the address of the other domain name server, the processing is stopped as a result, and the IP address of the keyword processing system 300 is responded only to the query of the keyword type.

However, depending on the type of domain name server, it may be impossible to classify and process the query. In this case, similar effects can be obtained by directly setting the main TLD. For example,

* .com.keyword IN A 127.0.0.1

* .net.keyword IN A 127.0.0.1

* .org.keyword IN A 127.0.0.1

* .kr.keyword IN A 127.0.0.1

* .cn.keyword IN A 127.0.0.1

* .comm.keyword IN A 127.0.0.1

* .keyword IN A 123.123.123.132

It may be configured in the form of, and may be set and used even when frequently inputted incorrectly, such as frequently used TLD or comm, but it is preferable to exclude words that can be processed as keywords for stable service. Since the TLD type can be added continuously, it must be managed continuously. In order to improve the efficiency of management / operation, it is set as slave for the zone for judging keyword type queries and managed in a separate master name server to manage multiple domain name servers. It is also possible to apply simultaneously.

2 is a process flow diagram of an example method according to the present invention.

When the domain name server 200 receives a query from the client 100 (S101), the domain name server 200 determines whether a specific zone is included in the query (S103). The specific zone is a predetermined DNS suffix so that it is easy to determine whether the character string input to the client 100 was a keyword, and a public top-level domain such as .com, .net, or .kr to prevent a conflict with an existing domain name. It is preferable to use a keyword or a specific domain name rather than a name (TLD: Top Level Domain). For example, a keyword such as keyword or local, which is not a public top-level domain name, or a domain name of a keyword processing system may be used as a DNS suffix. The domain name server 200 sets a specific rule for a specific domain name query and processes it. You will set up a zone file for that DNS suffix.

For example, if a keyword that is not a public top-level domain name is used as a DNS suffix, all keyword-type queries queried from the client 100 are forwarded in the form of 'string.keyword' with the DNS suffix keyword appended. In the name server 200, a zone file for 'keyword' is created, and a zone setting file must also be set. The zone configuration file

zone "keyword" IN {

type master;

file "keyword";

By adding the contents in the form of, the query ending with 'keyword' is processed by referring to the zone file named 'keyword'. If the IP address of the keyword processing system 300 is 123.123.123.123, the 'keyword' zone file

* .keyword IN A 123.123.123.123

It will be described as follows. Here, '*' means all and means to answer 123.123.123.123, which is the IP address of the keyword processing system 300, to all queries ending with 'keyword'.

Checking whether the specific zone is included (S103) is performed by checking whether the zone specified in the zone configuration file is included in the query, and when the specific zone is not included, according to the general function of the domain name server 200 The corresponding IP address to the query is found and responded to the client 100 (S105).

However, if it is confirmed that the specific zone is included in the query, the zone file for the corresponding zone is checked (S107).

In the conventional processing method, a mechanical response is made to a specific zone, but in this case, the same applies to the inappropriate query generated by various programs or errors in addition to the keyword type query input by the user from the client 100. As a result, the address of the keyword processing system 300 is responded, thereby causing unnecessary network traffic and the keyword processing system 300 load. In general, an error query generated from the client 100 causes a considerable interruption of service of a domain name existing or input of a domain name incorrectly. Since these queries are not keyword type queries, keyword processing is performed. Rather than responding to the address of the system 300, it is preferable that the domain name server 200 responds to terminate the processing of the query. To this end, in the present invention, in order to check whether the keyword query, '.' Check whether or not a specific character, such as (S109), and set the zone file to respond to refer to a specific IP address or other name server, such as a local IP address, for a domain type query other than a keyword query. (S111). For example, for zone file 'keyword',

*. *. keyword IN A 127.0.0.1

* .keyword IN A 123.123.123.123

or

*. *. keyword IN NS ns.service.com

* .keyword IN A 123.123.123.123

Can be set as follows. Where 127.0.0.1 is the IP address representing the computer itself, and it is possible to respond to a different IP address. .service.com corresponds to the address of another domain name server and should be a domain name server that does not have any zone handling. When zone file is set up like this, the zone does not have IP address or keyword processing function pointing to itself so that if the '.' Is included before the DNS suffix named keyword, it is not a keyword query. It responds to the address of another domain name server, and responds to the Internet address of the keyword processing system 300 only in response to a keyword type query.

However, depending on the type of domain name server, it may not be possible to classify and process the query. In this case, similar effects can be obtained by directly setting the main TLD. For example,

* .com.keyword IN A 127.0.0.1

* .net.keyword IN A 127.0.0.1

* .org.keyword IN A 127.0.0.1

* .kr.keyword IN A 127.0.0.1

* .cn.keyword IN A 127.0.0.1

* .comm.keyword IN A 127.0.0.1

* .keyword IN A 123.123.123.132

It can be configured in the form of, and can be used to set frequently used cases such as frequently used TLD or frequently comm, but it is desirable to exclude the words that can be processed as keywords for stable service. Since TLD information can be added continuously, it must be managed continuously. To increase the efficiency of management / operation, set slave as zone for judging keyword type query and manage it in separate master name servers to manage multiple domain name servers. You can also make it applicable at the same time.

*** Description of the symbols for the main parts of the drawings ***
100: client 200: domain name system
250: domain name root server 300: keyword processing system
400: web server

Claims (2)

After confirming that the query received from the client includes a specific zone, if the specific zone is included, check again whether the specific string is included, and only if the specific string is not included, the Internet address of the keyword processing system is not included. Domain Name System zoned to respond
A specific query processing system through zone setting, comprising: a keyword processing system configured to receive a keyword query from a client accessing an Internet address from the domain name server and to respond to a corresponding web server or search server; The domain name server receiving a query from a client;
Confirming whether the received query includes a specific zone;
When it is determined that the query includes a specific zone, checking whether the query includes a specific character;
When the query includes a specific zone and includes a specific character, the domain name responds to another domain name server or a specific IP address to the client, and the query includes a specific zone but does not include a specific character. Responding to an Internet address of the keyword processing system to the client specific query processing method through the zone setting, characterized in that

Images