WO2017096888A1 - 域名解析***的实现方法及装置 - Google Patents

域名解析***的实现方法及装置 Download PDF

Info

Publication number
WO2017096888A1
WO2017096888A1 PCT/CN2016/089471 CN2016089471W WO2017096888A1 WO 2017096888 A1 WO2017096888 A1 WO 2017096888A1 CN 2016089471 W CN2016089471 W CN 2016089471W WO 2017096888 A1 WO2017096888 A1 WO 2017096888A1
Authority
WO
WIPO (PCT)
Prior art keywords
request
domain name
server
name resolution
client
Prior art date
Application number
PCT/CN2016/089471
Other languages
English (en)
French (fr)
Inventor
李茗
赵瑞前
Original Assignee
乐视控股（北京）有限公司
乐视云计算有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 乐视控股（北京）有限公司, 乐视云计算有限公司 filed Critical 乐视控股（北京）有限公司
Priority to US15/246,536 priority Critical patent/US20170171147A1/en
Publication of WO2017096888A1 publication Critical patent/WO2017096888A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/14—Network architectures or network communication protocols for network security for detecting or protecting against malicious traffic
    • H04L63/1441—Countermeasures against malicious traffic
    • H04L63/1466—Active attacks involving interception, injection, modification, spoofing of data unit addresses, e.g. hijacking, packet injection or TCP sequence number attacks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/563—Data redirection of data network streams

