CN107613039B - IP address attribution query method, device, system and storage medium - Google Patents

Abstract

The present disclosure provides a method, device, system and storage medium for IP address attribution query. The method includes: converting an IP address of a user terminal into a target domain name; sending a query request carrying the target domain name to a DNS server, The query request instructs the DNS server to query the reference domain name corresponding to the target domain name, where the reference domain name is used to identify the IP address range to which the IP address belongs; receive the reference domain name returned by the DNS server; based on a preset correspondence Searching for the attribution corresponding to the reference domain name, determining the attribution found as the attribution of the IP address, and the preset correspondence is a pre-stored correspondence between the reference domain name and the attribution. By applying the solution of the present disclosure, the query efficiency of the IP address attribution can be improved.

Description

IP address attribution query method, device, system and storage medium

technical field

The present application relates to the field of communication technologies, and in particular, to a method, device, system and storage medium for querying IP address attribution.

Background technique

IP address refers to the Internet Protocol Address (English: Internet Protocol Address, also translated as Internet Protocol Address). The IP address is a unified address format provided by the IP protocol. It assigns a logical address to each network and each host on the Internet, thereby shielding the difference in physical addresses.

The IP address attribution query is a very common requirement. The IP address in the user request is used to query which province, city or operator the IP address belongs to. Generally, IP addresses are allocated in segments, and a set of IP addresses in a continuous range is allocated to a province, city or operator. For example, IPs belonging to the IP address range 1.23.64.0 to 1.23.74.255 belong to region A, and IPs belonging to the IP address range 1.23.75.0 to 1.23.79.255 belong to region B. It can be seen that the user's IP address 1.23.78.33 falls within the IP address range of region B, which means that the IP address belongs to region B.

In the related art, the IP address range to which the IP address belongs is often queried from the database, and then the attribution of the IP address is determined. Since the database is stored in the hard disk, the data needs to be read from the hard disk when querying the attribution of the IP address, resulting in low query efficiency. .

SUMMARY OF THE INVENTION

In order to overcome the problems existing in the related art, the present disclosure provides a method, apparatus, system and storage medium for IP address attribution query.

According to a first aspect of the embodiments of the present disclosure, a method for querying IP address attribution is provided. The method is applied to a query server, and the method includes:

Convert the IP address of the user terminal to the target domain name;

Send a query request carrying the target domain name to the DNS (Domain Name System, domain name system) server, the query request instructing the DNS server to query the reference domain name corresponding to the target domain name, and the reference domain name is used for Identifies the IP address range to which the IP address belongs;

Receive the base domain name returned by the DNS server;

Based on a preset correspondence relationship, the attribution corresponding to the reference domain name is searched, and the found attribution is determined as the attribution of the IP address, and the preset correspondence is a pre-stored correspondence between the reference domain name and the attribution.

In an optional implementation, converting the IP address of the user terminal into the target domain name includes:

Convert IP addresses to numbers;

The number is combined with the preset top-level domain to obtain the target domain name corresponding to the IP address.

In an optional implementation manner, the converting the IP address into a number may include:

Convert the decimal number to hexadecimal number of each byte in the IP address;

Combine the hexadecimal numbers obtained by converting each byte in the order of bytes in the IP address to obtain a hexadecimal number;

Convert the hexadecimal number obtained by the combination into a decimal number to obtain the number corresponding to the IP address.

In an optional implementation manner, the reference domain name is obtained by domain name conversion based on the upper limit IP address in the IP address range to which the IP address belongs.

According to a second aspect of the embodiments of the present disclosure, a method for querying IP address attribution is provided. The method is applied to a DNS server, and the method includes:

receiving a query request sent by the query server, where the query request carries a target domain name corresponding to the IP address;

Query a reference domain name corresponding to the target domain name based on the query request, where the reference domain name is used to identify the IP address range to which the IP address belongs;

Send the reference domain name to the query server, so that the query server searches for the attribution corresponding to the reference domain name based on the preset correspondence, and determines the found attribution as the attribution of the IP address. The preset corresponding relationship is the corresponding relationship between the pre-stored reference domain name and the attribution.

In an optional implementation manner, the querying the reference domain name corresponding to the target domain name based on the query request includes:

The reference domain name corresponding to the target domain name is queried from the zone file. The zone file is obtained by using the DNSSEC (Domain Name System Security Extensions, Domain Name System Security Extensions) protocol to sign the reference domain name in the DNS. The reference domain name is based on the The upper limit IP address in the IP address range to which the IP address belongs is obtained by performing domain name conversion.

In an optional implementation manner, the record set of each reference domain name in the zone file is sorted according to a preset policy, and the record set at least includes a next security record (Next Secure, which may be referred to as an NESC record), so The name of the base domain name in which the next record set is recorded in the NESC record;

The querying the reference domain name corresponding to the target domain name from the zone file includes:

Query the target domain name from the zone file, when the target domain name is between the first benchmark domain name and the second benchmark domain name, send the NESC record in the record set of the first benchmark domain name to the query server ;

The name of the second benchmark domain name is recorded in the sent NESC record, the first benchmark domain name and the second benchmark domain name are adjacent benchmark domain names in the zone file, and the first benchmark domain name is arranged before the second benchmark domain name .

According to a third aspect of the embodiments of the present disclosure, an apparatus for querying IP address attribution is provided, and the apparatus includes:

The information conversion module is configured to convert the IP address of the user terminal into the target domain name;

The information communication module is configured to send a query request carrying the target domain name to the DNS server, and receive the reference domain name returned by the DNS server; the query request instructs the DNS server to query the reference domain name corresponding to the target domain name , the reference domain name is used to identify the IP address range to which the IP address belongs;

The attribution determination module is configured to search for the attribution corresponding to the reference domain name based on a preset correspondence, and determine the found attribution as the attribution of the IP address, and the preset correspondence is a pre-stored reference domain name Correspondence with the place of belonging.

In an optional implementation manner, the information conversion module is specifically configured as:

Convert IP addresses to numbers;

The number is combined with the preset top-level domain to obtain the target domain name corresponding to the IP address.

In an optional implementation manner, the information conversion module is specifically configured as:

Convert the decimal number to hexadecimal number of each byte in the IP address;

Combine the hexadecimal numbers obtained by converting each byte in the order of bytes in the IP address to obtain a hexadecimal number;

Convert the hexadecimal number obtained by the combination into a decimal number to obtain the number corresponding to the IP address.

In an optional implementation manner, the reference domain name is obtained by domain name conversion based on the upper limit IP address in the IP address range to which the IP address belongs.

According to a fourth aspect of the embodiments of the present disclosure, there is provided a device for querying IP address attribution, the device comprising:

an information communication module, configured to receive a query request sent by the query server, where the query request carries a target domain name corresponding to the IP address;

a domain name query module, configured to query a reference domain name corresponding to the target domain name based on the query request, where the reference domain name is used to identify the IP address range to which the IP address belongs;

The information communication module is further configured to send the reference domain name to the query server, so that the query server searches for the attribution corresponding to the reference domain name based on the preset correspondence, and determines the found attribution as: The attribution of the IP address, and the preset correspondence is the correspondence between the pre-stored reference domain name and the attribution.

