CN101902442A - Method, system and position information server for acquiring IP geographic position information - Google Patents
Method, system and position information server for acquiring IP geographic position information Download PDFInfo
- Publication number
- CN101902442A CN101902442A CN2009100853272A CN200910085327A CN101902442A CN 101902442 A CN101902442 A CN 101902442A CN 2009100853272 A CN2009100853272 A CN 2009100853272A CN 200910085327 A CN200910085327 A CN 200910085327A CN 101902442 A CN101902442 A CN 101902442A
- Authority
- CN
- China
- Prior art keywords
- dns
- server
- information
- domain name
- authoritative server
- Prior art date
- Legal status (The legal status 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 status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 37
- 238000004806 packaging method and process Methods 0.000 claims abstract description 16
- 230000003993 interaction Effects 0.000 claims description 38
- 230000004044 response Effects 0.000 claims description 19
- 238000006243 chemical reaction Methods 0.000 claims description 14
- 238000005538 encapsulation Methods 0.000 claims description 6
- 238000000605 extraction Methods 0.000 claims description 3
- 101100509103 Schizosaccharomyces pombe (strain 972 / ATCC 24843) ish1 gene Proteins 0.000 description 19
- 238000013507 mapping Methods 0.000 description 13
- 101150045440 ISP1 gene Proteins 0.000 description 5
- 101100353471 Mus musculus Prss28 gene Proteins 0.000 description 5
- 238000010586 diagram Methods 0.000 description 5
- 238000012423 maintenance Methods 0.000 description 5
- 230000008901 benefit Effects 0.000 description 3
- 230000007246 mechanism Effects 0.000 description 3
- 230000008569 process Effects 0.000 description 2
- 238000013519 translation Methods 0.000 description 2
- 101000610620 Homo sapiens Putative serine protease 29 Proteins 0.000 description 1
- 102100040345 Putative serine protease 29 Human genes 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 239000000284 extract Substances 0.000 description 1
- 239000012634 fragment Substances 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
Images
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention provides a method for acquiring IP geographic position information, which comprises the following steps: receiving an IP geographic position inquiry request initiated by an application program, wherein the request comprises an IP address; converting the IP address into a fully qualified domain name, and packaging the fully qualified domain name into a corresponding first DNS inquiry request; positioning an object-level DNS authoritative server according to the first DNS inquiry request; redirecting the fully qualified domain name by the object-level DNS authoritative server to acquire the information of the DNS authoritative server to which the mapped ISP belongs; packaging the redirected fully qualified domain name into a corresponding second DNS inquiry request, sending the second DNS inquiry request to the DNS authoritative server to which the ISP belongs, and returning corresponding geographic position information in a TXT format by the DNS authoritative server to which the ISP belongs according to the private policy; and converting the geographic position information into the information in an XML format to be returned to the application program. The invention can ensure the accuracy of the acquired geographic position information.
Description
Technical Field
The invention relates to the field of digital network communication, in particular to a method for acquiring IP geographical position information, a system for acquiring the IP geographical position information and a position information server.
Background
With the development of computer networks, more and more devices have independent IP addresses, and if the devices can be geographically located according to the IP addresses, more colorful and location-based application services can be provided for users.
Attempts have been made as early as 1985 to associate IP addresses with their corresponding geographic locations, wherein a more influential way is to collect geographic location information for the IP from various web sites and to associate the IP with the geographic location information for storage in a centralized server. Because the number of IP addresses worldwide is very large, it is very difficult to maintain a centralized database of such large sizes. Another difficulty is the lack of efficient tools to check the validity of addresses in a database, resulting in a large amount of erroneous data being stored in the database.
For example, many Internet service providers provide location information services based on IP addresses, but the location information provided by these services is generally relatively rough, such as being located only in countries or provinces or cities or counties, and not meeting the fine and accurate requirements of special services at all; or, many hardware device providers provide location services based on Dynamic Host Configuration Protocol (DHCP) and Link Layer Discovery Protocol (LLDP), and these methods require a network administrator to manually configure location information corresponding to each port into a location server of a local area network, and can only be used within a local area network administrative domain. Considering that a large number of local area networks use technologies such as Network Address Translation (NAT), Virtual Private Network (VPN), and firewall, the location information provided by the static configuration is not the real location information of the user/device.
Therefore, one technical problem that needs to be urgently solved by those skilled in the art is: how to creatively provide a method for acquiring IP geographical location information to ensure the accuracy of the geographical location information.
Disclosure of Invention
The technical problem to be solved by the invention is to provide a method for acquiring IP geographical position information, which is used for ensuring the accuracy of the geographical position information.
The invention also provides a system for acquiring the IP geographical position information and a position information server, which are used for ensuring the realization and the application of the method in practice.
In order to solve the above problem, the present invention discloses a method for obtaining IP geographical location information, where the geographical location information is stored in a DNS authoritative server to which an ISP belongs, the method including:
receiving an IP geographical position query request initiated by an application program, wherein the IP geographical position query request comprises an IP address;
converting the IP address into a fully-qualified domain name, and encapsulating the fully-qualified domain name into a corresponding first DNS query request;
according to the first DNS query request, positioning a target level DNS authoritative server in all levels of DNS authoritative servers; redirecting the fully qualified domain name by the target level DNS authoritative server to obtain the information of the DNS authoritative server to which the mapped ISP belongs;
packaging the redirected fully-qualified domain name into a corresponding second DNS query request, sending the second DNS query request to the DNS authoritative server to which the ISP belongs, and returning the TXT-format geographic position information corresponding to the redirected fully-qualified domain name by the DNS authoritative server to which the ISP belongs according to a private strategy;
and converting the geographical position information into information in an XML format, and returning the information to the application program.
Preferably, the full-name domain includes top-level domain name information and sub-level domain name information, the DNS authoritative servers at each level include a root DNS authoritative server, a top-level DNS authoritative server, and a sub-level DNS authoritative server, and the positioning step of the target-level DNS authoritative server includes:
sending the first DNS query request to a root DNS authoritative server, and returning top-level DNS authoritative server information pointed by the top-level domain name information by the root DNS authoritative server;
sending the first DNS query request to the top-level DNS authoritative server, and returning the information of the sub-level DNS authoritative server pointed by the sub-level domain name information by the top-level DNS authoritative server;
and sending the first DNS inquiry request to the subordinate DNS authoritative server.
Preferably, the method further comprises:
and recording the corresponding relation between the domain name information in the fully-qualified domain name and the target level DNS authoritative server to the local DNS server.
Preferably, the step of locating the target-level DNS authoritative server further comprises:
sending the first DNS query request to a local DNS server;
the local DNS server judges whether a corresponding relation record of the domain name information of the full-name domain name and a target level DNS authoritative server exists, if so, the information of the target level DNS authoritative server is directly returned;
and sending the first DNS inquiry request to the target-level DNS authoritative server.
Preferably, the step of returning the IP geographical location information includes:
if the DNS authoritative server to which the ISP belongs determines to return the geographical location information corresponding to the redirected fully-qualified domain name according to a private policy, packaging the geographical location information into a DNS response data packet and returning the DNS response data packet;
the method further comprises the following steps:
extracting the geographical location information in the TXT format from the DNS response packet.
Preferably, the target-level DNS authority server redirection operation is a domain name redirection DNAME operation conforming to RFC2672 protocol; the XML format is an XML format conforming to RFC5193 protocol.
The embodiment of the invention also discloses a system for acquiring the IP geographical position information, which comprises the following steps: the method comprises the following steps that an application program server, a location information server, a target level DNS authoritative server and a DNS authoritative server to which an ISP belongs: wherein,
the application program server is used for sending an IP geographical position query request and receiving geographical position information in an XML format returned corresponding to the request;
the target level DNS authoritative server is positioned in each level of DNS authoritative servers and is used for redirecting the fully qualified domain name to obtain the information of the DNS authoritative server to which the mapped ISP belongs;
the DNS authoritative server to which the ISP belongs is used for returning the geographical position information in the TXT format corresponding to the redirection full-name domain name based on a private strategy according to the second DNS query request;
the position information server comprises the following modules:
a geographic location query request receiving module, configured to receive the IP geographic location query request, where the query request includes an IP address;
the IP address conversion module is used for converting the IP address into a full-name domain name;
a DNS query request encapsulation module used for encapsulating the fully qualified domain name into a corresponding first DNS query request; and encapsulating the redirected fully-qualified domain name into a corresponding second DNS query request;
the target level DNS interaction module is used for positioning a target level DNS authoritative server in each level of DNS authoritative servers according to the first DNS query request;
the DNS interaction module to which the ISP belongs is used for sending the second DNS query request to the DNS authoritative server to which the ISP belongs and receiving the geographical position information in the TXT format returned by corresponding to the request;
the geographic position format conversion module is used for converting the geographic position information in the TXT format into information in an XML format;
and the return module is used for returning the geographic position information in the XML format to the application program server.
Preferably, the full-name domain includes top-level domain name information and sub-domain name information, and the DNS authority servers of each level include a root DNS authority server, a top-level DNS authority server, and a sub-level DNS authority server; the root DNS authoritative server is used for returning top level DNS authoritative server information pointed by the top level domain name information according to the first DNS query request; the top level DNS authoritative server is used for returning the information of the sub-level DNS authoritative server pointed by the sub-domain name information according to the first DNS query request;
the target level DNS interaction module of the location information server comprises:
the root domain name server interaction submodule is used for sending the first DNS query request to a root DNS authoritative server and receiving top-level DNS authoritative server information returned by the root DNS authoritative server;
the top-level domain name server interaction submodule is used for sending the first DNS query request to the top-level DNS authoritative server and receiving information of the sub-level DNS authoritative server returned by the top-level DNS authoritative server;
and the subordinate domain name server interaction submodule is used for sending the first DNS query request to the subordinate DNS authoritative server.
Preferably, the system further includes a local DNS server, including:
and the recording module is used for recording the corresponding relation between the domain name information in the fully-qualified domain name and the target level DNS authoritative server.
Preferably, the target-level DNS interaction module of the location information server further includes:
the local domain name server interaction submodule is used for sending the first DNS query request to a local DNS server; receiving target level DNS authoritative server information returned by the local DNS;
a target level server interaction submodule, configured to send the first DNS query request to the target level DNS authoritative server;
the local DNS server further comprises:
the record searching module is used for judging whether a local DNS server has a corresponding relation record between the domain name information of the full-name domain name and a target level DNS authoritative server according to the first DNS query request, and if so, directly returning the information of the target level DNS authoritative server;
preferably, the DNS authoritative server to which the ISP belongs includes:
the packaging response module is used for packaging the geographical position information into a DNS response data packet and returning the geographical position information when the DNS authoritative server to which the ISP belongs determines to return the geographical position information corresponding to the redirection full-name domain name according to a private strategy;
the location information server further includes:
and the geographic position information extraction module is used for extracting the geographic position information in the TXT format from the DNS response data packet.
The embodiment of the invention also discloses a position information server, which is used for receiving the IP geographical position query request initiated by the application program server, wherein the query request comprises an IP address; and returning the geographic position information in an XML format to the application program server through interaction with the target level DNS authoritative server and the DNS authoritative server to which the ISP belongs; the target level DNS authoritative server is positioned in each level of DNS authoritative servers and is used for redirecting the fully qualified domain name to obtain the information of the DNS authoritative server to which the mapped ISP belongs; the DNS authoritative server to which the ISP belongs is used for returning the geographical position information in the TXT format corresponding to the redirection full-name domain name based on a private strategy according to the second DNS query request;
the location information server specifically includes the following modules:
a geographic location query request receiving module, configured to receive the IP geographic location query request, where the query request includes an IP address;
the IP address conversion module is used for converting the IP address into a full-name domain name;
a DNS query request encapsulation module used for encapsulating the fully qualified domain name into a corresponding first DNS query request; and encapsulating the redirected fully-qualified domain name into a corresponding second DNS query request;
the target level DNS interaction module is used for positioning a target level DNS authoritative server in each level of DNS authoritative servers according to the first DNS query request;
the DNS interaction module to which the ISP belongs is used for sending the second DNS query request to the DNS authoritative server to which the ISP belongs and receiving the geographical position information in the TXT format returned by corresponding to the request;
the geographic position format conversion module is used for converting the geographic position information in the TXT format into information in an XML format;
and the return module is used for returning the geographic position information in the XML format to the application program server.
Compared with the prior art, the invention has the following advantages:
the invention completes the collection and maintenance of the geographical location information by adopting the ISP responsible for distributing the IP address; the mapping of the IP address to the ISP and the mapping of the IP address to the geographical location information is done through the DNS system of the Internet. Specifically, the maintenance work of the IP geographical location information is distributed to each ISP by using a tree hierarchy of the DNS resolution system, that is, the IP address is mapped to the ISP responsible for allocating the IP address, and the mapping from the IP address to the geographical location information can be realized by accessing the DNS authoritative server to which the ISP belongs. In this case, since the ISP maintains the most accurate correspondence between the IP address and the geographical location information, the accuracy of the obtained IP geographical location information can be ensured; in addition, in the specific implementation, the ISP only needs to submit the IP geographical position information maintained by the ISP to the DNS authoritative server to which the ISP belongs, and the distribution information of the IP address does not need to be disclosed, so that the benefit of the ISP is guaranteed.
Drawings
Fig. 1 is a flowchart of an embodiment 1 of a method for acquiring IP geographical location information according to the present invention;
FIG. 2 is a schematic diagram of a DNS namespaces tree structure;
fig. 3 is a flowchart of embodiment 2 of a method for obtaining IP geographical location information according to the present invention;
FIG. 4 is a block diagram of one embodiment of a system for obtaining IP geolocation information of the present invention;
fig. 5 is a block diagram of an embodiment of a location information server of the present invention.
Detailed Description
In order to make the aforementioned objects, features and advantages of the present invention comprehensible, embodiments accompanied with figures are described in further detail below.
As can be derived by analyzing the prior art, the use of IP addresses to obtain geographical location information involves two key problems, one being that the collection and maintenance of geographical locations must be distributed and not centralized. Another problem is that the acquisition of geographical location information must be open, global, and not statically configured, local.
In view of the above problems, the present inventor has creatively proposed one of the core concepts of the present invention, that is, the collection and maintenance of the geographical location information is done by the ISP responsible for allocating the IP address; the mapping of IP addresses to ISPs and IP addresses to geographical location information is done based on the Internet's DNS system. Specifically, the maintenance work of the IP geographical location information is distributed to each ISP by utilizing a tree-shaped hierarchical structure of a DNS analysis system, namely, an IP address is mapped to the ISP responsible for distributing the IP address; the mapping of the IP address to the geographic position information can be realized by accessing the DNS authoritative server to which the ISP belongs.
Referring to fig. 1, a flowchart of an embodiment 1 of a method for acquiring IP geographical location information according to the present invention is shown, where the geographical location information is stored in a DNS authoritative server to which an ISP belongs; the embodiment may specifically include the following steps:
103, positioning a target level DNS authoritative server in all levels of DNS authoritative servers according to the first DNS query request;
105, packaging the redirected fully-qualified domain name into a corresponding second DNS query request, and sending the second DNS query request to a DNS authoritative server to which the ISP belongs;
and step 107, converting the geographical position information into information in an XML format, and returning the information to the application program.
In a specific implementation, the IP geolocation query request may be sent by an application program through an HTTP protocol, and in order to construct the first DNS query request, an IP address in the IP geolocation query request needs to be converted into a Fully Qualified Domain Name (FQDN). A fully qualified domain name is a uniform, worldwide addressable URI that may include a host name and various levels of domain name information, and it is known that constructing a fully qualified domain name may be accomplished by reversing an IP address, followed by an associated domain name suffix, such as IP address: 218.241.111.22 into FQDN can be 22.111.241.218. loc.cn. A fully qualified domain name may logically indicate exactly where the host is, or it may be said that a fully qualified domain name is a complete representation of a host name. The location of the host in the domain name tree can be seen from the information contained in the fully qualified domain name.
In a preferred embodiment of the present invention, the fully qualified domain name may include top level domain name information and sub-level domain name information, and the respective levels of DNS authoritative servers may include a root DNS authoritative server, a top level DNS authoritative server, and a sub-level DNS authoritative server, in which case, the step 103 may include the following sub-steps:
substep a1, sending the first DNS query request to a root DNS authoritative server, and returning, by the root DNS authoritative server, top DNS authoritative server information to which the top domain name information points;
substep a2, sending the first DNS query request to the top-level DNS authoritative server, and returning, by the top-level DNS authoritative server, the information of the sub-level DNS authoritative server to which the sub-level domain name information points;
sub-step A3, sending the first DNS query request to the sub-level DNS authoritative server.
For example, assume that the IP address received in the IP geolocation query request is "58.61.200.1," which is converted to FQDN as: 1.200.61.58.loc.cn, and encapsulating the FQDN into a corresponding first DNS query request, referring to the DNS domain name space tree structure shown in fig. 2, first sending the first DNS query request to a root DNS authoritative server; the root DNS authoritative server resolves the domain name information of the FQDN into loc.cn, and returns the record address of the top level DNS authoritative server to which the FQDN belongs (in this example, CN. top level domain name node shown in 201);
then sending the first DNS query request to the top level DNS authoritative server (CN. domain name resolution authoritative server); the top-level DNS authoritative server returns the record address of the second-level DNS authoritative server (in this example, the loc.cn. second-level domain name node shown as 202); in this example, the secondary DNS authoritative server is a target-level DNS authoritative server;
then sending the first DNS query request to the secondary DNS authoritative server (loc.cn domain name resolution authoritative server); and the secondary DNS authoritative server acquires the information of the DNS authority server to which the ISP belongs.
The embodiment shows the process of positioning the target-level DNS authoritative server by adopting a DNS step-by-step resolution mode, and by adopting the mode, when the address of the DNS authoritative server is changed, the DNS authoritative server can be updated in time, so that the positioning accuracy of the target-level DNS authoritative server can be ensured.
As another preferred embodiment, the present invention may further include the steps of:
and recording the corresponding relation between the domain name information in the fully-qualified domain name and the target level DNS authoritative server to the local DNS server.
In this case, the step 103 may further include the following sub-steps:
substep B1, sending the first DNS query request to a local DNS server;
in the substep B2, the local DNS server determines whether there is a correspondence record between the domain name information of the fully qualified domain name and the target-level DNS authoritative server, and if so, directly returns the information of the target-level DNS authoritative server;
sub-step B3, sending the first DNS query request to the target-level DNS authoritative server.
More preferably, if it is determined in the local DNS server that the correspondence record between the domain name information and the target-level DNS authoritative server does not exist, the target-level DNS authoritative server may be relocated in each level of DNS authoritative servers, for example, the above sub-step a1-A3 is performed.
The caching feature of the local DNS server provides a method of speeding up performance for subsequent queries of fully qualified domain names while greatly reducing DNS-related query traffic on the network. In practice, in order to ensure the validity of the correspondence between the domain name information and the target level DNS authoritative server in the cache region, when the cache information is reported, it is noted that the mapping is "non-authoritative" mapping, and address information of the DNS server that obtains the correspondence is given.
Of course, the above-mentioned location target level DNS authoritative server is only used as an example, and any manner is feasible for those skilled in the art according to the needs, for example, a DNS recursive resolution manner, which is not limited by the present invention.
In practice, an Internet Service Provider (ISP) is responsible for maintaining the correspondence between the IP address of the IP device and the geographic location information, and therefore, if the most accurate IP geographic location information is to be obtained, the information of the DNS authoritative server to which the ISP belongs needs to be obtained. In the embodiment of the invention, the mapping of the IP address to the DNS authoritative server belonging to the ISP is realized by the target-level DNS authoritative server, and particularly, the target-level DNS authoritative server can realize the mapping of the full-name domain name to the information of the DNS authoritative server belonging to the ISP by adopting the DNAME operation conforming to the RFC2672 protocol.
The DNAME defined in RFC2672 whose resource records are capable of mapping one sub-domain name space in its entirety to another domain space, the DNAME records create aliases for only a single node, and a single DNAME resource record will result in renaming the root and all descendants in the domain name space sub-tree, which enables an organization to rename its partial domain name space. For example, a zone file of a target level DNS authoritative server has the following configuration:
200.61.58.loc.cn.DNAME 200.61.58.isp1.loc.cn.
200.61.58.loc.cn. A 192.0.2.23
then an a record of 200.61.58.isp1.loc.cn. is queried which returns 192.0.2.23.
Namely, the target level DNS authoritative server can distinguish the information of the ISP to which the IP address belongs by using a DNAME mechanism.
In the embodiment of the present invention, preferably, the step 106 may include the following sub-steps:
substep C1, the DNS authoritative server to which the ISP belongs judges whether to return the geographical position information corresponding to the redirected fully-named domain name or not according to a private policy, if so, executing substep C2; otherwise, the geographical position information is not returned;
and a sub-step C2 of packaging the geographic position information into a DNS response data packet and returning.
In this case, the embodiment of the present invention may further include the following sub-steps:
extracting the geographical location information in the TXT format from the DNS response packet.
In practice, the ISP will decide whether to return the geographical location information according to the respective private policy and may decide how accurately to return the location information. For example, the returned geographical location information is located to a city, county, or to a street or cell.
In order to facilitate an application program to directly edit the geographical location information in the XML format by using a common text editor, the invention needs to convert the geographical location information into information in the XML format, preferably, the XML format may be an XML format conforming to RFC5193 protocol, and then the geographical location information in the XML format is returned to the corresponding application program through an http protocol.
Referring to fig. 3, a flowchart of embodiment 2 of a method for obtaining IP geographical location information according to the present invention is shown, where the geographical location information is stored in a DNS authoritative server to which an ISP belongs; the embodiment may specifically include the following steps:
While, for purposes of simplicity of explanation, the foregoing method embodiments have been described as a series of acts or combination of acts, it will be appreciated by those skilled in the art that the present invention is not limited by the illustrated ordering of acts, as some steps may occur in other orders or concurrently with other steps in accordance with the invention. Further, those skilled in the art should also appreciate that the embodiments described in the specification are preferred embodiments and that the acts and modules referred to are not necessarily required by the invention.
Referring to fig. 4, a structure diagram of an embodiment of the system for acquiring IP geographic location information according to the present invention is shown, and specifically, the system may include an application server 401, a location information server 402, a target-level DNS authoritative server 403, and a DNS authoritative server 404 to which an ISP belongs: wherein,
the application server 401 is configured to send an IP geographic location query request and receive geographic location information in an XML format returned in response to the request;
the location information server 402 may include the following modules:
a geographic location query request receiving module 4021, configured to receive the IP geographic location query request, where the query request includes an IP address;
the IP address conversion module 4022 is configured to convert the IP address into a fully-qualified domain name;
a DNS query request encapsulating module 4023, configured to encapsulate the fully qualified domain name into a corresponding first DNS query request; and encapsulating the redirected fully-qualified domain name into a corresponding second DNS query request;
a target level DNS interaction module 4024, configured to locate a target level DNS authoritative server in each level of DNS authoritative servers according to the first DNS query request;
the DNS interacting module 4025 to which the ISP belongs is configured to send the second DNS query request to the DNS authoritative server to which the ISP belongs, and receive the geographic location information in the TXT format returned by the request;
a geographic location format conversion module 4026, configured to convert the TXT format geographic location information into XML format information;
a returning module 4027, configured to return the geographic location information in the XML format to the application server;
the target level DNS authoritative server 403 is located in each level DNS authoritative server, and is configured to redirect the fully qualified domain name to obtain information of the DNS authoritative server 404 to which the mapped ISP belongs;
the DNS authoritative server 404 to which the ISP belongs is configured to return the geographical location information in the TXT format corresponding to the redirected fully qualified domain name based on a private policy according to the second DNS query request.
In practice, the information of the location information server 402 is completely disclosed to the outside, all application servers can directly access the location information server 402 to obtain the geographical location information, and the location information server 402 is responsible for inquiring the geographical location information of the device corresponding to the IP address from different ISPs, so that the mapping details from the IP address to the geographical location information are shielded. The method for the application program server to acquire the geographical location information is transparent, the application program server only needs to send an HTTP request and transmit the IP address of the equipment needing to inquire the geographical location information, the geographical location information in the XML format of the equipment can be received, and the XML message conforms to the standard regulation of RFC5139, so that the application program analysis is facilitated.
In a preferred embodiment of the present invention, the fully qualified domain name may include top level domain name information and sub-domain name information, and the DNS authority servers at each level may include a root DNS authority server, a top level DNS authority server, and a sub-level DNS authority server; the root DNS authoritative server is used for returning top level DNS authoritative server information pointed by the top level domain name information according to the first DNS query request; the top level DNS authoritative server is used for returning the information of the sub-level DNS authoritative server pointed by the sub-domain name information according to the first DNS query request;
the target level DNS interaction module of the location information server may include the following sub-modules:
the root domain name server interaction submodule is used for sending the first DNS query request to a root DNS authoritative server and receiving top-level DNS authoritative server information returned by the root DNS authoritative server;
the top-level domain name server interaction submodule is used for sending the first DNS query request to the top-level DNS authoritative server and receiving information of the sub-level DNS authoritative server returned by the top-level DNS authoritative server;
and the subordinate domain name server interaction submodule is used for sending the first DNS query request to the subordinate DNS authoritative server.
In another preferred embodiment of the present invention, the embodiment of the present invention may further include: the local DNS server may include a recording module, configured to record a correspondence between domain name information in the fully qualified domain name and the target-level DNS authoritative server.
In this case, the target level DNS interaction module of the location information server may further include the following sub-modules: the local domain name server interaction submodule is used for sending the first DNS query request to a local DNS server; receiving target level DNS authoritative server information returned by the local DNS;
a target level server interaction submodule, configured to send the first DNS query request to the target level DNS authoritative server;
the local DNS server may further include the following modules:
and the record searching module is used for judging whether a local DNS server has a corresponding relation record between the domain name information of the full-name domain name and the target level DNS authoritative server according to the first DNS query request, and if so, directly returning the information of the target level DNS authoritative server.
In the embodiment of the present invention, preferably, the DNS authoritative server to which the ISP belongs may include
The following modules:
the packaging response module is used for packaging the geographical position information into a DNS response data packet and returning the geographical position information when the DNS authoritative server to which the ISP belongs determines to return the geographical position information corresponding to the redirection full-name domain name according to a private strategy;
in this case, the location information server may further include the following modules:
and the geographic position information extraction module is used for extracting the geographic position information in the TXT format from the DNS response data packet.
For the system embodiment shown in fig. 4, since it is basically similar to the method embodiment shown in fig. 2, the description is simple, and the relevant points can be referred to the partial description of the method embodiment.
To facilitate a better understanding of the present invention to those skilled in the art, the present embodiment is further described below in conjunction with the specific example shown in FIG. 5.
Step T1, the application server sends IP geographical location inquiry request to the location information server:
8080, the IP address of the application server is "58.61.200.1", and the HTTP POST request sent by the application server is shown in the following codes:
POST/location HTTP/1.1
Host:location.org:8080
Content-Type:application/xml
Content-Length:80
<？xml version＝″1.0″？>
<locationRequestxmlns＝″urn:ietf:params:xml:ns:location″/>
step T2, the IP address conversion module of the location information server converts the IP address into FQDN;
the IP address translation module extracts the IP address "58.61.200.1" of the application server and constructs an FQDN: 1.200.61.58. loc.cn.;
step T3, a DNS query request encapsulation module of the location information server encapsulates the FQDN into a corresponding first DNS query request;
step T4, a target level DNS interaction module of the location information server positions a target level DNS authoritative server in each level of DNS authoritative servers according to the first DNS query request;
in this example, the target-level DNS interaction module may be configured to:
firstly, sending the first DNS query request to a root DNS authoritative server, and receiving top-level DNS authoritative server information returned by the root DNS authoritative server;
then, sending the first DNS query request to cn. top level DNS authoritative server, and receiving the information of the second level DNS authoritative server of loc.cn, returned by cn. top level DNS authoritative server;
and then, sending the first DNS query request to the information of the second-level DNS authoritative server in loc.cn.
T5, loc.cn. secondary DNS authoritative server uses DNAME mechanism to complete the mapping from IP address to ISP;
in this example, the loc.cn. zone file content segments are as follows:
$TTL 86400
loc.cn.IN SOA cnnic.loc.cn.zzz.cnic.cn.(
1；serial
3h；refresh after 3 hours
1h；retry after 1 hour
1w；expire after 1 week
1h；negative caching TTL of 1 hour
)
IN NS ns
$ORIGIN loc.cn.
ns IN A 218.241.108.190
isp1 IN NS ns.isp1
ns.isp1 IN A 218.241.108.193
isp2 IN NS ns.isp2
ns.isp2 IN A 218.241.108.191
；assume the following IP addresses are allocated by ISP1
200.61.58.loc.cn.IN DNAME 200.61.58.isp1.loc.cn.
；assume the following IP addresses are allocated by ISP2
211.102.241.loc.cn.IN DNAME 211.102.241.isp2.loc.cn.
the above code indicates that FQDN in the first DNS query request issued by the location information server is mapped to: 1.200.61.58.isp1.loc.cn., namely, the IP geographical location information belongs to the management of ISP1, and the address of the DNS authoritative server to which ISP1 belongs is acquired as follows: 218.241.108.193.
step T6, a DNS query request encapsulation module of the location information server encapsulates the FQDN into a corresponding second DNS query request, and a DNS interaction module to which the ISP belongs sends the second DNS query request to a DNS authoritative server to which the ISP1 belongs;
the zone file fragments on the DNS authority server to which ISP1 belongs are as follows:
$TTL 86400
200.61.58.isp1.loc.cn.IN SOA.isp1.loc.cn.zzz.cnnic.cn.(
1；serial
3h；refresh after 3 hours
1h；retry after 1 hour
1w；expire after 1 week
1h；negative caching ttl of 1 hour
)
IN NS ns.isp1.loc.cn.
3.200.61.58.isp1.loc.cn.IN TXT″country＝china a1＝guangdong a2＝0 a3＝shenzhen a4＝0a5＝baoan a6＝qianjing2road bld＝guhaihuayuan unit＝bdong2floor room＝100 plc＝0 pcn＝0pobox＝0 addcode＝0 seat＝0 rd＝0 rdsec＝0 rdbr＝0 rdsubbr＝0 prm＝0 pom＝0 longitude＝0.0latitude＝0.0 height＝0.0″
2.200.61.58.isp1.loc.cn.in TXT "centering ═ china a1 ═ guangdong a2 ═ 0 a3 ═ shenzhen a4 ═ 0 a5 ═ 20 baoan a6 ═ 2 way of advancing bld ═ ancient garden unit 2 No. floor 101 plc ═ 0 pcn ═ 0 pobox ═ 0 addcode ═ 0sea at ═ 0rd ═ 0 rdsec ═ 0 rbbr ═ 0 rdsubbr ═ 0 rbur ═ 0 prm ═ 0 lance ═ 0 long ═ 0.0 left ═ 0.0 right ═ 0.0 ═ 0-
1.200.61.58.isp1.loc.cn.in TXT "centering ═ china a1 ═ guangdong a2 ═ 0 a3 ═ shenzhen a4 ═ 0 a5 ═ 20 baoan a6 ═ 2 way of advancing bld ═ ancient garden unit ═ 2 way of building 103 plc ═ 0 pcn ═ 0 pobox ═ 0 addcode ═ 0sea at ═ 0rd ═ 0 rdsec ═ 0 rdsub ═ 0 prm ═ 0 plan ═ 0 ranging ═ 0.0 registration ═ 0 registration ═ 0.0 registration ═ 0
So far, the FQDN: the TXT record corresponding to isp1.loc.cn is "country a1 ═ guangdong a2 ═ 0 a3 ═ Shenzhen a4 ═ 0 a5 ═ Baoan a6 ═ 2 way forward bld ═ ancient sea garden unit No. 2 floor 103 plc ═ 0 pcn ═ 0 pobox ═ 0 addcode ═ 0 setat ═ 0rd ═ 0 rdsec ═ 0 prm ═ 0 sphere ═ 0 locality ═ 0.0 height ═ 0.0", and the authoritative server returns the DNS t record to the authoritative server which the DNS server belongs to and the authoritative DNS server is the DNS package.
Step T7, extracting the geographical location information in TXT record format from the DNS response packet by the geographical location format conversion module of the location information server, packaging the geographical location information into XML format according to the standard specification of RFC5139, and returning the XML format to the application program server by the return module; specific operations may refer to the following codes:
<？xml version＝″1.0″encoding＝″UTF-8″？>
<presence xmlns＝″urn:ietf:params:xml:ns:pidf″
xmlns:gp＝″urn:ietf:params:xml:ns:pidf:geopriv10″
xmlns:cl＝″urn:ietf:params:xml:ns:pidf:geopriv10:civicLoc″
entity＝″pres:geotarget@example.com″>
<tuple id＝″sg89ae″>
<status>
<gp:geopriv>
<gp:location-info>
<cl:civicAddress>
< cl: country > China </cl: country >
< cl: A1 Guangdong: A1>
<cl:A2>0</cl:A2>
< cl: A3> Shenzhen: A3>
<cl:A4>0</cl:A4>
< cl: A5 Baoan </cl: A5>
< cl: A6> Advance 2-way </cl: A6>
< cl: BLD > ancient sea Garden: BLD >
< cl: UNIT > building 2 </cl: UNIT >
<cl:ROOM>103</cl:ROOM>
<cl:PLC>0</cl:PLC>
<cl:PCN>0</cl:PCN>
<cl:POBOX>0</cl:POBOX>
<cl:ADDCODE>0</cl:ADDCODE>
<cl:SEAT>0</cl:SEAT>
<cl:RD>0</cl:RD>
<cl:RDSEC>0</cl:RDSEC>
<cl:RDBR>0</cl:RDBR>
<cl:RDSUBBR>0</cl:RDSUBBR>
<cl:PRM>0</cl:PRM>
<cl:POM>0.</cl:POM>
</cl:civicAddress>
</gp:location-info>
<gp:usage-rules>
<gp:retransmission-allowed>yes</gp:retransmission-allowed>
<gp:retention-expiry>2008-06-23T04:57:29Z</gp:retention-expiry>
</gp:usage-rules>
</gp:geopriv>
</status>
<timestamp>2008-12-30T09:22:14Z</timestamp>
</tuple>
</presence>
And step T8, the application program server processes the XML format location information to provide the location-based related service for the user.
That is, in the above example, when the user queries the corresponding geographic location information according to the IP address "58.61.200.1", the user can obtain the accurate geographic location information of "2 th building 103 of ancient sea garden in the precious security region of shenzhen, guangdong province, china", etc.
Referring to fig. 5, a structure diagram of an embodiment of a location information server according to the present invention is shown, where the location information server is configured to receive an IP geographic location query request initiated by an application server, where the query request includes an IP address; and returning the geographic position information in an XML format to the application program server through interaction with the target level DNS authoritative server and the DNS authoritative server to which the ISP belongs; wherein,
the location information server may specifically include the following modules:
a geographic location query request receiving module 501, configured to receive the IP geographic location query request, where the query request includes an IP address;
an IP address conversion module 502, configured to convert the IP address into a fully-qualified domain name;
a DNS query request encapsulating module 503, configured to encapsulate the fully qualified domain name into a corresponding first DNS query request; and encapsulating the redirected fully-qualified domain name into a corresponding second DNS query request;
a target-level DNS interaction module 504, configured to locate a target-level DNS authoritative server among the DNS authoritative servers of each level according to the first DNS query request;
the DNS interaction module 505 to which the ISP belongs is configured to send the second DNS query request to the DNS authoritative server to which the ISP belongs, and receive the geographic location information in the TXT format returned by the request;
a geographic location format conversion module 506, configured to convert the TXT format geographic location information into XML format information;
a returning module 507, configured to return the geographic location information in the XML format to the application server;
the target level DNS authoritative server is positioned in each level of DNS authoritative servers and is used for redirecting the fully qualified domain name to obtain the information of the DNS authoritative server to which the mapped ISP belongs;
and the DNS authoritative server to which the ISP belongs is used for returning the geographical location information in the TXT format corresponding to the redirection full-name domain name based on a private policy according to the second DNS query request.
For the system embodiment shown in fig. 5, since it is basically similar to the method embodiment shown in fig. 2, the description is simple, and the relevant points can be referred to the partial description of the method embodiment.
The method, the system and the location information server for acquiring the IP geographical location information provided by the present invention are introduced in detail, and a specific example is applied in the text to explain the principle and the implementation of the present invention, and the description of the above embodiment is only used to help understanding the method and the core idea of the present invention; meanwhile, for a person skilled in the art, according to the idea of the present invention, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present invention.
Claims (12)
1. A method for obtaining IP geographical location information, wherein the geographical location information is stored in a DNS authoritative server to which an ISP belongs, the method comprises:
receiving an IP geographical position query request initiated by an application program, wherein the IP geographical position query request comprises an IP address;
converting the IP address into a fully-qualified domain name, and encapsulating the fully-qualified domain name into a corresponding first DNS query request;
according to the first DNS query request, positioning a target level DNS authoritative server in all levels of DNS authoritative servers; redirecting the fully qualified domain name by the target level DNS authoritative server to obtain the information of the DNS authoritative server to which the mapped ISP belongs;
packaging the redirected fully-qualified domain name into a corresponding second DNS query request, sending the second DNS query request to the DNS authoritative server to which the ISP belongs, and returning the TXT-format geographic position information corresponding to the redirected fully-qualified domain name by the DNS authoritative server to which the ISP belongs according to a private strategy;
and converting the geographical position information into information in an XML format, and returning the information to the application program.
2. The method according to claim 1, wherein the full-name domain name comprises top-level domain name information and sub-level domain name information, the respective levels of DNS authoritative servers comprise a root DNS authoritative server, a top-level DNS authoritative server, and a sub-level DNS authoritative server, and the step of locating the target-level DNS authoritative server comprises:
sending the first DNS query request to a root DNS authoritative server, and returning top-level DNS authoritative server information pointed by the top-level domain name information by the root DNS authoritative server;
sending the first DNS query request to the top-level DNS authoritative server, and returning the information of the sub-level DNS authoritative server pointed by the sub-level domain name information by the top-level DNS authoritative server;
and sending the first DNS inquiry request to the subordinate DNS authoritative server.
3. The method of claim 2, further comprising:
and recording the corresponding relation between the domain name information in the fully-qualified domain name and the target level DNS authoritative server to the local DNS server.
4. The method of claim 3, wherein the step of locating the target-level DNS authoritative server further comprises:
sending the first DNS query request to a local DNS server;
the local DNS server judges whether a corresponding relation record of the domain name information of the full-name domain name and a target level DNS authoritative server exists, if so, the information of the target level DNS authoritative server is directly returned;
and sending the first DNS inquiry request to the target-level DNS authoritative server.
5. The method of claim 1, 2, 3 or 4, wherein the step of returning the IP geolocation information comprises:
if the DNS authoritative server to which the ISP belongs determines to return the geographical location information corresponding to the redirected fully-qualified domain name according to a private policy, packaging the geographical location information into a DNS response data packet and returning the DNS response data packet;
the method further comprises the following steps:
extracting the geographical location information in the TXT format from the DNS response packet.
6. The method of claim 5, wherein the target-level DNS authoritative server redirection operation is a Domain name redirection DNAME operation compliant with RFC2672 protocol; the XML format is an XML format conforming to RFC5193 protocol.
7. A system for obtaining IP geolocation information, comprising: the method comprises the following steps that an application program server, a location information server, a target level DNS authoritative server and a DNS authoritative server to which an ISP belongs: wherein,
the application program server is used for sending an IP geographical position query request and receiving geographical position information in an XML format returned corresponding to the request;
the target level DNS authoritative server is positioned in each level of DNS authoritative servers and is used for redirecting the fully qualified domain name to obtain the information of the DNS authoritative server to which the mapped ISP belongs;
the DNS authoritative server to which the ISP belongs is used for returning the geographical position information in the TXT format corresponding to the redirection full-name domain name based on a private strategy according to the second DNS query request;
the position information server comprises the following modules:
a geographic location query request receiving module, configured to receive the IP geographic location query request, where the query request includes an IP address;
the IP address conversion module is used for converting the IP address into a full-name domain name;
a DNS query request encapsulation module used for encapsulating the fully qualified domain name into a corresponding first DNS query request; and encapsulating the redirected fully-qualified domain name into a corresponding second DNS query request;
the target level DNS interaction module is used for positioning a target level DNS authoritative server in each level of DNS authoritative servers according to the first DNS query request;
the DNS interaction module to which the ISP belongs is used for sending the second DNS query request to the DNS authoritative server to which the ISP belongs and receiving the geographical position information in the TXT format returned by corresponding to the request;
the geographic position format conversion module is used for converting the geographic position information in the TXT format into information in an XML format;
and the return module is used for returning the geographic position information in the XML format to the application program server.
8. The system of claim 7, wherein the fully qualified domain name comprises top level domain name information and sub-domain name information, and the respective levels of DNS authoritative servers comprise a root DNS authoritative server, a top level DNS authoritative server, and a sub-level DNS authoritative server; the root DNS authoritative server is used for returning top level DNS authoritative server information pointed by the top level domain name information according to the first DNS query request; the top level DNS authoritative server is used for returning the information of the sub-level DNS authoritative server pointed by the sub-domain name information according to the first DNS query request;
the target level DNS interaction module of the location information server comprises:
the root domain name server interaction submodule is used for sending the first DNS query request to a root DNS authoritative server and receiving top-level DNS authoritative server information returned by the root DNS authoritative server;
the top-level domain name server interaction submodule is used for sending the first DNS query request to the top-level DNS authoritative server and receiving information of the sub-level DNS authoritative server returned by the top-level DNS authoritative server;
and the subordinate domain name server interaction submodule is used for sending the first DNS query request to the subordinate DNS authoritative server.
9. The system of claim 8, further comprising:
a local DNS server, comprising:
and the recording module is used for recording the corresponding relation between the domain name information in the fully-qualified domain name and the target level DNS authoritative server.
10. The system of claim 9, wherein the target-level DNS interaction module of the location information server further comprises:
the local domain name server interaction submodule is used for sending the first DNS query request to a local DNS server; receiving target level DNS authoritative server information returned by the local DNS;
a target level server interaction submodule, configured to send the first DNS query request to the target level DNS authoritative server;
the local DNS server further comprises:
and the record searching module is used for judging whether a local DNS server has a corresponding relation record between the domain name information of the full-name domain name and the target level DNS authoritative server according to the first DNS query request, and if so, directly returning the information of the target level DNS authoritative server.
11. The system according to claim 7, 8, 9 or 10, wherein the DNS authoritative server to which the ISP belongs comprises:
the packaging response module is used for packaging the geographical position information into a DNS response data packet and returning the geographical position information when the DNS authoritative server to which the ISP belongs determines to return the geographical position information corresponding to the redirection full-name domain name according to a private strategy;
the location information server further includes:
and the geographic position information extraction module is used for extracting the geographic position information in the TXT format from the DNS response data packet.
12. A location information server is characterized in that the location information server is used for receiving an IP geographical location query request initiated by an application program server, wherein the query request comprises an IP address; and returning the geographic position information in an XML format to the application program server through interaction with the target level DNS authoritative server and the DNS authoritative server to which the ISP belongs; the target level DNS authoritative server is positioned in each level of DNS authoritative servers and is used for redirecting the fully qualified domain name to obtain the information of the DNS authoritative server to which the mapped ISP belongs; the DNS authoritative server to which the ISP belongs is used for returning the geographical position information in the TXT format corresponding to the redirection full-name domain name based on a private strategy according to the second DNS query request;
the location information server specifically includes the following modules:
a geographic location query request receiving module, configured to receive the IP geographic location query request, where the query request includes an IP address;
the IP address conversion module is used for converting the IP address into a full-name domain name;
a DNS query request encapsulation module used for encapsulating the fully qualified domain name into a corresponding first DNS query request; and encapsulating the redirected fully-qualified domain name into a corresponding second DNS query request;
the target level DNS interaction module is used for positioning a target level DNS authoritative server in each level of DNS authoritative servers according to the first DNS query request;
the DNS interaction module to which the ISP belongs is used for sending the second DNS query request to the DNS authoritative server to which the ISP belongs and receiving the geographical position information in the TXT format returned by corresponding to the request;
the geographic position format conversion module is used for converting the geographic position information in the TXT format into information in an XML format;
and the return module is used for returning the geographic position information in the XML format to the application program server.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200910085327.2A CN101902442B (en) | 2009-05-25 | 2009-05-25 | Method, system and position information server for acquiring IP geographic position information |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200910085327.2A CN101902442B (en) | 2009-05-25 | 2009-05-25 | Method, system and position information server for acquiring IP geographic position information |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101902442A true CN101902442A (en) | 2010-12-01 |
| CN101902442B CN101902442B (en) | 2014-03-05 |
Family
ID=43227649
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN200910085327.2A Active CN101902442B (en) | 2009-05-25 | 2009-05-25 | Method, system and position information server for acquiring IP geographic position information |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101902442B (en) |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102487396A (en) * | 2010-12-02 | 2012-06-06 | 中兴通讯股份有限公司 | User position determining method and system |
| CN103501357A (en) * | 2013-09-18 | 2014-01-08 | 深圳先进技术研究院 | Domain name resolution system and domain name resolution method |
| CN103973819A (en) * | 2013-01-25 | 2014-08-06 | 搜房媒体技术（北京）有限公司 | Method, related device and system for responding to request for community domain name |
| CN105025059A (en) * | 2014-04-28 | 2015-11-04 | 清华大学 | Location information service system |
| CN105338126A (en) * | 2014-07-17 | 2016-02-17 | 阿里巴巴集团控股有限公司 | Method and server of remote information query |
| CN106096040A (en) * | 2016-06-29 | 2016-11-09 | 中国人民解放军国防科学技术大学 | Organization web ownership place method of discrimination based on search engine and device thereof |
| CN107613039A (en) * | 2017-09-19 | 2018-01-19 | 北京小米移动软件有限公司 | IP address attribution inquiry method, device, system and storage medium |
| CN108337271A (en) * | 2017-01-17 | 2018-07-27 | 北京云端智度科技有限公司 | A method of promoting DNS security and performance |
| CN109104506A (en) * | 2017-06-20 | 2018-12-28 | 腾讯科技（深圳）有限公司 | The determination method, apparatus and computer readable storage medium of domain name mapping rule |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1207668A2 (en) * | 2000-11-16 | 2002-05-22 | Microsoft Corporation | System and method for performing client-centric load balancing of multiple globally-dispersed servers |
| CN1631023A (en) * | 2001-10-24 | 2005-06-22 | 奥列格·亚历山德罗维奇·谢列布连尼科夫 | Method and system for getting on-line status, authentication, verification, authorization, communication and transaction services for web-enabled hardware and software, based on uniform telephone addr |
| CN1981284A (en) * | 2004-05-04 | 2007-06-13 | 派克斯费尔有限公司 | Systems and methods for direction of communication traffic |
| CN101176293A (en) * | 2004-11-05 | 2008-05-07 | 株式会社东芝 | Network discovery mechanism |
-
2009
- 2009-05-25 CN CN200910085327.2A patent/CN101902442B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1207668A2 (en) * | 2000-11-16 | 2002-05-22 | Microsoft Corporation | System and method for performing client-centric load balancing of multiple globally-dispersed servers |
| CN1631023A (en) * | 2001-10-24 | 2005-06-22 | 奥列格·亚历山德罗维奇·谢列布连尼科夫 | Method and system for getting on-line status, authentication, verification, authorization, communication and transaction services for web-enabled hardware and software, based on uniform telephone addr |
| CN1981284A (en) * | 2004-05-04 | 2007-06-13 | 派克斯费尔有限公司 | Systems and methods for direction of communication traffic |
| CN101176293A (en) * | 2004-11-05 | 2008-05-07 | 株式会社东芝 | Network discovery mechanism |
Cited By (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102487396A (en) * | 2010-12-02 | 2012-06-06 | 中兴通讯股份有限公司 | User position determining method and system |
| CN103973819B (en) * | 2013-01-25 | 2018-02-02 | 搜房媒体技术（北京）有限公司 | A kind of method, relevant apparatus and system for responding community's domain name request |
| CN103973819A (en) * | 2013-01-25 | 2014-08-06 | 搜房媒体技术（北京）有限公司 | Method, related device and system for responding to request for community domain name |
| CN103501357A (en) * | 2013-09-18 | 2014-01-08 | 深圳先进技术研究院 | Domain name resolution system and domain name resolution method |
| CN105025059A (en) * | 2014-04-28 | 2015-11-04 | 清华大学 | Location information service system |
| CN105025059B (en) * | 2014-04-28 | 2019-05-14 | 清华大学 | Location information service system |
| CN105338126B (en) * | 2014-07-17 | 2018-10-23 | 阿里巴巴集团控股有限公司 | The method and server of remote-query information |
| US10225231B2 (en) | 2014-07-17 | 2019-03-05 | Alibaba Group Holding Limited | Method and server of remote information query |
| CN105338126A (en) * | 2014-07-17 | 2016-02-17 | 阿里巴巴集团控股有限公司 | Method and server of remote information query |
| CN106096040A (en) * | 2016-06-29 | 2016-11-09 | 中国人民解放军国防科学技术大学 | Organization web ownership place method of discrimination based on search engine and device thereof |
| CN106096040B (en) * | 2016-06-29 | 2019-06-04 | 中国人民解放军国防科学技术大学 | Organization web ownership place method of discrimination and its device based on search engine |
| CN108337271A (en) * | 2017-01-17 | 2018-07-27 | 北京云端智度科技有限公司 | A method of promoting DNS security and performance |
| CN109104506A (en) * | 2017-06-20 | 2018-12-28 | 腾讯科技（深圳）有限公司 | The determination method, apparatus and computer readable storage medium of domain name mapping rule |
| CN109104506B (en) * | 2017-06-20 | 2021-05-14 | 腾讯科技（深圳）有限公司 | Method and device for determining domain name resolution rule and computer readable storage medium |
| CN107613039A (en) * | 2017-09-19 | 2018-01-19 | 北京小米移动软件有限公司 | IP address attribution inquiry method, device, system and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101902442B (en) | 2014-03-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101902442A (en) | Method, system and position information server for acquiring IP geographic position information | |
| US9866523B2 (en) | Method and system for increasing speed of domain name system resolution within a computing device | |
| US7752210B2 (en) | Method of determining geographical location from IP address information | |
| US7225272B2 (en) | Method and apparatus for providing name services | |
| US9231903B2 (en) | System and method for resolving a DNS request using metadata | |
| US9246874B2 (en) | Virtual domain name system | |
| US20060218289A1 (en) | Systems and methods of registering and utilizing domain names | |
| US9497159B2 (en) | System and method for IP network semantic label storage and management | |
| CN106797410A (en) | Domain name analytic method and device | |
| US20030233454A1 (en) | Creating a public identity for an entity on a network | |
| BRPI0822330B1 (en) | METHOD OF ACQUISITION OF SERVER IDENTIFIER BASED ON DEVICE LOCATION, APPLIANCE, DOMAIN NAME SYSTEM, SYSTEM FOR SIGNALING CONTROL INFORMATION AND MOBILE DEVICE | |
| CN108011995A (en) | Strange land implementation method more living, strange land service platform more living and storage medium | |
| CN107786678B (en) | Domain name resolution method, device and system | |
| CN107836103A (en) | Resource discovering in local network | |
| CN105282269A (en) | Local DNS root server configuration method and service method | |
| CN101499996A (en) | Domain name differentiate parsing method and domain name server | |
| CN102594885A (en) | Sensor network analyzing intercommunicating platform, sensor network intercommunicating method and system | |
| WO2014089872A1 (en) | Method and system for supporting dns resolution of domain name group | |
| US20180375818A1 (en) | Dns-based method of transmitting data | |
| WO2009012992A2 (en) | Requester-aware domain name system | |
| WO2005093999A1 (en) | Systems and methods of registering and utilizing domain names | |
| US9183368B2 (en) | Validating control of domain zone | |
| US8117439B2 (en) | Issuing secure certificate using domain zone control validation | |
| CN105245626B (en) | The method for realizing website addressing using quick domain name in private network | |
| Nikkel | Domain name forensics: a systematic approach to investigating an internet presence |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20210203 Address after: 100190 room 506, building 2, courtyard 4, South 4th Street, Zhongguancun, Haidian District, Beijing Patentee after: CHINA INTERNET NETWORK INFORMATION CENTER Address before: 100190 Building 1, software park, Chinese Academy of Sciences, No.4, Nansi street, Zhongguancun, Haidian District, Beijing Patentee before: Computer Network Information Center, Chinese Academy of Sciences |
|
| TR01 | Transfer of patent right |