Definitions

  • the embodiments of the present invention relate to the field of Internet technologies, and in particular, to a method and an apparatus for implementing a domain name resolution system.
  • IP Internet Protocol Address
  • the prior art uses a Domain Name System (DNS) as a distributed database in which domain names and IP addresses are mapped to each other, which enables users to access the Internet more conveniently without having to remember The number of IP strings read directly by the machine.
  • DNS Domain Name System
  • DNS hijacking Since the role of the DNS is to map the domain name to a real computer-recognizable IP address so that the computer can communicate further, deliver the URL and content, etc., domain name hijacking (DNS hijacking) often occurs. DNS hijacking intercepts the request for domain name resolution within the hijacked network, analyzes the requested domain name, and releases the request outside the scope of the review. Otherwise, it returns a fake IP address or does nothing to make the request unresponsive. The effect is specific to the A fake URL cannot be reflected or accessed by the network. Therefore, how to make the request for self-access is not maliciously hijacked becomes an urgent problem for Internet vendors to maintain their own services.
  • DNS hijacking intercepts the request for domain name resolution within the hijacked network, analyzes the requested domain name, and releases the request outside the scope of the review. Otherwise, it returns a fake IP address or does nothing to make the request unresponsive. The effect is specific to the A fake URL cannot be reflected or accessed by the network. Therefore, how to make the request for self-access is not maliciously hijacke
  • the embodiment of the invention provides a method and a device for implementing a domain name resolution system, which are used to solve the existing In the technology, the normal domain name access request of the user is maliciously hijacked, and the target address can be securely accessed through a normal HTTP request.
  • an embodiment of the present invention provides a method for implementing a domain name resolution system, where the method is mainly used on one side of a transition server, and includes:
  • the transition server receives a request from a client, the transition server having a preset IP address;
  • the request that the transition server receives the client includes:
  • the transition server receives a request sent by the client according to a preset IP address that the transition server has, and the preset IP address is a preset virtual IP address.
  • the preset virtual IP address has at least two;
  • the request of the transition server to receive the client includes:
  • the transition server receives a request sent by the client according to a different virtual IP address selected by the service type.
  • forwarding the request to the execution server includes:
  • the transition server forwards the request to the target execution server according to the load status of the execution server
  • the transition server forwards the request to a corresponding execution server based on the content of the request.
  • an embodiment of the present invention provides a method for implementing a domain name resolution system, where the method is mainly used to execute a server side, including:
  • the execution server receives the request of the client forwarded by the transition server
  • the domain name resolution result corresponding to the request is returned to the transition server.
  • domain name resolution result corresponding to the request configured according to the request is:
  • an embodiment of the present invention provides an apparatus for implementing a domain name resolution system, where the apparatus is mainly located in a transition server, and includes:
  • a receiving unit configured to receive a request from a client
  • a forwarding unit configured to forward the request to an execution server, and receive a domain name resolution result returned by the execution server;
  • a returning unit configured to return the domain name resolution result to the client.
  • the receiving unit is configured to receive a request sent by the client according to a preset IP address that the transition server has, where the preset IP address is a preset virtual IP address.
  • the preset virtual IP address has at least two; the receiving unit is configured to receive a request sent by the client according to different virtual IP addresses selected by the service type.
  • the forwarding unit is configured to forward the request to the target execution server according to the load status of the execution server; and is further configured to forward the request to the corresponding execution server according to the content of the request.
  • an embodiment of the present invention provides an apparatus for implementing a domain name resolution system, where the apparatus is mainly located in an execution server, and includes:
  • a receiving unit configured to receive a request of a client forwarded by the transition server
  • a searching unit configured to search, according to the request, a domain name resolution result corresponding to the request configured by itself;
  • a return unit configured to return a domain name resolution result corresponding to the request to the transition server.
  • the searching unit includes:
  • An obtaining module configured to obtain an export IP address of the request
  • a traversal module configured to traverse an egress IP address configured in the execution server and a corresponding domain name resolution result thereof;
  • a searching module configured to search, in the execution server, a corresponding domain name resolution result according to the requested egress IP address.
  • an embodiment of the present invention provides an apparatus for implementing a domain name resolution system, where the apparatus is mainly located in a transition server, and includes:
  • a memory configured to store executable instructions of the processor
  • the processor is configured to:
  • an embodiment of the present invention provides an apparatus for implementing a domain name resolution system, where the apparatus is mainly located in an execution server, and includes:
  • a memory configured to store executable instructions of the processor
  • the processor is configured to:
  • the domain name resolution result corresponding to the request is returned to the transition server.
  • the method and device for implementing the domain name resolution system provided by the embodiment of the present invention can be uniformly sent by the client to the transition server based on the IP address preset by the transition server, and the transition server forwards the received request to the execution server.
  • the corresponding domain name resolution result is found in the record information of the execution server and returned to the client. Since the present invention can directly send the request sent by the client based on the preset IP address, the DNS resolution in the prior art is not needed, thereby effectively avoiding the DNS hijacking phenomenon occurring in the DNS resolution process, thereby realizing
  • the purpose of secure access to the destination address is through a normal HTTP request from the client.
  • FIG. 1 is a flowchart of a method for implementing a domain name resolution system according to an embodiment of the present invention
  • FIG. 2 is a flowchart of a method for implementing another domain name resolution system according to an embodiment of the present invention
  • FIG. 3 is a structural block diagram of an apparatus for implementing a domain name resolution system according to an embodiment of the present invention
  • FIG. 4 is a block diagram of an apparatus for implementing another domain name resolution system according to an embodiment of the present invention.
  • FIG. 5 is a structural block diagram of another apparatus for implementing a domain name resolution system according to an embodiment of the present invention.
  • FIG. 6 is a schematic structural diagram of a server according to an embodiment of the present invention.
  • DNS is a distributed database that maps domain names and IP addresses to each other. It enables users to easily access the Internet without having to remember the IP number string that can be directly read by the machine.
  • the host name is used to obtain the IP address corresponding to the host name.
  • DNS domain name resolution system
  • the embodiment of the present invention provides a method for implementing a domain name resolution system.
  • the method is mainly used on one side of a transition server. As shown in FIG. 1 , the method includes:
  • the transition server receives a request from a client, where the transition server has a preset IP address.
  • the transition server receives a request sent by the client according to a preset IP address that the transition server has, and the preset IP address is a preset virtual IP address.
  • the preset virtual IP address has at least two; the request that the transition server receives the client includes: The transition server receives a request sent by the client according to a different virtual IP address selected by the service type.
  • the embodiment of the present invention may send the client's request to the transition server based on the preset IP address, that is, send the HTTP request sent by the client directly to the preset IP address, and the The request is sent to the transition server set by the embodiment of the present invention.
  • the embodiment of the present invention may set a transition server with an IP address, and the transition server receives the request of the client.
  • forwarding the request to the execution server includes: the transition server forwarding the request to a target execution server according to a load status of the execution server; the transition server is configured according to the content of the request The request is forwarded to the corresponding execution server. Since the client's request needs to be received by the transition server in step 101, the request sent by the client is received by the transition server with the preset IP address. In the embodiment of the present invention, the transition server only needs to receive the client's request without parsing the client's domain name. The transition server is only responsible for collecting the client's request and forwarding the client's request to the execution server according to the request and the load of the server.
  • the execution server is a server that actually executes client requests.
  • the corresponding domain name resolution result includes: each operator information corresponding to the egress IP address, and the configured domain name and geographic location information.
  • the actual execution of the client request is an execution server. Therefore, in the embodiment of the present invention, the transition server needs to receive the domain name resolution result corresponding to the client request returned by the execution server, and the transit server performs the translation of the domain name resolution result. Therefore, the client sees that the domain name resolution result is from a preset IP address.
  • the method for implementing the domain name resolution system can be uniformly sent by the client to the transition server based on the IP address preset by the transition server, and the transition server forwards the received request to the execution server, and executes the server.
  • the corresponding domain name resolution result is found in the record information and returned to the client. Since the present invention can directly send the request sent by the client based on the preset IP address, the DNS resolution in the prior art is not needed, thereby effectively avoiding the DNS hijacking phenomenon occurring in the DNS resolution process, thereby realizing Normal through the client
  • the HTTP request can be used to securely access the destination address.
  • the embodiment of the present invention further provides a method for implementing a domain name resolution system, where the method is mainly used to execute a server side, as shown in FIG. 2, the method includes:
  • the execution server receives the request of the client forwarded by the transition server.
  • the transition server only performs the collection and transfer of the client request, and the execution server performs the client request, so the execution server needs to receive the request of the client forwarded by the transition server.
  • the execution server Since the execution server is actually executing the client request in the embodiment of the present invention, the execution server stores the record information of the domain name resolution result, that is, the information in the execution server can be manually configured.
  • the execution server in the embodiment of the present invention only needs to search for the corresponding domain name resolution result in the execution server according to the requested domain name to obtain the requested operator information, the real IP address, and the related geographical location information. .
  • the embodiment of the present invention needs to return the domain name resolution result to the client by the transition server, in order to enable the client to see that the domain name resolution result is from the preset IP address used for sending the request.
  • the real result of the domain name resolution is the execution server. Therefore, the execution server needs to return the domain name resolution result to the transition server first, and the transition server forwards the domain name resolution result to the client, so that the client can see the domain name.
  • the result of the parsing comes from the default IP address used to send the request.
  • the method for implementing the domain name resolution system can be uniformly sent by the client to the transition server based on the IP address preset by the transition server, and the transition server forwards the received request to the execution server, and executes the server.
  • the corresponding domain name resolution result is found in the record information and returned to the client. Since the present invention can directly send the request sent by the client based on the preset IP address, the DNS resolution in the prior art is not needed, thereby effectively avoiding the DNS hijacking phenomenon occurring in the DNS resolution process, thereby realizing
  • the purpose of secure access to the destination address is through a normal HTTP request from the client.
  • the HTTP request sent by the client when the HTTP request sent by the client is sent to the transition server based on the preset IP address in the transition server, the HTTP request of the client may be sent to the transition server based on the preset virtual IP address.
  • a virtual IP is an IP address that is not connected to a network interface card in a particular computer or computer.
  • the client's HTTP request is sent to this virtual IP address, but all data passes through the real network interface.
  • the client's request is directly sent to the transition server corresponding to the virtual IP address, and does not enter the DNS server in the prior art for domain name resolution, so that DNS hijacking can be effectively avoided.
  • the preset virtual IP address may have multiple (at least two); when there are multiple virtual IP addresses, different virtuals may be selected according to the requested service type.
  • the IP address sends the client's request to the transition server. For example, when there are two preset virtual IP addresses (VIP-1, VIP-2), the finance department can request VIP-1, the administrative department can use VIP-2, and the transition server uses two presets.
  • the virtual IP address receives the network request from the client, and forwards the received request on the VIP-1 to the corresponding execution server 1, and forwards the received request on the VIP-2 to the corresponding execution server 2.
  • the embodiment of the present invention also needs to forward the client's request to the execution server that actually executes the client request. Since the transition server in the embodiment of the present invention is a unique entry point for receiving a client request, the transition server needs to forward a large number of client requests to the execution server. If all client requests are forwarded to the same execution server, then The load on the execution server may be too large, which may affect the operational efficiency of the execution server and cause processing failure. Therefore, the transition server in the embodiment of the present invention needs to forward the client request according to a certain rule.
  • the transition server in the embodiment of the present invention may forward the client's request to the target execution server according to the load status of the execution server.
  • the plurality of execution servers including the target execution server have the same content and provide the same service.
  • the transition server only needs to perform each execution according to the load status of each execution server. Selecting a target execution server with a normal load condition (below the load status warning value) and forwarding the client request to the selected target execution server Further, the transition server may also record the schedule, and when other packets requested by the client arrive, it is also forwarded to the previously selected target execution server.
  • the transition server in the embodiment of the present invention may further forward the client request to the corresponding execution server according to the content requested by the client.
  • each execution server may provide a different service, and when the client request arrives, the transition server may select a corresponding execution server to execute the request according to the requested content.
  • the client only knows the virtual IP address of the transition server configuration, and the transition server is responsible for forwarding the client request to the corresponding execution server through the content requested by the client.
  • the transition server when the transition server receives the request sequence BBBBDCD sent by the client, the transition server can send all the requests B to the execution server 1 according to the content of the request, and send the request C and the request D to the execution server 2, that is, The execution server 1 processes the request sequence BBB, and the execution server 2 processes the request sequence CDCD.
  • the execution server 1 processes the request sequence BBB
  • the execution server 2 processes the request sequence CDCD.
  • the domain name resolution result that is, the carrier information corresponding to each IP address and its configured domain name and geographic location information are recorded in the execution server of the embodiment of the present invention. Therefore, after the transition server forwards the client request to the execution server, the corresponding domain name resolution result needs to be searched in the execution server according to the request. In the process of actually searching for the domain name resolution result, the egress IP address of the request needs to be obtained first, that is, the remote address information of the client is obtained. In actual situations, because the IP address information carried in the HTTP request header can be forged, the IP address carried in the request header is not trusted, but HTTP uses TCP to transfer information between two computers (usually a server and a client).
  • the protocol so the remote address information of the client, that is, the export IP of the request, can be obtained from the TCP connection.
  • the egress IP address recorded in the server and its corresponding domain name resolution result may be traversed according to the egress IP address requested by the client.
  • the IPlib is configured in the execution server of the embodiment of the present invention, and the IPlib includes the remote address information (export IP address information) of the client and its corresponding Internet Service Provider (ISP) information and geographic location. information.
  • the execution server is similar to the configured IP database, and includes an egress IP address segment and corresponding information data, and the corresponding information data generally includes a country, a region (province/state), a city, a street, a latitude and longitude, and an ISP. Information such as providers.
  • the execution is performed according to the egress IP address requested by the client. Find the corresponding domain name resolution result in the server. After the corresponding domain name resolution result is found in the execution server, the corresponding domain name resolution result is forwarded to the client through the transition server, so that the client sees that the domain name resolution result is from the preset virtual IP address. address.
  • the embodiment of the present invention can effectively prevent the user from obtaining the invalid domain name resolution result of the wrong ISP provider when setting the DNS server inaccurate.
  • the embodiment of the present invention provides an apparatus for implementing a domain name resolution system.
  • the device is mainly located in a transition server.
  • the device includes: a receiving unit 31, and a forwarding. Unit 32 and return unit 33, wherein
  • a receiving unit 31 configured to receive a request from a client
  • the forwarding unit 32 is configured to forward the request to the execution server, and receive a domain name resolution result returned by the execution server;
  • the returning unit 33 is configured to return the domain name resolution result to the client.
  • the receiving unit 31 is configured to receive a request sent by the client according to a preset IP address that the transition server has, where the preset IP address is a preset virtual IP address.
  • the preset virtual IP address has at least two; the receiving unit 31 is configured to receive a request sent by the client according to different virtual IP addresses selected by the service type.
  • the forwarding unit 32 is configured to forward the request to the target execution server according to the load status of the execution server; and is further configured to forward the request to the corresponding execution server according to the content of the request.
  • the device for implementing the domain name resolution system can send the request to the transition server uniformly by the client based on the IP address preset by the transition server, and the transition server forwards the received request to the execution server, and executes the server.
  • the corresponding domain name resolution result is found in the record information and returned to the client. Since the present invention can directly send the request sent by the client based on the preset IP address, the DNS resolution in the prior art is not needed, thereby effectively avoiding the DNS hijacking phenomenon occurring in the DNS resolution process, thereby realizing
  • the purpose of secure access to the destination address is through a normal HTTP request from the client.
  • an embodiment of the present invention provides an apparatus for implementing a domain name resolution system, where the apparatus is mainly located in an execution server.
  • the apparatus includes: a receiving unit 41, and a search Unit 42 and return unit 43, wherein
  • the receiving unit 41 is configured to receive a request of the client forwarded by the transition server;
  • the searching unit 42 is configured to search, according to the request, a domain name resolution result corresponding to the request configured by itself;
  • the returning unit 43 is configured to return the domain name resolution result corresponding to the request to the transition server.
  • the searching unit 42 includes:
  • the obtaining module 421 is configured to obtain an exit IP address of the request.
  • the traversing module 422 is configured to traverse the egress IP address configured in the execution server and its corresponding domain name resolution result;
  • the searching module 423 is configured to search for a corresponding domain name resolution result in the execution server according to the requested egress IP address.
  • the device for implementing the domain name resolution system can send the request to the transition server uniformly by the client based on the IP address preset by the transition server, and the transition server forwards the received request to the execution server, and executes the server.
  • the corresponding domain name resolution result is found in the record information and returned to the client. Since the present invention can directly send the request sent by the client based on the preset IP address, the DNS resolution in the prior art is not needed, thereby effectively avoiding the DNS hijacking phenomenon occurring in the DNS resolution process, thereby realizing
  • the purpose of secure access to the destination address is through a normal HTTP request from the client.
  • the device for implementing the domain name resolution system provided by the embodiment of the present invention can effectively prevent the user from obtaining the invalid domain name resolution result of the wrong ISP provider when setting the DNS server inaccurate by configuring the ISP provider information in the execution server.
  • the server may include a processor 610, a communications interface 620, a memory 630, and a communication bus 640, where The 610, the communication interface 620, and the memory 630 complete communication with each other via the communication bus 640.
  • Communication interface 620 can be used for information transfer between the server and the client.
  • the processor 610 can call the logic instructions in the memory 630 to perform the method of: transmitting the client's request to the transition server based on the preset IP address; the transition server forwarding the client's request to the execution server; The request is in the Finding a corresponding domain name resolution result in the line server, and returning the corresponding domain name resolution result to the client.
  • the logic instructions in the memory 630 described above may be implemented in the form of a software functional unit and sold or used as a stand-alone product, and may be stored in a computer readable storage medium.
  • the technical solution of the present invention which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including
  • the instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present invention.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like. .
  • the device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, ie may be located A place, or it can be distributed to multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the embodiment. Those of ordinary skill in the art can understand and implement without deliberate labor.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本发明实施例提供一种域名解析***的实现方法及装置，涉及互联网技术领域，解决了现有技术中用户正常的域名访问请求被恶意劫持的缺陷。本发明实施例的方法包括：过渡服务器接收客户端的请求，所述过渡服务器具有预设IP地址；将所述请求转发到执行服务器中，并接收所述执行服务器返回的域名解析结果；将所述域名解析结果返回给所述客户端。本发明实施例实现了通过正常的HTTP请求即可安全访问目标地址的目的。