In an optional implementation manner, the domain name query module is specifically configured as:

The reference domain name corresponding to the target domain name is queried from the zone file. The zone file is obtained by using the DNSSEC protocol to sign the reference domain name in the DNS. The reference domain name is based on the upper limit of the IP address range to which the IP address belongs. The IP address is obtained by domain name conversion.

In an optional implementation manner, the record sets of each reference domain name in the zone file are sorted according to a preset policy, the record set includes at least NESC records, and the NESC records record the benchmark of the next record set the name of the domain name;

The domain name query module is specifically configured as:

Query the target domain name from the zone file, when the target domain name is between the first benchmark domain name and the second benchmark domain name, send the NESC record in the record set of the first benchmark domain name to the query server ;

The name of the second benchmark domain name is recorded in the sent NESC record, the first benchmark domain name and the second benchmark domain name are adjacent benchmark domain names in the zone file, and the first benchmark domain name is arranged before the second benchmark domain name .

According to a fifth aspect of the embodiments of the present disclosure, there is provided an IP address attribution query system, the system includes a query server and a DNS server;

The query server converts the IP address of the user terminal into a target domain name, and sends a query request carrying the target domain name to the DNS server;

The DNS server queries the reference domain name corresponding to the target domain name based on the query request, and sends the reference domain name to the query server, where the reference domain name is used to identify the IP address range to which the IP address belongs ;

The query server searches for an attribution corresponding to the reference domain name based on a preset correspondence, and determines the found attribution as the attribution of the IP address, and the preset correspondence is a pre-stored reference domain name and attribution Correspondence to the ground.

According to a sixth aspect of the embodiments of the present disclosure, there is provided an IP address attribution query apparatus, comprising: a processor; a memory for storing instructions executable by the processor; wherein the processor is configured to:

Convert the IP address of the user terminal to the target domain name;

Send a query request carrying the target domain name to the DNS server, where the query request instructs the DNS server to query the reference domain name corresponding to the target domain name, and the reference domain name is used to identify the IP address range to which the IP address belongs ;

Receive the base domain name returned by the DNS server;

Based on a preset correspondence relationship, the attribution corresponding to the reference domain name is searched, and the found attribution is determined as the attribution of the IP address, and the preset correspondence is a pre-stored correspondence between the reference domain name and the attribution.

According to a seventh aspect of the embodiments of the present disclosure, there is provided an IP address attribution query apparatus, comprising: a processor; a memory for storing instructions executable by the processor; wherein the processor is configured to:

receiving a query request sent by the query server, where the query request carries a target domain name corresponding to the IP address;

Query a reference domain name corresponding to the target domain name based on the query request, where the reference domain name is used to identify the IP address range to which the IP address belongs;

Send the reference domain name to the query server, so that the query server searches for the attribution corresponding to the reference domain name based on the preset correspondence, and determines the found attribution as the attribution of the IP address. The preset corresponding relationship is the corresponding relationship between the pre-stored reference domain name and the attribution.

According to an eighth aspect of the embodiments of the present disclosure, there is provided a computer-readable storage medium on which a computer program is stored, and when the program is executed by a processor, implements the steps of the above-mentioned method for querying IP address attribution in a query server by an application.

According to a ninth aspect of the embodiments of the present disclosure, there is provided a computer-readable storage medium on which a computer program is stored, and when the program is executed by a processor, implements the steps of the above application method for IP address attribution in a DNS server.

The technical solutions provided by the embodiments of the present disclosure may include the following beneficial effects:

The embodiment of the present disclosure converts the IP address of the user terminal into the target domain name through the query server, and sends the target domain name to the DNS server. The DNS server queries the reference domain name corresponding to the target domain name based on the query request, because the reference domain name is used to identify The IP address range to which the IP address belongs. Therefore, after the DNS server sends the reference domain name to the query server, the query server can search for the attribution corresponding to the reference domain name based on the preset correspondence, so that the found attribution It is determined as the attribution of the IP address, so as to quickly query the attribution of the IP address.

It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure.

Description of drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description serve to explain the principles of the disclosure.

FIG. 1 is a network architecture diagram of IP address attribution query according to an exemplary embodiment of the present disclosure.

FIG. 2 is a flowchart of a method for querying IP address attribution according to an exemplary embodiment of the present disclosure.

Fig. 3 is a flowchart of another IP address attribution query method according to an exemplary embodiment of the present disclosure.

FIG. 4 is a flowchart of a process of generating a zone file according to an exemplary embodiment of the present disclosure.

FIG. 5 is an interactive schematic diagram of a method for querying IP address attribution according to an exemplary embodiment of the present disclosure.

Fig. 6 is a block diagram of an IP address attribution query system according to an exemplary embodiment of the present disclosure.

FIG. 7 is a block diagram of a device for querying IP address attribution according to an exemplary embodiment of the present disclosure.

Fig. 8 is a block diagram of another apparatus for querying IP address attribution according to an exemplary embodiment of the present disclosure.

Fig. 9 is a block diagram of an apparatus for IP address attribution query according to an exemplary embodiment of the present application.

Fig. 10 is a block diagram of another apparatus for IP address attribution query according to an exemplary embodiment of the present application.

Detailed ways

Exemplary embodiments will be described in detail herein, examples of which are illustrated in the accompanying drawings. Where the following description refers to the drawings, the same numerals in different drawings refer to the same or similar elements unless otherwise indicated. The implementations described in the illustrative examples below are not intended to represent all implementations consistent with this disclosure. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present disclosure as recited in the appended claims.

The terminology used in the present disclosure is for the purpose of describing particular embodiments only and is not intended to limit the present disclosure. As used in this disclosure and the appended claims, the singular forms "a," "the," and "the" are intended to include the plural forms as well, unless the context clearly dictates otherwise. It will also be understood that the term "and/or" as used herein refers to and includes any and all possible combinations of one or more of the associated listed items.

It should be understood that although the terms first, second, third, etc. may be used in this disclosure to describe various pieces of information, such information should not be limited by these terms. These terms are only used to distinguish the same type of information from each other. For example, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information, without departing from the scope of the present disclosure. Depending on the context, the word "if" as used herein can be interpreted as "at the time of" or "when" or "in response to determining."

In order to better understand the IP address attribution query method, device, system and storage medium disclosed in the present invention, the DNS and DNSSEC protocols will be introduced first. Domain Name System (DNS) is a distributed database on the Internet that maps domain names and IP addresses to each other. DNS includes a series of records that describe names, IP addresses, and other information about hosts. These databases reside in DNS servers. In the DNS system, common resource record types are:

Host record (A record): As defined by RFC 1035, A record is an important record for name resolution, which maps a specific host name to the IP address of the corresponding host. Among them, Request For Comments, abbreviated as RFC, can be a series of memorandums issued by the Internet Engineering Task Force (IETF).

Alias record (CNAME record): As defined in RFC 1035, a CNAME record is used to point an alias to an A record, so that there is no need to create a new A record for a new name.

IPv6 (Internet Protocol version 6, Internet Protocol version 6) host record (AAAA record or IPv6 IP address record): defined by RFC 3596, corresponding to the A record, used to map a specific host name to a host's IPv6 address.

