KR20100008043A - Method and apparatus for getting information in database of domain name system - Google Patents

Method and apparatus for getting information in database of domain name system Download PDF

Info

Publication number
KR20100008043A
KR20100008043A KR1020080068432A KR20080068432A KR20100008043A KR 20100008043 A KR20100008043 A KR 20100008043A KR 1020080068432 A KR1020080068432 A KR 1020080068432A KR 20080068432 A KR20080068432 A KR 20080068432A KR 20100008043 A KR20100008043 A KR 20100008043A
Authority
KR
South Korea
Prior art keywords
dns
client
query
information
database
Prior art date
Application number
KR1020080068432A
Other languages
Korean (ko)
Other versions
KR101005778B1 (en
Inventor
이상조
Original Assignee
(주)씨디네트웍스
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by (주)씨디네트웍스 filed Critical (주)씨디네트웍스
Priority to KR20080068432A priority Critical patent/KR101005778B1/en
Publication of KR20100008043A publication Critical patent/KR20100008043A/en
Application granted granted Critical
Publication of KR101005778B1 publication Critical patent/KR101005778B1/en

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements or network protocols for addressing or naming
    • H04L61/15Directories; Name-to-address mapping
    • H04L61/1505Directories; Name-to-address mapping involving standard directories or standard directory access protocols
    • H04L61/1511Directories; Name-to-address mapping involving standard directories or standard directory access protocols using domain name system [DNS]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L29/00Arrangements, apparatus, circuits or systems, not covered by a single one of groups H04L1/00 - H04L27/00
    • H04L29/12Arrangements, apparatus, circuits or systems, not covered by a single one of groups H04L1/00 - H04L27/00 characterised by the data terminal
    • H04L29/12009Arrangements for addressing and naming in data networks
    • H04L29/12047Directories; name-to-address mapping
    • H04L29/12056Directories; name-to-address mapping involving standard directories and standard directory access protocols
    • H04L29/12066Directories; name-to-address mapping involving standard directories and standard directory access protocols using Domain Name System [DNS]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L29/00Arrangements, apparatus, circuits or systems, not covered by a single one of groups H04L1/00 - H04L27/00
    • H04L29/12Arrangements, apparatus, circuits or systems, not covered by a single one of groups H04L1/00 - H04L27/00 characterised by the data terminal
    • H04L29/12009Arrangements for addressing and naming in data networks
    • H04L29/12047Directories; name-to-address mapping
    • H04L29/12132Mechanisms for table lookup, also between directories; Directory data structures; Synchronization of directories
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements or network protocols for addressing or naming
    • H04L61/15Directories; Name-to-address mapping
    • H04L61/1552Mechanisms for table lookup, e.g. between directories; Directory data structures; Synchronization of directories

Abstract

PURPOSE: A method and a device for getting information in database of domain name system are provided to directly acquire the information stored in the DNS database through DNS server. CONSTITUTION: A DNS query generating unit(400) creates the DNS query by the client IP(Internet Protocol) address information. A client information receiving unit(410) receives the information matching with the client IP address saved in the DNS database from the DNS server. By the same library as the library used in the production of the DNS query at the DNS system, the DNS query generating unit creates the DNS query.

Description

Method and apparatus for obtaining information stored in database of domain name system {Method and apparatus for getting information in database of Domain Name System}
The present invention relates to a method and apparatus for obtaining information stored in a database of a domain name system, and more particularly, to a method and apparatus for acquiring information stored in a database of a domain name system while using a conventional domain name system as it is. It is about.
Domain Name System (DNS) is an IP address that identifies the location of domain names on the Internet, which are provided in the form of text for easy recognition by users in web browsers installed on devices such as computers. It is a system to change.
In other words, a domain name is a name that users can easily recognize, but a numeric Internet Protocol (IP) address is required to find a device such as a client or server on the Internet.
In such a domain system, a DNS server reads an IP address corresponding to a domain name from a DNS database connected to a DNS server and transmits the information to a client or a server so that each device is connected to each other.
For example, if you provide a DNS server with a domain name of abc.com, the DNS server reads an IP address of 123.45.67.89 that matches abc.com from the DNS database associated with the DNS server and provides it to the client. The IP address is used to connect to a device on the Internet that corresponds to the domain name abc.com.
On the other hand, such a domain name system must be common to all Internet users, so a common protocol is required, and these regulations are specified in Request For Comments (RFC).
Therefore, the transfer of domain name from client to DNS server and IP address transfer from DNS server to client are made by this convention.
The DNS database may store not only IP address information corresponding to the domain name but also ISP (Internet Service Provider) information and location information according to the IP address.
For example, IPv4, our current IP address system, consists of 32 bits and has five class structures: A, B, C, D, and E. Only three classes A, B, and C are generally used, and 8 bits of the first class A class are network parts, and the remaining classes B and C are host parts.
Due to the nature of the IP address, the IP address is assigned according to a certain rule, and the IP address information can be used to know the location information of the device corresponding to the IP address or ISP information providing the Internet service to the device.
However, the information stored in the DNS database can be accessed only through a DNS server, and thus the access is very limited. Therefore, it is difficult for a service provider to obtain information such as IP address information directly from the DNS database.
Therefore, there is a problem in that a separate database storing IP address information and information matching the same is provided to another device or used only with the stored information.
Therefore, there is a problem that the provision of a user-customized service using IP address information is limited.
In order to solve the conventional problems as described above, it is to propose a method and apparatus for obtaining information stored in the database of the domain name system that can directly obtain information stored in the DNS database through the DNS server.
Therefore, the present invention proposes a method and apparatus for acquiring information stored in a database of a domain name system capable of providing a customized service using IP address information without constructing or using a separate database.
Still other objects of the present invention will be readily understood through the following description of the embodiments.
In order to achieve the above object, according to an aspect of the present invention there is provided a method of obtaining information stored in a database of a domain name system.
According to a preferred embodiment of the present invention, in a method of obtaining information stored in the database of the DNS performed by a host server in a domain name system (DNS), a DNS query is generated by Transmit to a DNS server and receive a response of the DNS query from the DNS server, wherein the DNS query is generated using client IP (Internet Protocol) address information, and the DNS server transmits the client IP address information to the DNS query. When is included, information matching the client IP address information stored in the database of the DNS is provided to obtain the information stored in the database of the DNS, characterized in that for transmitting to the host server in response to the DNS query.
The generation of the DNS query may be performed using the same library as the library used when generating the DNS query in the DNS system.
The generated DNS query may be a query statement by Request For Comments (RFC).
Information matching the received client IP address information may be used for a service provided by the host server.
The information matching the client IP address information may be information including at least one of location information of the client and Internet service provider (ISP) information subscribed to the client.
The DNS system further includes a local DNS server, the local DNS server may receive the DNS query from the host server, and send the DNS query to a DNS server that is authorized to the received DNS query.
The protocol for transmitting the DNS query and the response of the DNS query may be Domain Name System Security Extensions (DNSSEC).
According to another aspect of the present invention, an apparatus for obtaining information stored in a database of a domain name system is provided.
According to an embodiment of the present invention, in the apparatus for obtaining information stored in the database (DatabBase) of the DNS in the Domain Name System (DNS), generating a DNS query using the client IP address information DNS query generation unit; And a client information receiver configured to receive, as a response to the DNS query, information matching the client IP address information stored in the database of the DNS from a DNS server. .
The DNS query generator may generate the DNS query using a library identical to a library used when generating a DNS query in the DNS system.
The DNS query generated by the DNS query generator may be a query statement by Request For Comments (RFC).
The apparatus for acquiring information stored in the database of the DNS may further include a client information providing unit configured to provide information matching the received client IP address information to be used for the service provided by the host server.
The information matching the client IP address information may be information including at least one of location information of the client and Internet service provider (ISP) information subscribed to the client.
The DNS system further includes a local DNS server, the local DNS server may receive the generated DNS query, and send the DNS query to a DNS server having authority to the received DNS query.
The protocol for transmitting the DNS query and the response of the DNS query may be Domain Name System Security Extensions (DNSSEC).
According to another aspect of the present invention, there is provided a recording medium recording a program for implementing a method of obtaining information stored in a database of a domain name system.
According to a preferred embodiment of the present invention, it can be executed by the digital processing apparatus so that a method of obtaining information stored in the database of the DNS performed by a host server in a domain name system (DNS) is implemented. A recording medium in which a program of instructions is tangibly embodied and records a program that can be read by a digital processing apparatus, the DNS query being generated and transmitted to a DNS server, and the DNS server responds to the DNS query. Receive the DNS query is generated using the client IP (Internet Protocol) address information, the DNS server is the client IP address information stored in the database of the DNS when the DNS query includes the client IP address information Information matched to the host server as a response to the DNS query. The recording a program for implementing the acquisition method of the information stored in the database, characterized in that the transmission DNS record medium.
The generation of the DNS query may be performed using the same library as the library used when generating the DNS query in the DNS system.
Information matching the received client IP address information may be used for a service provided by the host server.
The information matching the client IP address information may be information including at least one of location information of the client and Internet service provider (ISP) information subscribed to the client.
The DNS system may further include a local DNS server, the local DNS server may receive the DNS query from the host server, and transmit the DNS query to a DNS server having authority to the received DNS query.
The protocol for transmitting the DNS query and the response of the DNS query may be Domain Name System Security Extensions (DNSSEC).
As described above, the method and apparatus for obtaining information stored in a database of a domain name system according to the present invention has an advantage of directly obtaining information stored in a DNS database.
Therefore, there is an advantage in that it is possible to provide a user-customized service using IP address information without constructing or using a separate database.
As the invention allows for various changes and numerous embodiments, particular embodiments will be illustrated in the drawings and described in detail in the written description. However, this is not intended to limit the present invention to specific embodiments, it should be understood to include all modifications, equivalents, and substitutes included in the spirit and scope of the present invention.
In describing the drawings, similar reference numerals are used for similar elements. In the following description of the present invention, if it is determined that the detailed description of the related known technology may obscure the gist of the present invention, the detailed description thereof will be omitted.
Terms such as first and second may be used to describe various components, but the components should not be limited by the terms. The terms are used only for the purpose of distinguishing one component from another.
For example, without departing from the scope of the present invention, the first component may be referred to as the second component, and similarly, the second component may also be referred to as the first component.
The term and / or includes a combination of a plurality of related items or any item of a plurality of related items.
When a component is referred to as being "connected" or "connected" to another component, it may be directly connected to or connected to that other component, but it may be understood that other components may be present in between. Should be.
On the other hand, when a component is said to be "directly connected" or "directly connected" to another component, it should be understood that there is no other component in between.
The terminology used herein is for the purpose of describing particular example embodiments only and is not intended to be limiting of the present invention.
Singular expressions include plural expressions unless the context clearly indicates otherwise. In this application, the terms "comprise" or "have" are intended to indicate that there is a feature, number, step, operation, component, part, or combination thereof described in the specification, and one or more other features. It is to be understood that the present invention does not exclude the possibility of the presence or the addition of numbers, steps, operations, components, components, or a combination thereof.
Unless defined otherwise, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art.
Terms such as those defined in the commonly used dictionaries should be construed as having meanings consistent with the meanings in the context of the related art, and are not construed in ideal or excessively formal meanings unless expressly defined in this application. Do not.
Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings, and the same or corresponding components will be denoted by the same reference numerals regardless of the reference numerals and redundant description thereof will be omitted.
First, a configuration of a domain name system to which a method for obtaining information stored in a database of a domain name system according to an exemplary embodiment of the present invention may be applied will be described with reference to FIGS. 1 and 2.
1 is a diagram illustrating a configuration of a domain name system to which a method for obtaining information stored in a database of a domain name system according to an exemplary embodiment of the present invention may be applied, and FIG. 2 illustrates an exemplary embodiment of the present invention. FIG. 4 is a diagram illustrating another configuration of a domain name system to which a method of obtaining information stored in a database of the domain name system can be applied.
Compared to FIG. 1, in FIG. 2, the client 100 may further include a local DNS server 105 connected for the first time and connected to the DNS server 110.
When the domain name system forms a hierarchical structure by further including such a local DNS server 105, the local DNS server 105 first receives the IP address information request from the client 100 according to the present invention. In this case, the request may be transmitted back to the DNS server 110 having the authority of the corresponding domain name.
Hereinafter, a description will be given of a domain name system to which a method for obtaining information stored in a database of a domain name system according to the present invention can be applied.
As shown in FIG. 1, a Domain Name System (DNS) to which the present invention can be applied includes a client 100, a DNS server 110, a DNS DB (DataBase) 120, and a host server 130. It may include.
Meanwhile, in FIG. 1, only one component is illustrated for convenience of description, but one or more components may be present.
First, the client 100 is a device that is connected through a communication network to access the DNS server 110 and the host server 130.
If the client 100 has a communication function and can be connected to the DNS server 110 and the host server 130, there is no limitation.
The client 100 may be, for example, a wireless terminal such as a user personal computer (PC), a mobile phone, a personal digital assistant (PDA), and the like, but is not limited thereto.
DNS server 110 receives the domain name information entered in the address input window of the web browser (web browser) installed in the client 100 and receives the IP address information stored in the DNS DB 120 matching the received domain name information Read it and send it to the client 100.
The client 100 receiving the IP address information connects to the host server 130 which is a server corresponding to the domain name entered into the web browser using the received IP address information.
DNS DB 120 stores the IP address information matching the domain name. In addition, location information according to an IP address or ISP information for providing an Internet service to a corresponding device may be stored.
The host server 130 is a server providing a specific service to the client 100 and may include both a web server providing a web page to a user through a web browser installed on the client 100 or a content server providing specific content. have.
Meanwhile, when the client 100 receives IP address information through the DNS server 110 and accesses the host server 130, the host server 130 according to the present invention receives IP address information of the connected client 100. Generates a DNS query used and transmits to the DNS server (110).
This DNS query is generated as a DNS query that satisfies the regulations according to the RFC, which is a common convention of the aforementioned domain name system.
Meanwhile, the DNS server 110 receiving the DNS query reads the information matching the IP address information from the DNS DB 120 using the query and transmits the information to the host server 130 again.
The host server 130 receives the information matching the IP address information from the DNS server 110 from the DNS server 110 to provide a user-customized service using the received information.
For example, the IP address of the client 100 is 1.2.3.4, the host server 110 sets the resource record type to TXT, and the DNS query 4.3.2.1.city.service ?? domain.com. It generates and transmits to the DNS server 110.
On the other hand, if the IP address of the client 100 is 1.2.3.4, the IP address in the query is expressed as 4.3.2.1 because the interpretation of the query is performed later, but is not limited thereto.
The DNS server 110 that receives the query has a resource type that matches the IP address of the client in the DNS DB 120 when the DNS query, that is, the form of * .city.service ?? domain.com is 1.2.3.4. The information corresponding to the TXT type is read and transmitted to the host server 130.
Such a DNS query may be generated in the form of a query statement, and the DNS query statement is formed using the form according to the RFC as described above.
Therefore, the host server 130 includes the received IP address information of the client 100 and automatically generates a query statement according to the RFC regulations and transmits the information to the DNS server 110 to receive the information stored in the DNS database 120. The received information will be available.
On the other hand, looking at the example of the query by the RFC regulations, not only the above-mentioned TXT but also various query statements are possible, by using this, it is possible to extract various types of information from the information stored in the DNS database 120.
Meanwhile, in the structure of the domain name system including the local DNS server 105 as shown in FIG. 2, DNS queries are transmitted to the local DNS server 105, and the local DNS server 105 has authority of city.service ?? domain.com. The DNS query is sent to the DNS server 110 having the authority.
On the other hand, in general, the DNS server 110 or the local DNS server 105 temporarily stores the received DNS query from the DNS server 110 for a preset time to live (TTL) time or the corresponding DNS server 105 or local If the DNS server 105 is not authorized, the DNS server 105 may be connected to another DNS server 110 or the local DNS server 105.
Therefore, when a plurality of DNS queries for requesting information stored in the DNS DB 120 are received, the load of the DNS server 110 itself may be reduced.
On the other hand, as described above to read and transmit the information stored in the DNS DB 120 in the DNS server 110 in accordance with the present invention will use the conventional DNS-related protocols as it is.
In general, devices such as servers or clients connected through the Internet have a DNS library for generating DNS queries for connecting to the DNS server 110.
The main library used when transmitting a DNS query to the DNS server 110 is 'gethostbyaddr', and the main library used when requesting a specific type of resource record is 'res_query'.
gethostbyaddr is for matching hostnames to IP addresses, and res_query is a library for specifying hostnames, classes, and types.
In addition, 'res_nquery' is a library used to specify a DNS server to send a query separately. It is a library related to host name, class, and type specification related to the resolution of DNS queries.
Therefore, in the present invention, by using the conventional library as it is to generate a DNS query to be transmitted to the DNS server 110, the information stored in the DNS DB 120 to the host server 130 without any change to the conventional DNS system 120 Can be received.
Therefore, the host server 130 can receive information stored in the DNS DB 120 without using a conventional domain name system as it is and performing a separate IP address tracking method in the host server 130. .
In addition, the host server 130 may provide various user-customized services using the information stored in the received DNS DB 120.
For example, the information on the region where the client 100 is located may be obtained through the client 100 IP address information of 1.2.3.4. By using this, even if the user does not specify a separate area, if the user wants the local information, the local information service of the area where the client 100 is located can be provided.
In addition, for example, if the registered ISP information is included, it is also possible to provide a customized advertisement by providing other Internet-related product advertisements provided by the subscribed ISP.
The method of using the information matching the IP address information can be variously implemented and is not limited to the above examples.
On the other hand, since the IP address information and location information and ISP information according to the IP address information may be important personal information, it may be required to strengthen the security.
In this case, instead of the general DNS protocol, it may be possible to protect the transmitted data by using DNSSEC (Domain Name System Security Extensions), which is an enhanced security protocol.
Hereinafter, with reference to Figure 3 will be described the order in which the method of obtaining information stored in the database of the domain name system according to an embodiment of the present invention.
3 is a flowchart illustrating an order in which a method of obtaining information stored in a database of a domain name system is performed according to an exemplary embodiment of the present invention.
As shown in FIG. 3, the method for acquiring information stored in a database of a domain name system according to an exemplary embodiment of the present invention first performs a query using a client 100 IP address information, that is, a DNS query in the host server 130. It transmits to the DNS server 110 (S300).
In addition, the DNS server 110 interprets the received DNS query to read the information matching the client 100 IP address information, that is, the client 100 information from the DNS DB 120, and the read client 100 information is the host. It is transmitted to the server 130 is received by the host server 130 (S302).
The host server 130 provides a user-customized service in the service originally provided by using the received information (S304).
On the other hand, the method of obtaining information stored in the database of the domain name system according to the present invention is implemented as a program and stored in a computer-readable recording medium (CD-ROM, RAM, ROM, floppy disk, hard disk, magneto-optical disk, etc.) Can be.
4 is a block diagram illustrating a configuration of an apparatus for obtaining information stored in a database of a domain name system according to an exemplary embodiment of the present invention.
As shown in FIG. 4, an apparatus for obtaining information stored in a database of a domain name system according to an exemplary embodiment of the present invention includes a DNS query generator 400, a client information receiver 410, and a client information provider ( 420.
First, the DNS query generator 400 generates a DNS query to query the DNS server 110 using the received IP address information of the client 120.
As described above, the DNS query can be generated using a DNS library for generating a conventional DNS query.
The client information receiver 410 receives the client 100 information transmitted by the DNS server 110 that receives the DNS query in response to the DNS query. As described above, the client 100 information may be information including at least one of location information and ISP information matching the IP address information.
The client information provider 420 provides the received client 100 information to a module related to a service provided by the host server 130 so that the service provided by the host server 130 may be provided as a user-customized service. .
Meanwhile, the apparatus for obtaining information stored in the database of the domain name system according to the present invention may be connected to a communication network as a separate device or included in the aforementioned host server to acquire information stored in the database of the domain name system.
In addition, the apparatus for obtaining information stored in the database of the domain name system according to the present invention may be implemented in a form in which a program in which the method for obtaining information stored in the database of the domain name system is implemented is installed in a digital device. It is self-evident.
Preferred embodiments of the present invention described above are disclosed for purposes of illustration, and those skilled in the art will be able to make various modifications, changes, and additions within the spirit and scope of the present invention. Additions should be considered to be within the scope of the following claims.
1 is a diagram illustrating a configuration of a domain name system to which a method for obtaining information stored in a database of a domain name system according to an exemplary embodiment of the present invention can be applied.
2 is a diagram illustrating another configuration of a domain name system to which a method for obtaining information stored in a database of a domain name system according to an exemplary embodiment of the present invention can be applied.
Figure 3 is a flow chart showing the order in which the method of obtaining information stored in the database of the domain name system according to an embodiment of the present invention is performed.
4 is a block diagram showing the configuration of an apparatus for obtaining information stored in a database of a domain name system according to an embodiment of the present invention.

Claims (15)

  1. In the method of obtaining information stored in the database (DataBase) of the DNS performed by the host server in the Domain Name System (DNS),
    Generate and send a DNS query to the DNS server, and receives the response of the DNS query from the DNS server,
    The DNS query is generated using client IP (Internet Protocol) address information.
    The DNS server, when the DNS query includes the client IP address information, DNS, characterized in that for transmitting the information matching the client IP address information stored in the database of the DNS to the host server in response to the DNS query Method of obtaining information stored in the database.
  2. The method of claim 1,
    The generation of the DNS query is a method of obtaining information stored in a database of the DNS, characterized in that performed using the same library (library) used in the generation of the DNS query in the DNS system.
  3. The method of claim 1,
    The generated DNS query is a query statement by Request For Comments (RFC), the method of obtaining information stored in the database of the DNS.
  4. The method of claim 1,
    Obtaining information stored in a database of DNS, wherein information matching the received client IP address information is used for a service provided by the host server.
  5. The method of claim 1,
    And the information matching the client IP address information is information including at least one of location information of the client and Internet service provider (ISP) information to which the client has subscribed.
  6. The method of claim 1,
    The DNS system further includes a local DNS server,
    And the local DNS server receives the DNS query from the host server, and transmits the DNS query to a DNS server having authority with respect to the received DNS query.
  7. The method of claim 1,
    The protocol for transmitting the DNS query and the response of the DNS query is Domain Name System Security Extensions (DNSEC).
  8. In the apparatus for obtaining information stored in the database (DatabBase) of the DNS in the Domain Name System (DNS: Domain Name System),
    A DNS query generating unit generating a DNS query using client IP (Internet Protocol) address information; And
    And a client information receiver configured to receive, from the DNS server, information matching the client IP address information stored in the database of the DNS as a response to the DNS query.
  9. The method of claim 8,
    And the DNS query generator is configured to generate the DNS query using a library identical to a library used when generating the DNS query in the DNS system.
  10. The method of claim 8,
    The DNS query generated by the DNS query generating unit is a method for obtaining information stored in a database of the DNS, characterized in that the query by RFC (Request For Comments).
  11. The method of claim 8,
    The apparatus for acquiring information stored in the database of the DNS further includes a client information providing unit which provides information matching the received client IP address information to be used for the service provided by the host server. Device for obtaining information.
  12. The method of claim 8,
    And the information matching the client IP address information is information including at least one of location information of the client and Internet service provider (ISP) information to which the client subscribes.
  13. The method of claim 8,
    The DNS system further includes a local DNS server,
    And the local DNS server receives the generated DNS query and transmits the DNS query to a DNS server having authority for the received DNS query.
  14. The method of claim 8,
    The protocol for transmitting the DNS query and the response of the DNS query is Domain Name System Security Extensions (DNSEC).
  15. In order to implement a method of obtaining information stored in the database of the DNS performed by a host server in a Domain Name System (DNS), a program of instructions that can be executed by a digital processing apparatus is tangibly implemented. A recording medium having recorded thereon a program that can be read by a digital processing device,
    Generate and send a DNS query to the DNS server, and receives the response of the DNS query from the DNS server,
    The DNS query is generated using client IP (Internet Protocol) address information.
    The DNS server, when the DNS query includes the client IP address information, DNS, characterized in that for transmitting the information matching the client IP address information stored in the database of the DNS to the host server in response to the DNS query Recording medium recording a program for implementing a method of obtaining information stored in a database of the.
KR20080068432A 2008-07-15 2008-07-15 Method and apparatus for getting information in database of Domain Name System KR101005778B1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
KR20080068432A KR101005778B1 (en) 2008-07-15 2008-07-15 Method and apparatus for getting information in database of Domain Name System

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR20080068432A KR101005778B1 (en) 2008-07-15 2008-07-15 Method and apparatus for getting information in database of Domain Name System
PCT/KR2009/003876 WO2010008190A2 (en) 2008-07-15 2009-07-15 Method and apparatus for acquiring information stored in a database of a domain name system

Publications (2)

Publication Number Publication Date
KR20100008043A true KR20100008043A (en) 2010-01-25
KR101005778B1 KR101005778B1 (en) 2011-01-06

Family

ID=41550834

Family Applications (1)

Application Number Title Priority Date Filing Date
KR20080068432A KR101005778B1 (en) 2008-07-15 2008-07-15 Method and apparatus for getting information in database of Domain Name System

Country Status (2)

Country Link
KR (1) KR101005778B1 (en)
WO (1) WO2010008190A2 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015030270A1 (en) * 2013-08-26 2015-03-05 Seo Jeong Hoan Domain name system and domain name service method based on user information

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20010104538A (en) * 2000-05-15 2001-11-26 최성호 Method for transmitting the applicable language to its original site by translating the announced speechs
JP2004266568A (en) * 2003-02-28 2004-09-24 Nec Corp Name resolution server and packet transfer apparatus
JP4362487B2 (en) * 2006-03-06 2009-11-11 日本電信電話株式会社 DNS server client system, DNS server device, cache server device, DNS query request control method, and DNS query request control program

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015030270A1 (en) * 2013-08-26 2015-03-05 Seo Jeong Hoan Domain name system and domain name service method based on user information
CN104798343A (en) * 2013-08-26 2015-07-22 徐正焕 Domain name system (dns) and domain name service method based on user information
CN104798343B (en) * 2013-08-26 2018-04-10 徐正焕 Domain name system (DNS) and domain name service method based on user profile
US10313299B2 (en) 2013-08-26 2019-06-04 Jeong Hoan Seo Domain name system (DNS) and domain name service method based on user information

Also Published As

Publication number Publication date
WO2010008190A4 (en) 2010-07-15
KR101005778B1 (en) 2011-01-06
WO2010008190A3 (en) 2010-05-27
WO2010008190A2 (en) 2010-01-21

Similar Documents

Publication Publication Date Title
US10148612B2 (en) Method and system for increasing speed of domain name system resolution within a computing device
US10742550B2 (en) Updating routing information based on client location
US10797995B2 (en) Request routing based on class
US10104058B2 (en) Content restriction compliance using reverse DNS lookup
US20180205697A1 (en) Managing content delivery network service providers by a content broker
US10264062B2 (en) Request routing using a popularity identifier to identify a cache component
US10931738B2 (en) Point of presence management in request routing
US9935921B2 (en) Correlating nameserver IPv6 and IPv4 addresses
US20170257340A1 (en) Managing request routing information utilizing client identifiers
US9628554B2 (en) Dynamic content delivery
US20180302465A1 (en) Point of presence management in request routing
US20190044787A1 (en) Point of presence management in request routing
US10225362B2 (en) Processing DNS queries to identify pre-processing information
US9608957B2 (en) Request routing using network computing components
US10523783B2 (en) Request routing utilizing client location information
Cheshire et al. DNS-based service discovery
US9800539B2 (en) Request routing management based on network components
US7225272B2 (en) Method and apparatus for providing name services
US7502923B2 (en) Systems and methods for secured domain name system use based on pre-existing trust
US8751586B2 (en) Domain name control based social website account authentication
CN106068639B (en) The Transparent Proxy certification handled by DNS
US9712422B2 (en) Selection of service nodes for provision of services
US9451046B2 (en) Managing CDN registration by a storage provider
US8606926B2 (en) Recursive DNS nameserver
EP2356577B1 (en) Request routing and updating routing information utilizing client location information

Legal Events

Date Code Title Description
A201 Request for examination
AMND Amendment
E902 Notification of reason for refusal
AMND Amendment
E601 Decision to refuse application
J201 Request for trial against refusal decision
AMND Amendment
B701 Decision to grant
GRNT Written decision to grant
FPAY Annual fee payment

Payment date: 20131031

Year of fee payment: 4

FPAY Annual fee payment

Payment date: 20141125

Year of fee payment: 5

FPAY Annual fee payment

Payment date: 20161226

Year of fee payment: 7

FPAY Annual fee payment

Payment date: 20171220

Year of fee payment: 8

FPAY Annual fee payment

Payment date: 20191106

Year of fee payment: 10