Description

域名解析***的实现方法及装置
本申请基于申请号为2015109189615、申请日为2015年12月10日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本发明实施例涉及互联网技术领域，尤其涉及一种域名解析***的实现方法及装置。
背景技术
在使用互联网的过程中，用户需要根据计算机的互联网协议地址(Internet Protocol Address，简称IP)才能进行正常通信。由于IP地址是一个32位的二进制数并且大量的IP地址使用户难以记忆，因此当用户直接使用IP地址进行通信时会非常不便。为了解决上述问题，现有技术中使用了域名解析***(Domain Name System，简称DNS)作为域名和IP地址相互映射的一个分布式数据库，能够使用户更方便的访问互联网，而不用去记住能够被机器直接读取的IP数串。通过主机名，最终得到该主机名对应的IP地址的过程叫做域名解析。
由于DNS的作用是把域名对应到真实的计算机能够识别的IP地址，以便计算机能够进一步通信，传递网址和内容等，因此往往会发生域名劫持(DNS劫持)。DNS劫持是在劫持的网络范围内拦截域名解析的请求，分析请求的域名，把审查范围以外的请求放行，否则返回假的IP地址或者什么都不做使请求失去响应，其效果就是对特定的网络不能反映或访问的是假网址。因此如何使针对自身访问的请求不被恶意劫持成为互联网厂商维护自身服务时亟待解决的问题。
发明内容
本发明实施例提供一种域名解析***的实现方法及装置，用以解决现有 技术中用户正常的域名访问请求被恶意劫持的缺陷，通过正常的HTTP请求即可安全访问目标地址的目的。
依据本发明实施例的第一个方面，本发明实施例提供一种域名解析***的实现方法，所述方法主要用于过渡服务器一侧，包括：
过渡服务器接收客户端的请求，所述过渡服务器具有预设IP地址；
将所述请求转发到执行服务器中，并接收所述执行服务器返回的域名解析结果；
将所述域名解析结果返回给所述客户端。
进一步的，所述过渡服务器接收客户端的请求包括：
过渡服务器接收客户端按照过渡服务器具有的预设IP地址发送的请求，所述预设IP地址为预设虚拟IP地址。
进一步的，所述预设虚拟IP地址具有至少两个；
过渡服务器接收客户端的请求包括：
过渡服务器接收客户端根据业务类型选择的不同的虚拟IP地址发送的请求。
进一步的，将所述请求转发到执行服务器中包括：
所述过渡服务器根据执行服务器的负载状况将所述请求转发到目标执行服务器中；
所述过渡服务器根据所述请求的内容将所述请求转发到相应的执行服务器中。
依据本发明实施例的第二个方面，本发明实施例提供一种域名解析***的实现方法，所述方法主要用于执行服务器一侧，包括：
执行服务器接收过渡服务器转发的客户端的请求；
根据所述请求查找自身配置的对应所述请求的域名解析结果；
将对应所述请求的域名解析结果返回给过渡服务器。
进一步的，根据所述请求查找自身配置的对应所述请求的域名解析结果包括：
获取所述请求的出口IP地址；
遍历所述执行服务器中配置的出口IP地址及其对应的域名解析结果；
根据所述请求的出口IP地址在所述执行服务器中查找对应的域名解析结 果。
依据本发明实施例的第三个方面，本发明实施例提供一种域名解析***的实现装置，所述装置主要位于过渡服务器中，包括：
接收单元，用于接收客户端的请求；
转发单元，用于将所述请求转发到执行服务器中，并接收所述执行服务器返回的域名解析结果；
返回单元，用于将所述域名解析结果返回给所述客户端。
进一步的，所述接收单元用于接收客户端按照过渡服务器具有的预设IP地址发送的请求，所述预设IP地址为预设虚拟IP地址。
进一步的，所述预设虚拟IP地址具有至少两个；所述接收单元用于接收客户端根据业务类型选择的不同的虚拟IP地址发送的请求。
进一步的，所述转发单元用于根据执行服务器的负载状况将所述请求转发到目标执行服务器中；还用于根据所述请求的内容将所述请求转发到相应的执行服务器中。
依据本发明实施例的第四个方面，本发明实施例提供一种域名解析***的实现装置，所述装置主要位于执行服务器中，包括：
接收单元，用于接收过渡服务器转发的客户端的请求；
查找单元，用于根据所述请求查找自身配置的对应所述请求的域名解析结果；
返回单元，用于将对应所述请求的域名解析结果返回给过渡服务器。
进一步的，所述查找单元包括：
获取模块，用于获取所述请求的出口IP地址；
遍历模块，用于遍历所述执行服务器中配置的出口IP地址及其对应的域名解析结果；
查找模块，用于根据所述请求的出口IP地址在所述执行服务器中查找对应的域名解析结果。
依据本发明实施例的第五个方面，本发明实施例提供一种域名解析***的实现装置，所述装置主要位于过渡服务器中，包括：
处理器，和
存储器，被配置为存储所述处理器的可执行指令；
所述的处理器被配置为：
接收客户端的请求；
将所述请求转发到执行服务器中，并接收所述执行服务器返回的域名解析结果；
将所述域名解析结果返回给所述客户端。
依据本发明实施例的第六个方面，本发明实施例提供一种域名解析***的实现装置，所述装置主要位于执行服务器中，包括：
处理器，和
存储器，被配置为存储所述处理器的可执行指令；
所述的处理器被配置为：
接收过渡服务器转发的客户端的请求；
根据所述请求查找自身配置的对应所述请求的域名解析结果；
将对应所述请求的域名解析结果返回给过渡服务器。
本发明实施例提供的域名解析***的实现方法及装置，能够由客户端基于过渡服务器预设的IP地址将请求统一发送到过渡服务器中，由过渡服务器将接收的请求转发到执行服务器中，在执行服务器的记录信息中查找到对应的域名解析结果并返回给客户端。由于本发明能够直接将客户端发送的请求基于预设的IP地址进行发送，因此并不需要进行现有技术中的DNS解析，有效避免了在DNS解析过程中发生的DNS劫持现象，从而实现了通过客户端正常的HTTP请求即可安全访问目标地址的目的。
附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作一简单地介绍，显而易见地，下面描述中的附图是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1为本发明实施例提供的一种域名解析***的实现方法的流程图；
图2为本发明实施例提供的另一种域名解析***的实现方法的流程图；
图3为本发明实施例提供的一种域名解析***的实现装置的组成框图；
图4为本发明实施例提供的另一种域名解析***的实现装置的组成框 图；
图5为本发明实施例提供的另一种域名解析***的实现装置的组成框图；
图6为本发明实施例提供的一种服务器的结构示意图。
具体实施方式
为使本发明实施例的目的、技术方案和优点更加清楚，下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本发明保护的范围。
DNS作为域名和IP地址相互映射的一个分布式数据库，能够使用户方便的访问互联网，而不用去记住能够被机器直接读取的IP数串，通过主机名最终得到该主机名对应的IP地址。由于现有技术中主机名到IP地址的映射有两种方式：1)静态映射，每台设备上都配置主机到IP地址的映射，各设备独立维护自己的映射表，而且只供本设备使用；2)动态映射，建立一套域名解析***(DNS)，只在专门的DNS服务器上配置主机到IP地址的映射，网络上需要使用主机名通信的设备，首先需要到DNS服务器查询主机所对应的IP地址。在解析域名时，可以首先采用静态域名解析的方法，如果静态域名解析不成功，再采用动态域名解析的方法。正是由于存在上述域名解析的过程，因此当客户端发送域名解析请求时，所述请求可能会被恶意劫持，返回给客户端假的IP地址或者不会对请求进行响应。
为了解决上述问题，本发明实施例提供一种域名解析***的实现方法，所述方法主要用于过渡服务器一侧，如图1所示，所述方法包括：
101、过渡服务器接收客户端的请求，所述过渡服务器具有预设IP地址。
在本发明的实施例中，过渡服务器接收客户端按照过渡服务器具有的预设IP地址发送的请求，所述预设IP地址为预设虚拟IP地址。例如，所述预设虚拟IP地址具有至少两个；所述过渡服务器接收客户端的请求包括：所述 过渡服务器接收客户端根据业务类型选择的不同的虚拟IP地址发送的请求。为了避免DNS劫持的发生，本发明实施例可以基于预设的IP地址将客户端的请求发送到过渡服务器中，也就是把客户端发送的HTTP请求直接向预设的IP地址进行发送，将所述请求发送到本发明实施例设置的过渡服务器中。由于此过程不需要经过DNS解析，可以将客户端的请求直接按照预设的IP地址进行发送，因此客户端的请求不会被返回假的IP地址。基于上述原因，本发明实施例可以设置具有IP地址的过渡服务器，由过渡服务器接收客户端的请求。
102、将所述请求转发到执行服务器中，并接收所述执行服务器返回的域名解析结果。
在本发明的实施例中，将所述请求转发到执行服务器中包括：所述过渡服务器根据执行服务器的负载状况将所述请求转发到目标执行服务器中；所述过渡服务器根据所述请求的内容将所述请求转发到相应的执行服务器中。由于在步骤101中需要由过渡服务器接收客户端的请求，因此客户端发送的请求都会被具有预设IP地址的过渡服务器接收。本发明实施例中过渡服务器只需要接收客户端的请求，而不对客户端的域名进行解析，过渡服务器只是负责汇集客户端的请求并根据所述请求以及服务器的负载情况将客户端的请求转发到执行服务器中，所述执行服务器是真正执行客户端请求的服务器。
103、将所述域名解析结果返回给客户端。
其中，所述对应的域名解析结果包括：出口IP地址对应的各个运营商信息及其配置的域名和地理位置信息。由于在本发明实施例中真正执行客户端请求的是执行服务器，因此本发明实施例中过渡服务器还需要接收执行服务器返回的客户端请求对应的域名解析结果，由过渡服务器进行域名解析结果的中转，因此使得客户端看到所述域名解析结果来自于预设的IP地址。
本发明实施例提供的域名解析***的实现方法，能够由客户端基于过渡服务器预设的IP地址将请求统一发送到过渡服务器中，由过渡服务器将接收的请求转发到执行服务器中，在执行服务器的记录信息中查找到对应的域名解析结果并返回给客户端。由于本发明能够直接将客户端发送的请求基于预设的IP地址进行发送，因此并不需要进行现有技术中的DNS解析，有效避免了在DNS解析过程中发生的DNS劫持现象，从而实现了通过客户端正常 的HTTP请求即可安全访问目标地址的目的。
与上述过渡服务器一侧的方法相对应，本发明实施例还提供一种域名解析***的实现方法，所述方法主要用于执行服务器一侧，如图2所示，所述方法包括：
201、执行服务器接收过渡服务器转发的客户端的请求。
由于在本发明实施例中，过渡服务器只是将客户端请求进行收集中转，由执行服务器对客户端请求进行执行，因此需要由执行服务器接收过渡服务器转发的客户端的请求。
202、根据所述请求查找自身配置的对应所述请求的域名解析结果。
由于在本发明实施例中真正执行客户端请求的是执行服务器，因此所述执行服务器中保存有域名解析结果的记录信息，也就是说执行服务器中的信息可以人为进行配置。本发明实施例中的执行服务器只需要根据所述请求的域名在所述执行服务器中查找对应的域名解析结果即可获取到所述请求的所属运营商信息及真实IP地址以及相关的地理位置信息。
203、将对应所述请求的域名解析结果返回给过渡服务器。
由于接收客户端请求的过渡服务器，因此为了使客户端看到所述域名解析结果来自于发送请求使用的预设IP地址，本发明实施例需要由过渡服务器将域名解析结果返回给客户端。但是真正查找到域名解析结果的是执行服务器，因此，需要由执行服务器将域名解析结果首先返回给过渡服务器，由过渡服务器将域名解析结果转发给客户端，从而才能使得客户端看到所述域名解析结果来自于发送请求使用的预设IP地址。
本发明实施例提供的域名解析***的实现方法，能够由客户端基于过渡服务器预设的IP地址将请求统一发送到过渡服务器中，由过渡服务器将接收的请求转发到执行服务器中，在执行服务器的记录信息中查找到对应的域名解析结果并返回给客户端。由于本发明能够直接将客户端发送的请求基于预设的IP地址进行发送，因此并不需要进行现有技术中的DNS解析，有效避免了在DNS解析过程中发生的DNS劫持现象，从而实现了通过客户端正常的HTTP请求即可安全访问目标地址的目的。
为了更好的对上述图1和图2所示方法进行理解，作为对上述实施方式的细化和扩展，本发明实施例将针对上述实施方式进行详细说明。
在本发明实施例中，将客户端发送的HTTP请求基于过渡服务器中预设的IP地址发送到过渡服务器时，可以基于预设的虚拟IP地址将客户端的HTTP请求发送到过渡服务器中。虚拟IP是一个不与特定计算机或计算机中的网络接口卡相连的IP地址，客户端的HTTP请求被发送到这个虚拟IP地址，但是所有的数据还是经过真实的网络接口。在本发明实施例中由于客户端的请求直接被发送到虚拟IP地址对应的过渡服务器中，并不进入现有技术中的DNS服务器进行域名解析，因此能够有效避免发生DNS劫持。
在实际将客户端的请求发送到虚拟IP地址的过程中，预设的虚拟IP地址可以具有多个(至少两个)；当具有多个虚拟IP地址时，可以根据请求的业务类型选择不同的虚拟IP地址将客户端的请求发送到过渡服务器中。例如，当具有两个预设的虚拟IP地址(VIP-1，VIP-2)时，财务部门的请求可以使用VIP-1，行政部门的请求可以使用VIP-2，过渡服务器使用两个预设的虚拟IP地址接收来自客户端的网络请求，并将接收的VIP-1上的请求转发到对应的执行服务器1中，将接收的VIP-2上的请求转发到对应的执行服务器2中。通过不同的虚拟IP地址将多个客户端请求转发到不同的执行服务器中，能够保证执行服务器的负载均衡，避免同一个执行服务器承载大量的请求而造成处理资源紧张。
当通过上述实施方式将客户端的请求基于预设的虚拟IP地址发送到过渡服务器之后，本发明实施例还需要将客户端的请求转发到真正执行客户端请求的执行服务器中。由于本发明实施例中的过渡服务器是接收客户端请求的唯一入口点，过渡服务器需要将大量的客户端请求转发到执行服务器中，若将所有的客户端请求转发到同一个执行服务器中，则可能会造成执行服务器的负载过大，影响执行服务器的运行效率而造成处理出现故障。因此，本发明实施例中的过渡服务器需要按照一定的规则将客户端请求进行转发。具体的，作为一种可选的实施方式，本发明实施例中的过渡服务器可以根据执行服务器的负载状况将客户端的请求转发到目标执行服务器中。在这种实施方式中，包括目标执行服务器在内的多个执行服务器中拥有相同的内容并提供相同的服务，当客户端请求到达时，过渡服务器只需要根据各个执行服务器的负载状况从各个执行服务器中选择一个负载状况正常(低于负载状况预警值)的目标执行服务器，并将所述客户端请求转发到选出的目标执行服务器 中，进一步的，过渡服务器还可以记录这个调度，当所述客户端请求的其他报文到达时，也会被转发到之前选出的目标执行服务器。
作为另一种可选的实施方式，本发明实施例中的过渡服务器还可以根据客户端请求的内容将客户端请求转发到相应的执行服务器中。在这种实施方式中，各个执行服务器可以提供不同的服务，当客户端请求到达时，过渡服务器可以根据请求的内容选择对应的执行服务器执行所述请求。在这种情况下，客户端只知道过渡服务器配置的虚拟IP地址，过渡服务器负责通过客户端请求的内容将客户端请求转发到对应的执行服务器中。例如，当过渡服务器接收到客户端发送的请求序列BBCDBCD时，过渡服务器可以根据请求的内容将所有请求B发送到执行服务器1中，将请求C和请求D发送到执行服务器2中，也就是由执行服务器1处理请求序列BBB，由执行服务器2处理请求序列CDCD。通过这种实施方式，能够避免将大量请求转发到一台执行服务器中造成服务器运行超负荷。
由于在本发明实施例的执行服务器中记录有域名解析结果，也就是各个IP地址对应的运营商信息及其配置的域名和地理位置信息。因此，当过渡服务器将客户端请求转发到执行服务器中之后，需要根据所述请求在执行服务器中查找对应的域名解析结果。在实际查找域名解析结果的过程中，首先需要获取所述请求的出口IP地址，也就是获取客户端的remote address信息。在实际情况下，由于HTTP请求头中携带的IP地址信息能够伪造，因此请求头中携带的IP地址不可信，但是HTTP是利用TCP在两台计算机(通常是服务器和客户端)之间传输信息的协议，因此可以从TCP连接中得到客户端的remote address信息，也就是所述请求的出口IP。当获取到客户端请求的出口IP后，就可以根据客户端请求的出口IP遍历执行服务器中记录的出口IP地址及其对应的域名解析结果。在本发明实施例的执行服务器中配置有IPlib，所述IPlib包含客户端的remote address信息(出口IP地址信息)及其对应的互联网服务提供商(Internet Service Provider，简称ISP)信息和地理位置Geo Location信息。也就是说，执行服务器类似于配置的IP数据库，其中包括出口IP地址段以及对应的信息数据，所述对应的信息数据一般包含有国家、区域(省/州)、城市、街道、经纬度、ISP提供商等信息。在遍历执行服务器中记载的信息的过程中，根据客户端请求的出口IP地址在所述执行 服务器中查找对应的域名解析结果。当在执行服务器中查找到对应的域名解析结果后，就可以通过过渡服务器将对应的域名解析结果进行中转返回给客户端，因此使得客户端看到所述域名解析结果来自于预设的虚拟IP地址。
本发明实施例通过在执行服务器中配置ISP提供商信息，能够有效避免用户在设置DNS服务器不准确时获取到错误ISP提供商的无效的域名解析结果。
作为对上述图1所示方法的实现，本发明实施例提供一种域名解析***的实现装置，所述装置主要位于过渡服务器中，如图3所示，所述装置包括：接收单元31、转发单元32以及返回单元33，其中，
接收单元31，用于接收客户端的请求；
转发单元32，用于将所述请求转发到执行服务器中，并接收所述执行服务器返回的域名解析结果；
返回单元33，用于将所述域名解析结果返回给所述客户端。
进一步的，接收单元31用于接收客户端按照过渡服务器具有的预设IP地址发送的请求，所述预设IP地址为预设虚拟IP地址。
进一步的，所述预设虚拟IP地址具有至少两个；接收单元31用于接收客户端根据业务类型选择的不同的虚拟IP地址发送的请求。
进一步的，转发单元32用于根据执行服务器的负载状况将所述请求转发到目标执行服务器中；还用于根据所述请求的内容将所述请求转发到相应的执行服务器中。
本发明实施例提供的域名解析***的实现装置，能够由客户端基于过渡服务器预设的IP地址将请求统一发送到过渡服务器中，由过渡服务器将接收的请求转发到执行服务器中，在执行服务器的记录信息中查找到对应的域名解析结果并返回给客户端。由于本发明能够直接将客户端发送的请求基于预设的IP地址进行发送，因此并不需要进行现有技术中的DNS解析，有效避免了在DNS解析过程中发生的DNS劫持现象，从而实现了通过客户端正常的HTTP请求即可安全访问目标地址的目的。
作为对上述图2所示方法的实现，本发明实施例提供一种域名解析***的实现装置，所述装置主要位于执行服务器中，如图4所示，所述装置包括：接收单元41、查找单元42以及返回单元43，其中，
接收单元41，用于接收过渡服务器转发的客户端的请求；
查找单元42，用于根据所述请求查找自身配置的对应所述请求的域名解析结果；
返回单元43，用于将对应所述请求的域名解析结果返回给过渡服务器。
进一步的，如图5所示，查找单元42包括：
获取模块421，用于获取所述请求的出口IP地址；
遍历模块422，用于遍历所述执行服务器中配置的出口IP地址及其对应的域名解析结果；
查找模块423，用于根据所述请求的出口IP地址在所述执行服务器中查找对应的域名解析结果。
本发明实施例提供的域名解析***的实现装置，能够由客户端基于过渡服务器预设的IP地址将请求统一发送到过渡服务器中，由过渡服务器将接收的请求转发到执行服务器中，在执行服务器的记录信息中查找到对应的域名解析结果并返回给客户端。由于本发明能够直接将客户端发送的请求基于预设的IP地址进行发送，因此并不需要进行现有技术中的DNS解析，有效避免了在DNS解析过程中发生的DNS劫持现象，从而实现了通过客户端正常的HTTP请求即可安全访问目标地址的目的。
此外，本发明实施例提供的域名解析***的实现装置通过在执行服务器中配置ISP提供商信息，能够有效避免用户在设置DNS服务器不准确时获取到错误ISP提供商的无效的域名解析结果。
针对上述域名解析***的实现装置需要说明的是，凡是在本发明实施例中使用到的各个单元模块的功能都可以通过硬件处理器(hardware processor)来实现。
图6示例了一种服务器的结构示意图，如图6所示，该服务器可以包括：处理器(processor)610、通信接口(Communications Interface)620、存储器(memory)630和通信总线640，其中，处理器610，通信接口620，存储器630通过通信总线640完成相互间的通信。通信接口620可以用于服务器与客户端之间的信息传输。处理器610可以调用存储器630中的逻辑指令，以执行如下方法：基于预设的IP地址将客户端的请求发送到过渡服务器中；所述过渡服务器将所述客户端的请求转发到执行服务器中；根据所述请求在所述执 行服务器中查找对应的域名解析结果；将所述对应的域名解析结果返回给所述客户端。
此外，上述的存储器630中的逻辑指令可以通过软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本发明各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所描述的装置实施例仅仅是示意性的，其中所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。本领域普通技术人员在不付出创造性的劳动的情况下，即可以理解并实施。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到各实施方式可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件。基于这样的理解，上述技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品可以存储在计算机可读存储介质中，如ROM/RAM、磁碟、光盘等，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行各个实施例或者实施例的某些部分所述的方法。
最后应说明的是：以上实施例仅用以说明本发明的技术方案，而非对其限制；尽管参照前述实施例对本发明进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本发明各实施例技术方案的精神和范围。