Service Location Record (SRV Record): Defined by RFC 2782 to define the location of a server that provides a specific service, such as host (hostname), port (port number), etc.

Named Management Pointer (NAPTR record): Defined by RFC 3403, it provides a regular expression way to map a domain name. A well-known application of NAPTR records is for ENUM queries.

The Domain Name System Security Extensions (DNSSEC) protocol is a security protocol based on the DNS protocol. It adds a layer of security to the DNS by signing the original DNS zone file. It adds RRSIG (Resource Record Signature, resource record signature), DNSKEY (DNS Public Key, DNS public key), DS (Delegation Signer) to the existing record types of the original DNS such as A, AAAA, NS, CNAME, etc. , representing the signer), NSEC (Next Secure, next security record) and other new records, each record of the same domain name constitutes the record set of the domain name. The zone file signed by DNSSEC can be a total record set after sorting the record set according to a preset policy (such as alphabetical ordering), and each domain name record set has a corresponding NSEC record, which identifies the domain name What types of records are there and who is its next domain name. NSEC records are automatically generated when zone data is signed. For example, an NSEC record will be inserted between vpn.test.net and xyz.test.net. The NSEC record can include two contents: the name of the next resource record after sorting (xyz.test.net.), and vpn.test .net. All resource record types (A, RRSIG, NSEC), etc. with this name. When a domain name requested by the user is between vpn and xyz, such as www.test.net., the DNS server will return that the domain name does not exist and return the NSEC record of vpn.test.net.

In addition, the application scenarios used by the embodiments of the present disclosure are also described. As shown in FIG. 1 , FIG. 1 is a network architecture diagram of IP address attribution query according to an exemplary embodiment of the present disclosure. The network architecture includes a user terminal, a query server and a DNS server. The user terminal may be a smart phone, a tablet computer, a PDA (Personal Digital Assistant, personal digital assistant), an e-book reader, a multimedia player, and the like. The query server may be a server that can query the attribution of an IP address, and the server may be a server, a server cluster, a cloud platform, or the like. For example, the query server can be a web server. The DNS server is a server with DNS, and the server can be a server, a server cluster, or a cloud platform.

In the related art, the IP address range to which the IP address belongs is often queried from the database, and then the attribution of the IP address is determined. Since the database is stored in the hard disk, the data needs to be read from the hard disk when querying the attribution of the IP address, resulting in low query efficiency. .

In order to avoid the defect of low query efficiency in the related art, the present disclosure provides an IP address attribution query method, which can be applied to the network architecture shown in FIG. , and send the target domain name to the DNS server. The DNS server queries the reference domain name corresponding to the target domain name based on the query request. Since the reference domain name is used to identify the IP address range to which the IP address belongs, and the IP address range corresponds to the attribution, therefore, after the DNS server sends the reference domain name to the query server, the query server can search and The attribution corresponding to the reference domain name is determined, so that the found attribution is determined as the attribution of the IP address, so that the attribution of the IP address can be quickly inquired. The embodiments of the present disclosure will be exemplified below with reference to the accompanying drawings.

First, an introduction is made from the query server. As shown in FIG. 2, FIG. 2 is a flowchart of an IP address attribution query method according to an exemplary embodiment of the present disclosure. The method is applied to the query server. Methods include:

In step 201, the IP address of the user terminal is converted into a target domain name. IP is an abbreviation for network protocols, and network protocol addresses are often abbreviated as IP addresses.

In step 202, a query request carrying the target domain name is sent to the DNS server, the query request instructing the DNS server to query a reference domain name corresponding to the target domain name, and the reference domain name is used to identify the IP address The home IP address range. DNS is an abbreviation for Domain Name System, and the domain name system server is often abbreviated as DNS server.

In step 203, the reference domain name returned by the DNS server is received.

In step 204, the attribution corresponding to the reference domain name is searched based on a preset correspondence relationship, and the found attribution is determined as the attribution of the IP address, and the preset correspondence is a pre-stored reference domain name and attribution Correspondence to the ground.

Next, introduce from the DNS server, as shown in FIG. 3 , which is a flowchart of another IP address attribution query method shown in the present disclosure according to an exemplary embodiment, and the method is applied to the DNS server, The method includes:

In step 301, a query request sent by a query server is received, where the query request carries a target domain name corresponding to an IP address.

In step 302, a reference domain name corresponding to the target domain name is queried based on the query request, where the reference domain name is used to identify the IP address range to which the IP address belongs.

In step 303, the reference domain name is sent to the query server, so that the query server searches for an attribution corresponding to the reference domain name based on a preset correspondence, and determines the found attribution as the IP address The preset correspondence is the correspondence between the pre-stored reference domain name and the attribution.

In order to better understand the IP address attribution query method disclosed by the present invention, the embodiments of the present disclosure are described in conjunction with the embodiment applied to the query server and the embodiment applied to the DNS server.

The user terminal may send an HTTP (HyperText Transfer Protocol, hypertext transfer protocol) request to the query server, where the HTTP request carries the IP address of the user terminal. In the query server, the IP address of the user terminal can be converted into the target domain name according to a preset conversion strategy. The target domain name is a type of domain name. In order to distinguish it from the subsequent reference domain name, the domain name obtained by domain name conversion of the IP address of the user terminal is called the target domain name.

In one embodiment, the correspondence between different target domain names and IP addresses may be pre-stored, and after obtaining the IP address of the user terminal, the target domain name corresponding to the IP address of the user terminal may be queried from the correspondence between the domain name and the IP address , thereby converting the IP address of the user terminal into the target domain name, for example, converting the IP address (208.80.152.2) into the target domain name (www.wikipedia.org).

Due to the large number of IP addresses, the corresponding relationship between domain names and IP addresses has a relatively large amount of information. In order to improve the conversion efficiency of domain names, in another embodiment, the IP addresses can be combined with a preset top-level domain to form a formal domain name. The preset top-level domain is a preset top-level domain, for example, it may be .com or .cn. The combination method can be to add the top-level domain name directly after the IP address. For example, translate the IP address (208.80.152.2) to the target domain name (208.80.152.2.com).

It can be seen that by adding a preset top-level domain name directly after the IP address, the domain name conversion efficiency can be improved, and there is no need to assign corresponding domain names to all IP addresses in advance to create a corresponding relationship between domain names and IP addresses.

In another embodiment, the IP address is a 32-bit binary number, usually divided into 4 groups of "8-bit binary numbers" (ie, 4 bytes). An IP address is usually expressed in the form of (a.b.c.d) in "dotted decimal", where a, b, c, and d are all decimal integers between 0 and 255. It can be understood that an IP address includes four sets of decimal numbers. Example: The dotted decimal IP address (100.4.5.6) is actually a 32-bit binary number (01100100.00000100.00000101.00000110). It can be seen that if a preset top-level domain name is added directly after the IP address, the domain name consisting of the IP address and the top-level domain name needs to be searched for subsequent domain name searches.

In order to improve the domain name conversion efficiency and improve the search efficiency during subsequent domain name searches, the converting the IP address of the user terminal into the target domain name includes:

Convert IP addresses to numbers;

The number is combined with the preset top-level domain to obtain the target domain name corresponding to the IP address.

It can be seen that the target domain name corresponding to the IP address is obtained by converting the dotted decimal represented by the IP address into a number, and combining the number with the preset top-level domain name, where the target domain name is a formal domain name. In subsequent domain name searches, the numbers are compared to improve search efficiency.

Regarding converting an IP address into a number, as one of the conversion methods, the converting an IP address into a number may include:

Convert the decimal number to hexadecimal number of each byte in the IP address;

Combine the hexadecimal numbers obtained by converting each byte in the order of bytes in the IP address to obtain a hexadecimal number;

Convert the hexadecimal number obtained by the combination to a decimal number, that is, to convert the IP address to a number.

Among them, the decimal number of each byte is equivalent to each group of decimal numbers, that is, each group of decimal numbers in the IP address is converted into hexadecimal numbers, and the hexadecimal numbers obtained by each group of conversion are in the order of the array in the IP address. Combining, combining to obtain a hexadecimal number, and converting the hexadecimal number obtained by combining to decimal, that is, converting the IP address into a number. Taking the IP address (a.b.c.d) including four groups (bytes) of a, b, c, and d as an example, convert the decimal a, b, c, and d to hexadecimal a', b', c' respectively , d', combine a', b', c', d' in the byte order of the IP address to obtain a hexadecimal number: a'b'c'd', combine the obtained a'b Convert 'c'd' to a decimal number to obtain the number corresponding to the IP address.

For example, for 1.23.74.255, the decimal number 1 in the first byte can be converted to hexadecimal number 01, the decimal number 23 in the second byte can be converted into hexadecimal number 17, and the third byte Convert the decimal data 74 to hexadecimal number 4A, convert the decimal number 255 of the fourth byte to hexadecimal number FF, combine the obtained hexadecimal numbers in byte order to obtain 1174AFF, and then convert 1174AFF Convert to decimal to get a string of numbers 18303743, which is the number corresponding to 1.23.74.255.

For another example, for 1.23.75.8, the decimal number 1 of the first byte can be converted to hexadecimal number 01, the decimal number 23 of the second byte can be converted to hexadecimal number 17, and the third byte can be converted to hexadecimal number 17. Convert the decimal data 75 of the section to hexadecimal number 4B, convert the decimal number 8 of the fourth byte to hexadecimal number 08, combine the obtained hexadecimal numbers in byte order to obtain 1174B08, and convert 1174B08 Convert to decimal to get a string of numbers 18303752, which is the number corresponding to 1.23.75.8.

Regarding the default top-level domain, the top-level domain (or top-level domain name; English: Top-level Domain; English abbreviation: TLD) is the highest-level domain in the Internet DNS hierarchy, which is stored in the namespace of the DNS root domain. The top-level domain is the last part of the domain name. For example, in the domain name of example.com, the top-level domain is .com (or .COM), and the case is considered the same.

Regarding the combination of numbers with the default top-level domain, in one example, numbers can be put into the default top-level domain as a first-level domain name. For example, assuming that the top-level domain is the .com domain, and the number obtained by IP address translation is 18303743, the combination obtains the target domain name: 18303743.com.

In the query server, after converting the IP address of the user terminal into the target domain name, a query request carrying the target domain name can be sent to the DNS server. The query request instructs the DNS server to query the reference domain name corresponding to the target domain name, where the reference domain name is used to identify the IP address range to which the IP address belongs.

In the DNS server, a query request sent by the query server is received, and the query request carries a target domain name corresponding to the IP address; the reference domain name corresponding to the target domain name is queried based on the query request. Since the reference domain name is used to identify the IP address range to which the IP address belongs, and the attribution can be determined based on the IP address range, after the DNS server sends the reference domain name to the query server, the query server can The preset correspondence relationship searches for the attribution corresponding to the reference domain name, so as to realize the IP address attribution query.

Regarding the query of the reference domain name corresponding to the target domain name based on the query request, in one example, the reference domain name corresponding to the target domain name may be queried from a zone file obtained by using the DNSSEC protocol to sign the reference domain name in the DNS , the reference domain name is obtained by domain name conversion based on the upper limit IP address in the IP address range to which the IP address belongs.

Since the reference domain name is obtained by domain name conversion based on the upper limit IP address in the IP address range to which the IP address belongs, an IP address range can be determined according to the reference domain name, and the IP address range is the IP address of the user terminal to which the IP address belongs. IP address range. It can be seen that, by querying the target domain name corresponding to the reference domain name, the IP address range to which the IP address belongs can be determined, thereby improving the query efficiency.

In one embodiment, the zone file may be pre-generated on the DNS server. As shown in FIG. 4 , FIG. 4 is a flowchart of a zone file generation process shown in the present disclosure according to an exemplary embodiment, including the following steps 401 and 402:

In step 401, domain name conversion is performed on the upper limit IP addresses in each IP address range to obtain a reference domain name.

Since IP addresses are allocated in segments, a set of IP addresses in a contiguous range is allocated to a province, city or operator. For example, IPs belonging to the IP address range 1.23.64.0 to 1.23.74.255 belong to region A, and IPs belonging to the IP address range 1.23.75.0 to 1.23.79.255 belong to region B.

In the adjacent IP address range, the upper limit IP address of the preceding IP address range is continuous with the lower limit IP address of the following IP address range, and there is no interval IP address. Therefore, the upper limit IP address in the IP address range can be used. or the lower bound IP address identifies the IP address range. As an implementation means, the embodiment of the present disclosure may use the upper limit IP address in the IP address range to identify the IP address range.

The so-called upper limit IP address is the largest IP address in the IP address range. For example, when the IP address range is 1.23.64.0 to 1.23.74.255, the upper limit IP address is 1.23.74.255, and when the IP address range is: 1.23.75.0 to 1.23.79.255, the upper limit IP address is 1.23.79.255. The so-called lower limit IP address is the smallest IP address in the IP address range. For example, when the IP address range is 1.23.64.0 to 1.23.74.255, the lower limit IP address is 1.23.64.0, and when the IP address range is: 1.23.75.0 to 1.23.79.255, the lower limit IP address is 1.23.75.0.

The conversion strategy for converting the upper limit IP address to the domain name may adopt the above-mentioned conversion strategy for converting the IP address into the target domain name, which will not be repeated here in order to save space.

In step 402, the reference domain name is stored in the DNS, and a zone file is obtained after the reference domain name in the DNS is signed by using the DNSSEC protocol.

Wherein, when the reference domain name is stored in the DNS, an original zone file will be generated, and after the original zone file in the DNS is signed by using the DNSSEC protocol, the zone file mentioned in the present disclosure can be obtained. The zone file mentioned in the present disclosure includes record sets of each reference domain name, and the record sets of each reference domain name are sorted according to a preset policy, that is, the record sets exist in sequence. In one example, the preset strategy may be an alphabetical order strategy or the like.