Claims (14)

  1. 一种域名解析***的实现方法，其特征在于，所述方法包括：
    过渡服务器接收客户端的请求，所述过渡服务器具有预设IP地址；
    将所述请求转发到执行服务器中，并接收所述执行服务器返回的域名解析结果；
    将所述域名解析结果返回给所述客户端。
  2. 根据权利要求1所述的方法，其特征在于，所述过渡服务器接收客户端的请求包括：
    过渡服务器接收客户端按照过渡服务器具有的预设IP地址发送的请求，所述预设IP地址为预设虚拟IP地址。
  3. 根据权利要求2所述的方法，其特征在于，所述预设虚拟IP地址具有至少两个；
    所述过渡服务器接收客户端的请求包括：
    所述过渡服务器接收客户端根据业务类型选择的不同的虚拟IP地址发送的请求。
  4. 根据权利要求1或2或3所述的方法，其特征在于，将所述请求转发到执行服务器中包括：
    所述过渡服务器根据执行服务器的负载状况将所述请求转发到目标执行服务器中；
    所述过渡服务器根据所述请求的内容将所述请求转发到相应的执行服务器中。
  5. 一种域名解析***的实现方法，其特征在于，所述方法包括：
    执行服务器接收过渡服务器转发的客户端的请求；
    根据所述请求查找自身配置的对应所述请求的域名解析结果；
    将对应所述请求的域名解析结果返回给过渡服务器。
  6. 根据权利要求5所述的方法，其特征在于，根据所述请求查找自身配置的对应所述请求的域名解析结果包括：
    获取所述请求的出口IP地址；
    遍历所述执行服务器中配置的出口IP地址及其对应的域名解析结果；
    根据所述请求的出口IP地址在所述执行服务器中查找对应的域名解析结果。
  7. 一种域名解析***的实现装置，其特征在于，所述装置包括：
    接收单元，用于接收客户端的请求；
    转发单元，用于将所述请求转发到执行服务器中，并接收所述执行服务器返回的域名解析结果；
    返回单元，用于将所述域名解析结果返回给所述客户端。
  8. 根据权利要求7所述的装置，其特征在于，所述接收单元用于接收客户端按照过渡服务器具有的预设IP地址发送的请求，所述预设IP地址为预设虚拟IP地址。
  9. 根据权利要求8所述的装置，其特征在于，所述预设虚拟IP地址具有至少两个，所述接收单元用于接收客户端根据业务类型选择的不同的虚拟IP地址发送的请求。
  10. 根据权利要求7或8或9所述的装置，其特征在于，所述转发单元用于根据执行服务器的负载状况将所述请求转发到目标执行服务器中；还用于根据所述请求的内容将所述请求转发到相应的执行服务器中。
  11. 一种域名解析***的实现装置，其特征在于，所述装置包括：
    接收单元，用于接收过渡服务器转发的客户端的请求；
    查找单元，用于根据所述请求查找自身配置的对应所述请求的域名解析结果；
    返回单元，用于将对应所述请求的域名解析结果返回给过渡服务器。
  12. 根据权利要求11所述的装置，其特征在于，所述查找单元包括：
    获取模块，用于获取所述请求的出口IP地址；
    遍历模块，用于遍历所述执行服务器中配置的出口IP地址及其对应的域名解析结果；
    查找模块，用于根据所述请求的出口IP地址在所述执行服务器中查找对应的域名解析结果。
  13. 一种域名解析***的实现装置，其特征在于，所述装置包括：
    处理器，和
    存储器，被配置为存储所述处理器的可执行指令；
    所述的处理器被配置为：
    接收客户端的请求；
    将所述请求转发到执行服务器中，并接收所述执行服务器返回的域名解析结果；
    将所述域名解析结果返回给所述客户端。
  14. 一种域名解析***的实现装置，其特征在于，所述装置包括：
    处理器，和
    存储器，被配置为存储所述处理器的可执行指令；
    所述的处理器被配置为：
    接收过渡服务器转发的客户端的请求；
    根据所述请求查找自身配置的对应所述请求的域名解析结果；
    将对应所述请求的域名解析结果返回给过渡服务器。