The DNS server can query the reference domain name corresponding to the target domain name from the zone file. Since the reference domain name is obtained by domain name conversion based on the upper limit IP address in the IP address range to which the IP address belongs, the upper limit IP address is only a part of all IP addresses. Therefore, the base domain names recorded in the zone file are only partial domain names, and the number of base domain names recorded in the zone file is less than the number of target domain names obtained by all IP addresses. In view of this, when there is a benchmark domain name matching the target domain name in the zone file, the matching benchmark domain name can be used as the benchmark domain name corresponding to the target domain name; if there is no benchmark domain name matching the target domain name in the zone file, you need to find The reference domain name associated with the target domain, and the associated reference domain name is used as the reference domain name corresponding to the target domain name, wherein the associated reference domain name identifies the IP address range to which the IP address corresponding to the target domain name belongs.

In an optional implementation manner, the record set of the reference domain name includes at least NESC (Next Secure) records, and the NSEC records are records designed in response to the absence of a certain record. The name of the base domain name of the next record set is recorded in the NESC record. Therefore, querying the reference domain name corresponding to the target domain name from the zone file includes:

Query the target domain name from the zone file, when the target domain name is between the first benchmark domain name and the second benchmark domain name, send the NESC record in the record set of the first benchmark domain name to the query server .

The name of the second benchmark domain name is recorded in the sent NESC record, the first benchmark domain name and the second benchmark domain name are adjacent benchmark domain names in the zone file, and the first benchmark domain name is arranged before the second benchmark domain name . The NESC record in the record set of the first reference domain name includes the name of the second reference domain name. The IP address range identified by the first reference domain name and the IP address range identified by the second reference domain name are adjacent IP address ranges, that is, the upper limit IP address of the IP address range arranged in the front, and the IP address range of the IP address range arranged in the rear. The lower limit IP address is continuous, and there is no interval IP address.

It can be seen from the above-mentioned embodiment that, because this embodiment can send the result containing the NESC record to the query server, and the NESC record records the benchmark domain name name of the next record set, the benchmark domain name corresponding to the target domain name is obtained, and then the benchmark domain name corresponding to the target domain name is obtained. It is inferred that the IP address of the user terminal is within the IP address range with the IP address corresponding to the second reference domain name (the reference domain name returned by the query server receiving the DNS server) as the upper limit IP address, so as to facilitate the subsequent determination of the attribution according to the IP address range .

The corresponding relationship between the reference domain name and the attribution is pre-stored in the query server. The corresponding relationship is determined according to the relationship between the reference domain name and the IP address range, and the corresponding relationship between the IP address range and the attribution. For example, the IP address range 1.23.64.0~1.23.74.255 corresponds to the region A, and the IP address range 1.23.75.0~1.23.79.255 corresponds to the region B. Therefore, the upper limit IP address in the IP address range (1.23. 74.255) The benchmark domain name 18303743.com obtained by domain name conversion, its corresponding IP address range is 1.23.64.0～1.23.74.255, and the IP address range 1.23.64.0～1.23.74.255 corresponds to the region A, then the benchmark domain name is 18303743 .com corresponds to region A. Similarly, the benchmark domain name 18305023.com (the converted domain name of 1.23.79.255) corresponds to region B. The correspondence stored in the query server can exist in the form of a mapping table.

Therefore, when the query result includes the name of the benchmark domain name of the next record set, the attribution corresponding to the benchmark domain name can be determined according to the name of the benchmark domain name and the corresponding relationship pre-stored in the query server, and the found attribution can be determined. The home of the IP address.

It can be understood that the record set may also include other types of records, for example, RRSIG, DNSKEY, DS, etc., which will not be listed one by one here.

Various technical features in the above embodiments can be combined arbitrarily, as long as there is no conflict or contradiction between the combinations of features, but due to space limitations, they are not described one by one, so the various technical features in the above embodiments can be combined arbitrarily It also belongs to the scope of the disclosure of this specification. The following is an example of an interactive embodiment.

As shown in FIG. 5 , FIG. 5 is an interactive schematic diagram of a method for querying IP address attribution according to an exemplary embodiment of the present disclosure. In this schematic diagram, the query server converts the IP address of the user terminal into the target domain name (step 501). The query server sends a query request carrying the target domain name to the DNS server, the query request instructs the DNS server to query the reference domain name corresponding to the target domain name, and the reference domain name is used to identify the IP address to which the IP address belongs. IP address range (step 502). The DNS server queries the reference domain name corresponding to the target domain name from the zone file (step 503). The zone file is obtained by using the DNSSEC protocol to sign the reference domain name in the DNS, and the reference domain name is obtained by domain name conversion based on the upper limit IP address in the IP address range to which the IP address belongs. The record sets of each reference domain name in the zone file are sorted according to a preset strategy, the record set includes at least NESC records, and the NESC records record the name of the reference domain name of the next record set. In one example, the querying the reference domain name corresponding to the target domain name from the zone file includes: if there is a reference domain name matching the target domain name in the zone file, taking the matched reference domain name as the target domain name corresponding to the target domain name Base domain name. In an example, the querying the reference domain name corresponding to the target domain name from the zone file includes: querying the target domain name from the zone file, when the target domain name is between the first reference domain name and the second reference domain name time, send the NESC record in the record set of the first benchmark domain name to the query server; wherein, the sent NESC record records the name of the second benchmark domain name, the first benchmark domain name and the second benchmark domain name The reference domain name is the adjacent reference domain name in the zone file, and the first reference domain name is arranged before the second reference domain name. The DNS server sends the reference domain name to the query server (step 504). The query server receives the reference domain name returned by the DNS server, searches for the attribution corresponding to the reference domain name based on the preset correspondence, and determines the found attribution as the attribution of the IP address, and the preset corresponding The relationship is the corresponding relationship between the pre-stored reference domain name and the attribution (step 505).

A specific application example is listed below for illustration.

The IP address range 1.23.64.0 to 1.23.74.255 and the IP address range 1.23.75.0 to 1.23.79.255 will be described. Convert the dotted decimal represented by the end of the segment (upper IP address) of each IP address range into the corresponding number and put it under a top-level domain as a first-level domain name. 18303743.com, then 1.23.79.255 storage becomes 18305023.com.

Use the DNSSEC protocol-based method to enter the reference domain name into the DNS. After completing the signature, a signed zone file in alphabetical order will be obtained. The DNS will load the zone file into the memory and provide it to the DNS server. Do a domain name lookup.

In the zone file after DNSSEC signature, these two records exist sequentially.

18303743.com.10800 IN A 1.23.74.255

172800 NSEC 18305023.com.A RRSIG NSEC

172800 RRSIG NSEC 5 5 172800 20160611031416 (201605120314165271com.Ujw/aq….15dV5tF7XgWSR78=)

18305023.com.10800 IN A 1.23.79.255

It can be seen that the base domain name 18305023.com of the next record set is recorded in the NSEC of 18303743.com.

When the query server receives the request carrying the IP address, it converts the IP address into the form of number + .com, obtains the domain name to be searched, and sends the domain name to the DNS server. Assuming that the IP address is 1.23.75.8, the actual record to be checked is 18303752.com, because this record does not exist in the DNS zone file, so the return record does not exist, and 18303743.com (that is, 18303752.com recently The NSEC record of the previous record) is returned, that is, the value of NSEC is 18305023.com.

Since the correspondence between the reference domain name and the attribution is recorded in the query server, it can be found that the attribution corresponding to 18305023.com is region B.

It can be seen that the IP data of the original area information is converted into the format of the domain name and entered into the DNS, and the DNSSEC signature is performed on the area file of the DNS. DNS is a basic Internet protocol, which is safe and reliable, and naturally supports distributed deployment. Through the cooperation of recursive servers and authoritative servers, the query speed can be accelerated, and there is no need to build a third-party architecture. DNS is a basic service with low cost.

Corresponding to the foregoing embodiments of the IP address attribution query method, the present disclosure also provides embodiments of an IP address attribution query apparatus, system, storage medium, and a server to which it is applied.

As shown in FIG. 6 , FIG. 6 is a block diagram of an IP address attribution query system according to an exemplary embodiment of the present disclosure. The system includes a query server 61 and a DNS server 62 .

The query server 61 converts the IP address of the user terminal into a target domain name, and sends a query request carrying the target domain name to the DNS server 62 .

The DNS server 62 queries the reference domain name corresponding to the target domain name based on the query request, and sends the reference domain name to the query server 61, where the reference domain name is used to identify the IP to which the IP address belongs. address range.

The query server 61 searches for the attribution corresponding to the reference domain name based on the preset correspondence, and determines the found attribution as the attribution of the IP address, and the preset correspondence is the pre-stored reference domain name and the reference domain name. Correspondence of attribution.

It can be seen from the above embodiment that the IP address of the user terminal is converted into the target domain name through the query server, and the target domain name is sent to the DNS server, and the DNS server queries the reference domain name corresponding to the target domain name based on the query request. In order to identify the IP address range to which the IP address belongs, after the DNS server sends the reference domain name to the query server, the query server can search for the attribution corresponding to the reference domain name based on the preset correspondence, so that the found The attribution is determined as the attribution of the IP address, so as to quickly query the attribution of the IP address.

In an optional implementation manner, the converting the IP address of the user terminal into the target domain name includes: converting the IP address into a number; and combining the number with a preset top-level domain to obtain the target domain name corresponding to the IP address.

In an optional implementation manner, the converting the IP address into a number includes:

Convert the decimal number to hexadecimal number of each byte in the IP address;

Combine the hexadecimal numbers obtained by converting each byte in the order of bytes in the IP address to obtain a hexadecimal number;

Convert the hexadecimal number obtained by the combination into a decimal number to obtain the number corresponding to the IP address.

In an optional implementation manner, the reference domain name is obtained by domain name conversion based on the upper limit IP address in the IP address range to which the IP address belongs.

In an optional implementation manner, the querying the reference domain name corresponding to the target domain name based on the query request includes: querying the reference domain name corresponding to the target domain name from a zone file, the zone file using The DNSSEC protocol is obtained by signing the reference domain name in the DNS, and the reference domain name is obtained by domain name conversion based on the upper limit IP address in the IP address range to which the IP address belongs.

In an optional implementation manner, the record sets of each reference domain name in the zone file are sorted according to a preset policy, the record set includes at least NESC records, and the NESC records record the benchmark of the next record set the name of the domain name;

The querying the reference domain name corresponding to the target domain name from the zone file includes: querying the target domain name from the zone file, when the target domain name is between the first reference domain name and the second reference domain name, querying the target domain name. sending the NESC record in the record set of the first reference domain name to the query server;

The name of the second benchmark domain name is recorded in the sent NESC record, the first benchmark domain name and the second benchmark domain name are adjacent benchmark domain names in the zone file, and the first benchmark domain name is arranged before the second benchmark domain name .

As shown in FIG. 7 , FIG. 7 is a block diagram of an IP address attribution query apparatus according to an exemplary embodiment of the present disclosure, the apparatus includes: an information conversion module 710 , an information communication module 720 and an attribution determination module 730 .

The information conversion module 710 is configured to convert the IP address of the user terminal into the target domain name.

The information communication module 720 is configured to send a query request carrying the target domain name to the DNS server, and receive the reference domain name returned by the DNS server; the query request instructs the DNS server to query the benchmark corresponding to the target domain name Domain name, the reference domain name is used to identify the IP address range to which the IP address belongs.

The attribution determination module 730 is configured to search for the attribution corresponding to the reference domain name based on a preset correspondence relationship, and determine the attribution found as the attribution of the IP address, and the preset correspondence is a pre-stored benchmark The correspondence between domain names and attributions.

In an optional implementation manner, the information conversion module 710 is specifically configured to: convert the IP address into a number; and combine the number with a preset top-level domain to obtain a target domain name corresponding to the IP address.

It can be seen from the above embodiment that the IP address is converted into a number, and the number is combined with the preset top-level domain to realize the conversion of the IP address of the user terminal into the target domain name, which not only improves the domain name conversion efficiency, but also improves the subsequent domain name lookup. Find efficiency.

In an optional implementation manner, the information conversion module 710 is specifically configured as:

Convert the decimal number to hexadecimal number of each byte in the IP address;

Combine the hexadecimal numbers obtained by converting each byte in the order of bytes in the IP address to obtain a hexadecimal number;

Convert the hexadecimal number obtained by the combination into a decimal number to obtain the number corresponding to the IP address. In an optional implementation manner, the reference domain name is obtained by domain name conversion based on the upper limit IP address in the IP address range to which the IP address belongs.

As shown in FIG. 8, FIG. 8 is a block diagram of another IP address attribution query apparatus shown in the present disclosure according to an exemplary embodiment, and the apparatus includes:

The information communication module 810 is configured to receive a query request sent by the query server, where the query request carries a target domain name corresponding to the IP address;

a domain name query module 820, configured to query a reference domain name corresponding to the target domain name based on the query request, where the reference domain name is used to identify the IP address range to which the IP address belongs;

The information communication module 810 is further configured to send the reference domain name to the query server, so that the query server searches for the attribution corresponding to the reference domain name based on the preset correspondence, and determines the found attribution. is the attribution of the IP address, and the preset correspondence is the correspondence between the pre-stored reference domain name and the attribution.

In an optional implementation manner, the domain name query module 820 is specifically configured as:

The reference domain name corresponding to the target domain name is queried from the zone file. The zone file is obtained by using the DNSSEC protocol to sign the reference domain name in the DNS. The reference domain name is based on the upper limit of the IP address range to which the IP address belongs. The IP address is obtained by domain name conversion.

As can be seen from the above embodiment, since the reference domain name is obtained by domain name conversion based on the upper limit IP address in the IP address range to which the IP address belongs, an IP address range can be determined according to the reference domain name, and the IP address range is the user. The IP address range to which the terminal's IP address belongs. It can be seen that, by querying the target domain name corresponding to the reference domain name, the IP address range to which the IP address belongs can be determined, thereby improving the query efficiency.

In an optional implementation manner, the record sets of each reference domain name in the zone file are sorted according to a preset policy, the record set includes at least NESC records, and the NESC records record the benchmark of the next record set The name of the domain name; the domain name query module 820 is specifically configured as:

Query the target domain name from the zone file, when the target domain name is between the first benchmark domain name and the second benchmark domain name, send the NESC record in the record set of the first benchmark domain name to the query server ;

The name of the second benchmark domain name is recorded in the sent NESC record, the first benchmark domain name and the second benchmark domain name are adjacent benchmark domain names in the zone file, and the first benchmark domain name is arranged before the second benchmark domain name .