PCT/CN2016/089471 2015-12-10 2016-07-08 域名解析***的实现方法及装置 WO2017096888A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US15/246,536 US20170171147A1 (en) 2015-12-10 2016-08-25 Method and electronic device for implementing domain name system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510918961.5 2015-12-10
CN201510918961.5A CN105872119A (zh) 2015-12-10 2015-12-10 域名解析***的实现方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/246,536 Continuation US20170171147A1 (en) 2015-12-10 2016-08-25 Method and electronic device for implementing domain name system

Publications (1)

Publication Number Publication Date
WO2017096888A1 true WO2017096888A1 (zh) 2017-06-15

Family

ID=56624483

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/089471 WO2017096888A1 (zh) 2015-12-10 2016-07-08 域名解析***的实现方法及装置

Country Status (3)

Country Link
US (1) US20170171147A1 (zh)
CN (1) CN105872119A (zh)
WO (1) WO2017096888A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110191203A (zh) * 2019-05-15 2019-08-30 聚好看科技股份有限公司 实现服务器动态访问的方法及电子设备

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108111635B (zh) * 2017-11-06 2021-05-07 北京百悟科技有限公司 业务访问方法和装置
CN109413076B (zh) * 2018-11-06 2022-11-29 北京奇虎科技有限公司 域名解析方法及装置
CN111225003B (zh) * 2018-11-23 2022-12-27 京东科技控股股份有限公司 一种nfs节点配置方法和装置
CN110769080B (zh) * 2019-10-30 2021-12-14 腾讯科技（深圳）有限公司 一种域名解析方法、相关产品及计算机可读存储介质
CN111314500A (zh) * 2020-02-19 2020-06-19 深圳前海微众银行股份有限公司 一种确定访问地址的方法及装置
CN113242210B (zh) * 2021-04-09 2023-03-24 杭州闪电玩网络科技有限公司 一种基于用户等级分流的防DDoS方法和***

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101834911A (zh) * 2010-03-31 2010-09-15 联想网御科技(北京)有限公司 域名劫持的防御方法和网络出口设备
US20130036468A1 (en) * 2011-08-01 2013-02-07 Visicom Media Inc. Anti-phishing domain advisor and method thereof
CN103685584A (zh) * 2012-09-07 2014-03-26 中国科学院计算机网络信息中心 一种基于隧道技术的反域名劫持方法和***
CN103825969A (zh) * 2013-10-29 2014-05-28 电子科技大学 一种基于匿名网络的dns查询方法
CN104468865A (zh) * 2014-12-25 2015-03-25 北京奇虎科技有限公司 域名解析控制、响应方法及相应的装置

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101769222B1 (ko) * 2012-12-26 2017-08-17 후아웨이 테크놀러지 컴퍼니 리미티드 서비스 불법 액세스를 예방하는 방법 및 장치
US9667590B2 (en) * 2013-12-30 2017-05-30 Cellco Partnership APN-based DNS query resolution in wireless data networks
US9935918B2 (en) * 2014-05-30 2018-04-03 Apple Inc. Cloud-based infrastructure for determining reachability of services provided by a server

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101834911A (zh) * 2010-03-31 2010-09-15 联想网御科技(北京)有限公司 域名劫持的防御方法和网络出口设备
US20130036468A1 (en) * 2011-08-01 2013-02-07 Visicom Media Inc. Anti-phishing domain advisor and method thereof
CN103685584A (zh) * 2012-09-07 2014-03-26 中国科学院计算机网络信息中心 一种基于隧道技术的反域名劫持方法和***
CN103825969A (zh) * 2013-10-29 2014-05-28 电子科技大学 一种基于匿名网络的dns查询方法
CN104468865A (zh) * 2014-12-25 2015-03-25 北京奇虎科技有限公司 域名解析控制、响应方法及相应的装置

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110191203A (zh) * 2019-05-15 2019-08-30 聚好看科技股份有限公司 实现服务器动态访问的方法及电子设备
CN110191203B (zh) * 2019-05-15 2022-02-01 聚好看科技股份有限公司 实现服务器动态访问的方法及电子设备