It can be seen from the above embodiment that the DNS server queries the target domain name from the zone file, and when the target domain name is between the first benchmark domain name and the second benchmark domain name, returns the NESC record in the record set of the first benchmark domain name to the query service. On the other hand, since the first benchmark domain name and the second benchmark domain name are adjacent benchmark domain names in the zone file, and the first benchmark domain name is arranged before the second benchmark domain name, the NESC record in the record set of the first benchmark domain name includes the data of the second benchmark domain name. In order to query the server to obtain the reference domain name corresponding to the target domain name, it can be inferred that the IP address of the user terminal is within the IP address range with the IP address corresponding to the second reference domain name as the upper limit IP address, and then determine the user terminal’s IP address. The attribution of the IP address improves the efficiency of attribution query.

Correspondingly, the present disclosure also provides an IP address attribution query apparatus, the apparatus includes a processor; a memory for storing executable instructions of the processor; wherein the processor is configured to:

Convert the IP address of the user terminal to the target domain name;

Send a query request carrying the target domain name to the DNS server, where the query request instructs the DNS server to query the reference domain name corresponding to the target domain name, and the reference domain name is used to identify the IP address range to which the IP address belongs ;

Receive the base domain name returned by the DNS server;

Based on a preset correspondence relationship, the attribution corresponding to the reference domain name is searched, and the found attribution is determined as the attribution of the IP address, and the preset correspondence is a pre-stored correspondence between the reference domain name and the attribution.

Correspondingly, the present disclosure also provides an IP address attribution query apparatus, the apparatus includes a processor; a memory for storing executable instructions of the processor; wherein the processor is configured to:

receiving a query request sent by the query server, where the query request carries a target domain name corresponding to the IP address;

Query a reference domain name corresponding to the target domain name based on the query request, where the reference domain name is used to identify the IP address range to which the IP address belongs;

Send the reference domain name to the query server, so that the query server searches for the attribution corresponding to the reference domain name based on the preset correspondence, and determines the found attribution as the attribution of the IP address. The preset corresponding relationship is the corresponding relationship between the pre-stored reference domain name and the attribution.

For the specific details of the implementation process of the functions and functions of each module in the above device, see the implementation process of the corresponding steps in the above method, which will not be repeated here.

For the apparatus embodiments, since they basically correspond to the method embodiments, reference may be made to the partial descriptions of the method embodiments for related parts. The device embodiments described above are only illustrative, wherein the modules described as separate components may or may not be physically separated, and the components shown as modules may or may not be physical modules, that is, they may be located in One place, or it can be distributed over multiple network modules. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution of the present disclosure. Those of ordinary skill in the art can understand and implement it without creative effort.

Correspondingly, the present disclosure also provides a computer-readable storage medium on which a computer program is stored, and when the program is executed by a processor, implements the steps of any of the above-mentioned IP address attribution query methods applied in the query server. .

Correspondingly, the present disclosure also provides a computer-readable storage medium on which a computer program is stored, and when the program is executed by a processor, implements the steps of any of the above-mentioned IP address attribution query methods applied in the DNS server. .

The present disclosure may employ a computer program implemented on one or more storage media (including, but not limited to, magnetic disk storage, CD-ROM (Compact Disc Read-Only Memory), optical storage, etc.) having program codes contained therein form of the product. Computer-usable storage media includes permanent and non-permanent, removable and non-removable media, and storage of information can be accomplished by any method or technology. Information may be computer readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read only memory (ROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), Flash Memory or other memory technology, CD-ROM, Digital Versatile Disc (DVD) or other optical storage, Magnetic Cassettes, Magnetic Magnetic Disks Storage or other magnetic storage device or any other non-transmission medium that can be used to store information that can be accessed by a computing device.

As shown in FIG. 9, FIG. 9 is a block diagram of an apparatus 900 for IP address attribution query according to an exemplary embodiment.

For example, the apparatus 900 may be provided as a server device. 9, system 900 includes processing component 922, which further includes one or more processors, and a memory resource represented by memory 932 for storing instructions executable by processing component 922, such as application programs. An application program stored in memory 932 may include one or more modules, each corresponding to a set of instructions. In addition, the processing component 922 is configured to execute the instructions to execute the above IP address attribution query method.

System 900 may also include a power supply assembly 926 configured to perform power management of system 900, a wired or wireless network interface 950 configured to connect system 900 to a network, and an input output (I/O) interface 958. System 900 may operate based on an operating system stored in memory 932 .

Wherein, when the instructions in the memory 932 are executed by the processing component 922, the system 900 is enabled to execute a method for querying IP address attribution, including:

Convert the IP address of the user terminal to the target domain name.

Send a query request carrying the target domain name to the DNS server, where the query request instructs the DNS server to query the reference domain name corresponding to the target domain name, and the reference domain name is used to identify the IP address range to which the IP address belongs .

Receive the base domain name returned by the DNS server.

Based on a preset correspondence relationship, the attribution corresponding to the reference domain name is searched, and the found attribution is determined as the attribution of the IP address, and the preset correspondence is a pre-stored correspondence between the reference domain name and the attribution.

As shown in FIG. 10 , FIG. 10 is a block diagram of another apparatus 1000 for IP address attribution query according to an exemplary embodiment.

For example, the apparatus 1000 may be provided as a server device. 10, the system 1000 includes a processing component 1022, which further includes one or more processors, and a memory resource, represented by memory 1032, for storing instructions executable by the processing component 1022, such as an application program. An application program stored in memory 1032 may include one or more modules, each corresponding to a set of instructions. In addition, the processing component 1022 is configured to execute the instructions to execute the above-mentioned IP address attribution query method.

System 1000 may also include a power supply assembly 1026 configured to perform power management of system 1000, a wired or wireless network interface 1050 configured to connect system 1000 to a network, and an input output (I/O) interface 1058. System 1000 may operate based on an operating system stored in memory 1032 .

Wherein, when the instructions in the memory 1032 are executed by the processing component 1022, the system 1000 is enabled to execute a method for querying IP address attribution, including:

A query request sent by the query server is received, where the query request carries a target domain name corresponding to the IP address.

The reference domain name corresponding to the target domain name is queried based on the query request, where the reference domain name is used to identify the IP address range to which the IP address belongs.

Send the reference domain name to the query server, so that the query server searches for the attribution corresponding to the reference domain name based on the preset correspondence, and determines the found attribution as the attribution of the IP address. The preset corresponding relationship is the corresponding relationship between the pre-stored reference domain name and the attribution.

Other embodiments of the present disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common general knowledge or techniques in the technical field not disclosed by this disclosure . The specification and examples are to be regarded as exemplary only, with the true scope and spirit of the disclosure being indicated by the following claims.

It is to be understood that the present disclosure is not limited to the precise structures described above and illustrated in the accompanying drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

The above descriptions are only preferred embodiments of the present disclosure, and are not intended to limit the present disclosure. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present disclosure shall be included in the present disclosure. within the scope of protection.

Claims (17)

1. An IP address home location query method is applied to a query server side, and comprises the following steps:

converting the IP address of the user terminal into a target domain name;

sending a query request carrying the target domain name to a Domain Name System (DNS) server, wherein the query request indicates the DNS server to query a reference domain name corresponding to the target domain name, and the reference domain name is used for identifying an IP address range to which the IP address belongs;

receiving a reference domain name returned by the DNS server;

and searching the attribution corresponding to the reference domain name based on a preset corresponding relation, and determining the searched attribution as the attribution of the IP address, wherein the preset corresponding relation is the prestored corresponding relation between the reference domain name and the attribution.

2. The method of claim 1, wherein the converting the IP address of the user terminal to the target domain name comprises:

converting the IP address into a number;

and combining the number with a preset top level domain to obtain a target domain name corresponding to the IP address.

3. The method of claim 2, wherein converting the IP address to a number comprises:

converting the decimal number of each byte in the IP address into a hexadecimal number;

combining the hexadecimal numbers obtained by converting each byte according to the byte sequence in the IP address to obtain a hexadecimal number;

and converting the hexadecimal number obtained by combination into a decimal number to obtain a number corresponding to the IP address.

4. The method according to any one of claims 1 to 3, wherein the reference domain name is obtained by performing domain name conversion based on an upper-limit IP address in an IP address range to which the IP address belongs.

5. An IP address home inquiring method is applied to a DNS server, and the method comprises the following steps:

receiving a query request sent by a query server, wherein the query request carries a target domain name corresponding to an IP address;

querying a reference domain name corresponding to the target domain name based on the query request, wherein the reference domain name is used for identifying an IP address range to which the IP address belongs;

and sending the reference domain name to the query server, so that the query server searches for an attribution corresponding to the reference domain name based on a preset corresponding relationship, and determines the found attribution as the attribution of the IP address, wherein the preset corresponding relationship is a pre-stored corresponding relationship between the reference domain name and the attribution.

6. The method of claim 5, wherein querying the reference domain name corresponding to the target domain name based on the query request comprises:

and querying a reference domain name corresponding to the target domain name from a zone file, wherein the zone file is obtained by signing the reference domain name in the DNS by using a domain name system security extension protocol, and the reference domain name is obtained by performing domain name conversion on an upper limit IP address in an IP address range to which the IP address belongs.

7. The method according to claim 6, wherein the record sets of the reference domain names in the zone file are sorted according to a preset policy, and the record sets at least include a next security record, and the next security record records the name of the reference domain name of the next record set;

the querying a reference domain name corresponding to the target domain name from the slave zone file includes:

inquiring the target domain name from the zone file, and when the target domain name is between a first reference domain name and a second reference domain name, sending the next safety record in the record set of the first reference domain name to the inquiry server;

and the name of a second reference domain name is recorded in the next sent safety record, the first reference domain name and the second reference domain name are adjacent reference domain names in the zone file, and the first reference domain name is arranged in front of the second reference domain name.

8. An IP address home querying device, the device comprising:

an information conversion module configured to convert an IP address of a user terminal into a target domain name;

the information communication module is configured to send a query request carrying the target domain name to the DNS server and receive a reference domain name returned by the DNS server; the query request indicates a DNS server to query a reference domain name corresponding to the target domain name, wherein the reference domain name is used for identifying an IP address range to which the IP address belongs;

and the attribution determining module is configured to search an attribution corresponding to the reference domain name based on a preset corresponding relation, and determine the searched attribution as the attribution of the IP address, wherein the preset corresponding relation is a pre-stored corresponding relation between the reference domain name and the attribution.

9. The apparatus of claim 8, wherein the information transformation module is specifically configured to:

converting the IP address into a number;

and combining the number with a preset top level domain to obtain a target domain name corresponding to the IP address.

10. An IP address home querying device, the device comprising:

the information communication module is configured to receive a query request sent by a query server, wherein the query request carries a target domain name corresponding to the IP address;

a domain name query module configured to query a reference domain name corresponding to the target domain name based on the query request, where the reference domain name is used to identify an IP address range to which the IP address belongs;

the information communication module is further configured to send the reference domain name to the query server, so that the query server searches for an attribution corresponding to the reference domain name based on a preset corresponding relationship, and determines the found attribution as the attribution of the IP address, where the preset corresponding relationship is a pre-stored corresponding relationship between the reference domain name and the attribution.

11. The apparatus according to claim 10, wherein the domain name querying module is specifically configured to:

and querying a reference domain name corresponding to the target domain name from a zone file, wherein the zone file is obtained by signing the reference domain name in the DNS by using a domain name system security extension protocol, and the reference domain name is obtained by performing domain name conversion on an upper limit IP address in an IP address range to which the IP address belongs.

12. The apparatus according to claim 11, wherein the record set of each reference domain name in the zone file is sorted according to a preset policy, and the record set at least includes a next security record, and the next security record records a name of the reference domain name of the next record set;

the domain name query module is specifically configured to:

inquiring the target domain name from the zone file, and when the target domain name is between a first reference domain name and a second reference domain name, sending the next safety record in the record set of the first reference domain name to the inquiry server;

and the name of a second reference domain name is recorded in the next sent safety record, the first reference domain name and the second reference domain name are adjacent reference domain names in the zone file, and the first reference domain name is arranged in front of the second reference domain name.

13. An IP address home inquiry system is characterized in that the system comprises an inquiry server and a DNS server,

the query server converts the IP address of the user terminal into a target domain name, and sends a query request carrying the target domain name to the DNS server;

the DNS server queries a reference domain name corresponding to the target domain name based on the query request, and sends the reference domain name to the query server, wherein the reference domain name is used for identifying an IP address range to which the IP address belongs;

and the query server searches for the home location corresponding to the reference domain name based on a preset corresponding relationship, and determines the found home location as the home location of the IP address, wherein the preset corresponding relationship is the pre-stored corresponding relationship between the reference domain name and the home location.

14. An IP address home location inquiring apparatus, comprising:

a processor;

a memory for storing processor-executable instructions;

wherein the processor is configured to:

converting the IP address of the user terminal into a target domain name;

sending a query request carrying the target domain name to a DNS server, wherein the query request indicates the DNS server to query a reference domain name corresponding to the target domain name, and the reference domain name is used for identifying an IP address range to which the IP address belongs;

receiving a reference domain name returned by a DNS server;

and searching the attribution corresponding to the reference domain name based on a preset corresponding relation, and determining the searched attribution as the attribution of the IP address, wherein the preset corresponding relation is the prestored corresponding relation between the reference domain name and the attribution.

15. An IP address home location inquiring apparatus, comprising:

a processor;

a memory for storing processor-executable instructions;

wherein the processor is configured to:

receiving a query request sent by a query server, wherein the query request carries a target domain name corresponding to an IP address;

querying a reference domain name corresponding to the target domain name based on the query request, wherein the reference domain name is used for identifying an IP address range to which the IP address belongs;

and sending the reference domain name to the query server, so that the query server searches for an attribution corresponding to the reference domain name based on a preset corresponding relationship, and determining the found attribution as the attribution of the IP address, wherein the preset corresponding relationship is a pre-stored corresponding relationship between the reference domain name and the attribution.

16. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of the method according to any one of claims 1 to 4.

17. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of the method of any one of claims 5 to 7.

Images