Also Published As

Publication number Publication date
CN105872119A (zh) 2016-08-17
US20170171147A1 (en) 2017-06-15

Similar Documents

Publication Publication Date Title
WO2017096888A1 (zh) 域名解析***的实现方法及装置
US9531664B2 (en) Selecting between domain name system servers of a plurality of networks
JP6656152B2 (ja) コンテンツデリバリーネットワークにおける要求をディスパッチする方法及びシステム
US9866576B2 (en) Rule-based network-threat detection
US9172619B1 (en) Maintaining IP tables
US8458298B2 (en) Failover in an internet location coordinate enhanced domain name system
WO2021120969A1 (zh) 域名解析方法、域名解析服务器及终端设备
JP5167225B2 (ja) １つのファイラー上の複数の仮想ファイラーが重複するネットワークアドレスを有する複数のアドレス空間に参加することを可能にする技術
US9059884B2 (en) Routing of IP traffic directed at domain names using DNS redirection
US7953868B2 (en) Method and system for preventing web crawling detection
US20100174829A1 (en) Apparatus for to provide content to and query a reverse domain name system server
US9497063B2 (en) Maintaining IP tables
JP5932841B2 (ja) 企業ネットワークの外部から分散ファイルシステムへのサイト認識アクセス
CN112565484B (zh) 域名无缝漫游访问局域网设备的方法、***及存储介质
US11843650B2 (en) Two-level cache architecture for live video streaming through hybrid ICN
CN103581361A (zh) 一种域名解析代理方法、设备及***
US11290472B2 (en) Threat intelligence information access via a DNS protocol
US10122630B1 (en) Methods for network traffic presteering and devices thereof
CN116389599A (zh) 网关服务请求的处理、云原生网关***的管理方法及装置
KR101645222B1 (ko) 어드밴스드 도메인 네임 시스템 및 운용 방법
US20240236117A1 (en) Blocking and alerting with domain fronting intelligence
US20240236118A1 (en) Detecting and alerting on domain fronting within a network
WO2024151619A1 (en) Blocking and alerting with domain fronting intelligence
CN111614783A (zh) 域名解析应急响应方法及***
WO2024151637A1 (en) Detecting and alerting on domain fronting within a network

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16872088

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16872088

Country of ref document: EP

Kind code of ref document: A1