WO2020252834A1 - 一种网络请求处理方法及系统、入口及出口网络设备 - Google Patents

一种网络请求处理方法及系统、入口及出口网络设备 Download PDF

Info

Publication number
WO2020252834A1
WO2020252834A1 PCT/CN2019/096168 CN2019096168W WO2020252834A1 WO 2020252834 A1 WO2020252834 A1 WO 2020252834A1 CN 2019096168 W CN2019096168 W CN 2019096168W WO 2020252834 A1 WO2020252834 A1 WO 2020252834A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
dns
namespace
resolution
request
Prior art date
Application number
PCT/CN2019/096168
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 EP19858631.5A priority Critical patent/EP3783870A4/en
Priority to US16/825,932 priority patent/US20200403963A1/en
Publication of WO2020252834A1 publication Critical patent/WO2020252834A1/zh

Links

Images

Classifications

    • 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]

Definitions

  • the embodiments of the present application relate to the field of communication technology, and in particular, to a method and system for processing network requests, and ingress and egress network equipment.
  • Network acceleration service providers often need to provide customized services for multiple enterprise users at the same time.
  • these customized services there are often many common requirements.
  • the resolution request for the same domain name, in the existing technology is targeted at each enterprise user.
  • the management is independent of each other. Even the same requirements will be processed separately to ensure the safe isolation of data.
  • service providers not only a large number of equipment is required to support, but also for the same The processing of demand will consume a lot of resources.
  • the purpose of the embodiments of this application is to provide a network request processing method and system, ingress and egress network equipment, through network-namespace (network-namespace, etns), both virtual network equipment isolated by the same physical machine, realize different
  • the network of enterprise users is isolated, and by setting the DNS network name space, requests from different users are processed uniformly, so that DNS resolution results can be shared, network resources are saved, and the efficiency of DNS resolution is improved.
  • the embodiment of the present application provides a network request processing method, including the following steps: the first LAN network namespace recognizes the received network request, and sends the identified DNS resolution request to the first A DNS network namespace; the first DNS network namespace receives the DNS resolution request, obtains the resolution result, and responds to the resolution result to the first LAN network namespace; where the first LAN network namespace is deployed with the first DNS network namespace On the first network device, the first network device includes at least one first LAN network namespace; at least one LAN network namespace is also deployed on the first network device, and each LAN network namespace sends its own DNS resolution request to the first network device. A DNS network namespace for resolution.
  • the embodiment of the present application also provides an entrance network device on which a LAN network namespace and a DNS network namespace are deployed; wherein the LAN network namespace receives a network request sent by a corresponding local area network through a virtual private network, and responds to The network request is identified, the identified DNS resolution request is sent to the DNS network namespace, and the recognized service request is forwarded based on the local routing strategy; the DNS network namespace receives the DNS resolution request sent by the LAN network namespace, and obtains the resolution result , And respond to the analysis result to the LAN network namespace, where the method of obtaining the analysis result includes forwarding the DNS resolution request to the DNS recursive server or the DNS network namespace on the egress network device.
  • the embodiment of the application also provides an egress network device on which a LAN network namespace and a DNS network namespace are deployed; wherein the DNS network namespace receives a DNS resolution request, and obtains the resolution result corresponding to the DNS resolution request,
  • the analysis result is shared with the LAN network namespace; the LAN network namespace configures a routing strategy for the IP address in the analysis result, and sends the routing strategy to the corresponding LAN network namespace on the ingress network device.
  • An embodiment of the present application also provides a network request processing system.
  • the system includes the above-mentioned ingress network device and egress network device, wherein the ingress network device is communicatively connected with at least one local area network, and receives and processes network requests sent by the local area network.
  • the embodiment of the present application recognizes the received network request through the first local area network name space, so that the DNS resolution request can be recognized; the recognized DNS resolution request is sent to the first DNS network name
  • the first DNS network namespace is used to uniformly process DNS resolution requests, and the obtained resolution results are responded to the first LAN network namespace, which can realize unified management of DNS resolution requests; due to the first LAN network namespace
  • the first DNS network namespace is deployed on the first network device, and the first network device further includes at least one first LAN network namespace.
  • the first DNS network namespace only needs to be resolved when the DNS resolution request is received for the first time, and then the resolution results obtained can be directly shared with all the first LAN network namespaces that send this DNS resolution request, avoiding Repeated resolution of the same DNS resolution request improves the efficiency of DNS resolution and, more importantly, saves equipment resources.
  • each first local area network network namespace receives network requests sent by the corresponding local area network through its virtual dedicated channel.
  • the information exchange between each LAN network namespace and the managed LAN through a virtual dedicated channel can ensure data isolation between different LANs.
  • obtaining the resolution result includes: obtaining the resolution result corresponding to the DNS resolution request from the local cache; if the corresponding resolution result cannot be obtained from the local cache, then forward the DNS resolution request.
  • the analysis result can be obtained directly from the local, which can realize a quick response.
  • the second DNS network namespace sends the received DNS resolution request to the DNS recursive server to obtain the resolution result, and shares the resolution result with the second LAN network namespace on the second network device; the second LAN network name
  • the space configures a routing strategy for the IP address corresponding to the received analysis result, and sends the routing strategy to the corresponding first LAN network namespace on the first network device.
  • the user sends the corresponding IP service request, it can be directly routed and forwarded according to the matched routing strategy, which saves the time of routing for the user and enables the user to Obtain business data faster, which means that the business data of the application requested by the user can be effectively accelerated.
  • the second DNS network namespace determines the application corresponding to the DNS resolution request, and shares the resolution result with the second LAN network namespace containing the application acceleration requirements on the second network device; the second LAN network namespace is the received Configure the routing policy for the IP address corresponding to the analysis result of the, and send the routing policy to the corresponding first LAN network namespace on the first network device. Only the analysis results are shared to the area network namespace with corresponding application acceleration requirements, so that acceleration resources can be more targeted to serve the applications in need.
  • the first local area network network namespace forwards the identified service request based on the local routing policy, where the local routing policy includes the routing policy received from the second local area network network namespace.
  • the identified service request is forwarded based on the routing strategy to avoid real-time matching of the routing strategy, thereby slowing down the service response speed.
  • Fig. 1 is a flowchart of a method for processing a network request according to a first embodiment of the present application
  • FIG. 2 is a flowchart of a method for obtaining analysis results according to a second embodiment of the present application
  • Fig. 3 is a schematic structural diagram of a first network device according to a third embodiment of the present application.
  • FIG. 4 is a schematic structural diagram of a second network device according to a fourth embodiment of the present application.
  • Fig. 5 is a schematic structural diagram of a network request processing system according to a fifth embodiment of the present application.
  • this application proposes a new network architecture, including ingress network equipment and egress network equipment.
  • the ingress network equipment can directly receive network requests from users. How much is deployed on the ingress network equipment?
  • the egress network device is in communication connection with the ingress network device, and the received network request can be sent to the destination device through the Internet.
  • a local area network network corresponding to multiple LAN network namespaces on the ingress network device is deployed one-to-one Namespace is used to realize the network isolation between each user's local area network.
  • a DNS network namespace corresponding to the DNS network namespace on the entrance network device is also deployed to process data collected from the DNS network namespace on the entrance network device DNS resolution request.
  • this solution can uniformly process DNS resolution requests from various LAN network namespaces, so as to realize centralized management of DNS resolution requests from different user LANs, and provide a basis for realizing the sharing of DNS resolution results.
  • the DNS network namespace can save the resolution result, so that next time there are users After initiating a DNS resolution request for the same application, the saved resolution result can be directly returned, thereby realizing the sharing of DNS resolution results.
  • each LAN network namespace that receives user network requests
  • the following embodiments take a LAN network namespace as an example for specific description. It should be noted that in the network architecture proposed in this application, The specific working methods of each LAN network namespace are the same.
  • the first embodiment of the present application relates to a network request processing method.
  • the core of this embodiment is that the first LAN network namespace recognizes the received network request, and sends the identified DNS resolution request to the first DNS network namespace; the first DNS network namespace receives the DNS resolution request and obtains Analyze the result, and respond to the first LAN network namespace; where the first LAN network namespace and the first DNS network namespace are deployed on the first network device, and the first network device includes at least one first local area network
  • the network namespace can realize the unified processing of DNS resolution requests, facilitate the sharing of DNS resolution results, and improve the efficiency of DNS resolution.
  • the implementation details of the network request processing method of this embodiment will be described below in detail. The following content is only provided for ease of understanding and is not necessary for implementing this solution.
  • FIG. 1 The flow chart of the network request processing method in this embodiment is shown in Fig. 1, which will be described in detail below.
  • Step 101 The first local area network network namespace identifies the received network request, and sends the identified DNS resolution request to the first DNS network namespace.
  • enterprise users can be regarded as a local area network, and the enterprise can build a communication network within it to realize network interaction among employees, departments, and external networks.
  • the same Enterprise users can also build multiple local area networks to facilitate cross-regional or cross-departmental network management.
  • a LAN network namespace corresponds to the management of a user LAN, and can establish a virtual private channel with the managed LAN.
  • the first LAN network namespace performs network interaction with the LAN through the virtual private channel to receive network requests from the corresponding LAN. It can ensure the network isolation between different LANs.
  • the network request includes a DNS resolution request and a service request.
  • the identified DNS resolution request is sent to the first DNS network namespace.
  • the DNS resolution request may be sent based on the connection established between the first LAN network namespace and the first DNS network namespace.
  • the first LAN network namespace and the first DNS network namespace are deployed on the first network device, and at least one first LAN network namespace is also deployed on the first network device.
  • the first local area network network namespace sends the respective DNS resolution requests to the first DNS network namespace for resolution.
  • each different enterprise user corresponds to a different local area network
  • each first local area network network namespace receives network requests sent by the corresponding local area network, that is, each first local area network can be used to receive different enterprise users' Network request and processing.
  • the first LAN network namespace corresponding to enterprise user 1 is used to receive the network request of enterprise user 1
  • the first LAN network namespace corresponding to enterprise user 2 is used to receive the network request of enterprise user 2
  • enterprise user 2 corresponds to The first LAN network namespace cannot receive the network request of enterprise user 1 and realizes the isolation of data requests from different enterprise users on the communication link.
  • Each first LAN network namespace sends the DNS resolution request received to the first DNS network namespace processing, in this way, the first DNS network namespace can receive DNS resolution requests from all enterprise users, and can be centrally managed to provide a basis for the sharing of DNS resolution results.
  • Step 102 The first DNS network namespace receives the DNS resolution request, obtains the resolution result, and responds the resolution result to the first LAN network namespace.
  • the first DNS network namespace after the first DNS network namespace receives the DNS resolution request sent by the first LAN network namespace, it can forward the DNS resolution request to the DNS recursive server, receive the resolution result returned by the DNS recursive server, and save it. Before the DNS resolution request is forwarded to the DNS recursive server, it can also be judged whether the resolution result of the DNS resolution request is cached locally. If so, the local resolution result is directly obtained, otherwise the DNS resolution request is forwarded to the DNS recursive server. The DNS network namespace then responds the resolution result to the corresponding first LAN network namespace. When there is an analysis result locally, the analysis result can be directly obtained locally, which can achieve a fast response.
  • the first network device can have multiple LAN network namespaces, and each LAN network namespace sends its own DNS resolution request to the first DNS network namespace for resolution.
  • the following takes two LAN network namespaces as examples Be explained.
  • netns1 and netns2 represent two different LAN network namespaces, which are used to receive network requests from user 1 and user 2, respectively; these two different LAN network namespaces will both send the DNS resolution requests they receive to the first DNS network The namespace is resolved.
  • netns1 When netns1 receives the DNS resolution request for the first application sent by user 1, it sends the DNS resolution request to the first DNS network namespace for resolution; the first DNS network namespace first determines whether the DNS resolution request exists locally If the resolution result exists, the resolution result will be directly obtained locally. If it does not exist, the DNS resolution request will be sent to the DNS recursive server for resolution to obtain the resolution result; after the resolution result is obtained, the first DNS network namespace Respond the obtained analysis result to netns1.
  • the first DNS network namespace can directly return the previously obtained resolution result to netns2.
  • the resolution result returned by the first DNS network namespace is controllable.
  • the resolution result obtained by the first DNS network namespace from the DNS recursive server can include multiple IP addresses, and the first DNS network namespace can directly select one or more of the multiple IP addresses to respond to the request. Therefore, it is possible to optimize the result of the DNS resolution request by setting the first DNS network namespace to select the IP address.
  • the first DNS network namespace can select an IP address from multiple IP addresses as the resolution result It is fed back to the corresponding first LAN network namespace, and the selected IP address may be an address that does not conflict with the IP in the user's local area network, thereby ensuring the validity of the analysis result.
  • the received network request is identified through the first LAN network namespace, and the DNS resolution request can be recognized; by sending the identified DNS resolution request to the first DNS network namespace, The DNS resolution request is processed uniformly by the first DNS network namespace, and the obtained resolution result is responded to the first LAN network namespace, which can realize the unified management of DNS resolution requests; because the first LAN network namespace and the first A DNS network namespace is deployed on the first network device, and the first network device also includes at least one first LAN network namespace.
  • the first The DNS network namespace only needs to be resolved when the DNS resolution request is received for the first time, and then the resolution results obtained can be directly shared with all the first LAN network namespaces that send this DNS resolution request, avoiding the same
  • the repeated resolution of DNS resolution requests improves the efficiency of DNS resolution.
  • the process of sending the DNS resolution request to the DNS recursive server by the first DNS network namespace can specifically include two implementations: directly forwarding the DNS resolution request to the DNS recursive server on the public network, so as The DNS recursive server obtains the resolution result; or forwards the DNS resolution request to the second DNS network namespace on the second network device, and receives the resolution result from the second DNS network namespace.
  • FIG. 2 illustrates the processing flow after the first DNS network namespace forwards the DNS resolution request to the second DNS network namespace in the first embodiment of the present application.
  • Step 201 Forward the DNS resolution request to the second DNS network namespace on the second network device.
  • this embodiment there is a second network device, and this network device is provided with network namespaces corresponding to the network namespaces deployed on the first network device mentioned in the first embodiment. That is, a second LAN network namespace corresponding to the first LAN network namespace and a second DNS network namespace corresponding to the first DNS network namespace are deployed on the second network device, where the first LAN network namespace is The corresponding second local area network network namespace can be communicatively connected, and the first DNS network namespace can be communicatively connected with the second DNS network namespace.
  • the DNS resolution request can be forwarded to the second DNS network namespace, and the second DNS network namespace will perform resolution.
  • the space may forward the DNS resolution request to the DNS recursive server on the public network to obtain the resolution result.
  • the resolution result can also be shared with the second LAN network namespace on the second network device.
  • the network namespace may configure a routing policy for the IP address corresponding to the received analysis result, and send the routing policy to the corresponding first LAN network namespace on the first network device.
  • the first LAN network namespace receives and saves the routing strategy, and when receiving the service request, it can determine the forwarding path based on the locally stored routing strategy, and forward the service request through the determined forwarding path. Specifically, after the first LAN network namespace receives the network request from the corresponding user LAN, it identifies the network request. If it is identified as a service request, it forwards the identified service request based on the local routing strategy.
  • the routing strategy includes the routing strategy received from the second LAN network namespace, and the routing strategy can specifically include forwarding the request to the corresponding second LAN network namespace on the second network device, and the second LAN network namespace performs accelerated processing, Or send the request directly to the origin server, etc., where the accelerated processing of the service request by the second LAN network namespace may include forwarding the service request to a high-quality line based on the routing strategy, or forwarding the service request to the acceleration server.
  • the second DNS network namespace can determine the application that sent the request based on the domain name information in the request, and after obtaining the resolution result, only share the resolution result with the application containing the request.
  • the second LAN network namespace corresponding to the acceleration requirements of the business.
  • the second network device in this embodiment is provided with multiple second LAN network namespaces.
  • netns3 and netns4 represent two different second LANs
  • the network name space corresponds to netns1 and netns2 mentioned in the first embodiment.
  • netns1 in the first network device When netns1 in the first network device receives the DNS resolution request sent by the user's local area network, it sends the DNS resolution request to the first DNS network namespace, and the first DNS network namespace sends the DNS resolution request to the second network.
  • the second DNS network namespace on the device after obtaining the resolution result, the second DNS network namespace will feed back the resolution result to the first DNS network namespace on the first network device and share it with the second LAN network The namespace netns3.
  • the second DNS network namespace can determine the application that sends the DNS resolution request according to the domain name information contained in the DNS resolution request, and then determine whether the users corresponding to the second LAN network namespaces netns3 and netns4 have network acceleration for the application Service, and share this analysis result to the second LAN network namespace netns3 and/or netns4 where the network acceleration service exists.
  • the second DNS network namespace will send the resolution result to netns4.
  • the resolution result After netns4 receives the resolution result, it can be the IP in the resolution result.
  • the address is configured with a routing strategy and shared with netns2 respectively, so that when netns2 receives a service request from the application, it can directly route and forward according to this routing strategy. Only the analysis results are shared to the LAN network namespace of the network acceleration service with subscription applications, so that the acceleration resources can be more targeted to serve the applications in need.
  • the IP address corresponding to the analysis result is matched to accelerate the routing policy, and the routing policy is matched for the IP in the analysis result.
  • the user sends the corresponding IP service request it can be directly based on the matching
  • a good routing strategy for routing and forwarding saves the time of routing for users and enables the user to obtain service data faster, that is, the service data of the application requested by the user can be effectively accelerated.
  • Step 202 Receive a resolution result returned by the second DNS network namespace.
  • the second embodiment of the present application provides an entrance network device.
  • the entrance network device 300 is deployed with a LAN network namespace and a DNS network namespace, where the entrance network device 300 can be deployed Multiple LAN network namespaces.
  • Two examples in the figure are the LAN network namespace netns1 represented by 301 in the figure and the LAN network namespace netns2 represented by 303 in the figure.
  • the entrance network device 300 is also deployed with DNS network namespace, the figure takes the first DNS network namespace represented by 302 as an example; among them, the LAN network namespace netns1 represented by 301 and the LAN network namespace netns2 represented by 303 respectively receive corresponding users through the virtual private network
  • the network request sent by the local area network is identified, the identified DNS resolution request is sent to the first DNS network namespace 302, and the identified service request is forwarded based on the local routing strategy;
  • the first DNS network namespace 302 Receives the DNS resolution request sent by the LAN network namespace, obtains the resolution result, and responds the resolution result to the corresponding LAN network namespace.
  • the method for obtaining the resolution result includes forwarding the DNS resolution request to the DNS recursive server or the export network device DNS network namespace.
  • the ingress network device in this embodiment is the same as the first network device in the foregoing embodiment, and this embodiment can be implemented in cooperation with the first embodiment.
  • the related technical details mentioned in the first embodiment are still valid in this embodiment, and in order to reduce repetition, they will not be repeated here.
  • the related technical details mentioned in this embodiment can also be applied to the first embodiment.
  • the third embodiment of the present application relates to an egress network device.
  • the egress network device 400 is deployed with a LAN network namespace and a DNS network namespace; wherein, the egress network device 400 can deploy multiple LAN network namespaces
  • two examples are taken, namely the LAN network namespace netns3 represented by 401 in the figure and the LAN network namespace netns4 represented by 403 in the figure.
  • the egress network device 400 is also deployed with a DNS network namespace.
  • the second DNS network namespace represented by 402 as an example; where the second DNS network namespace receives DNS resolution requests, obtains the resolution results corresponding to the DNS resolution requests, and shares the resolution results to the LAN network namespaces netns3 and netns4 ; LAN network namespaces netns3 and netns4 configure routing strategies for the IP addresses in the analysis results, and send the routing strategies to the corresponding LAN network namespaces on the ingress network device.
  • the egress network device in this embodiment is the same as the second network device in the foregoing embodiment.
  • the related technical details mentioned in the above embodiments are still valid in this embodiment, and the technical effects that can be achieved can also be achieved in this embodiment. In order to reduce repetition, details are not repeated here. Correspondingly, the related technical details mentioned in this embodiment can also be applied to the above embodiment.
  • the fourth embodiment of the present application relates to a network request processing system. As shown in FIG. 5, it includes an ingress network device 300 according to the second embodiment and an egress network device 400 according to the third embodiment, wherein the ingress network device and at least one Local area network communication connection, receiving and processing network requests sent by the local area network.
  • the LAN network namespace netns1 represented by 301 in the figure on the portal network device 300 and the LAN network namespace netns2 represented by 303 in the figure represent two different LAN network namespaces, respectively To receive network requests from user 1 and user 2, where user 1 and user 2 respectively correspond to local area networks; these two different local area network network namespaces will each send the received DNS resolution requests to the first DNS network namespace 302 Analyze.
  • netns1 After netns1 receives the DNS resolution request for the first application sent by user 1, it sends the DNS resolution request to the first DNS network namespace 302 for resolution; the first DNS network namespace 302 first determines whether the DNS resolution exists locally If the requested resolution result exists, the resolution result is directly obtained locally; if it does not exist, the DNS resolution request is sent to the second DNS network namespace 402 on the egress network device for resolution.
  • the LAN network namespace netns3 represented by 401 in the figure and the LAN network namespace netns4 represented by 403 in the figure represent two different LAN network namespaces, which are respectively different from those in the figure mentioned in the first embodiment.
  • the indicated LAN network namespace netns1 corresponds to the LAN network namespace netns2 indicated by 303 in the figure.
  • netns1 receives the DNS resolution request sent by the user, it forwards the DNS resolution request to the first DNS network namespace 302.
  • a DNS network namespace 302 then sends the DNS resolution request to the second DNS network namespace 402 on the egress network device 400 for resolution.
  • the second DNS network namespace 402 can determine the application that sent the request based on the domain name information in the request, and forward the request to obtain the resolution result; after obtaining the resolution result, The second DNS network namespace 402 will feed back this resolution result to the first DNS network namespace 302 on the ingress network device 300.
  • the second DNS network namespace 402 can determine netns3 and netns3 and netns3 respectively based on the determined application information.
  • netns4 Whether the user corresponding to netns4 is for the acceleration service of the application, if so, share the analysis result to the local area network namespace netns3 and or netns4 that has the corresponding acceleration service, so that netns3 and/or netns4 can be included in the analysis result Configure the corresponding routing strategy for the IP address of the, and share the routing strategy to the corresponding netns1 and/or netns2. If not, do not share.
  • the first DNS network namespace 302 After the first DNS network namespace 302 obtains the resolution result, it can respond with the obtained resolution result to the LAN network namespace netns1 represented by 301 in the figure; when the LAN network namespace netns2 represented by 303 in the figure is received When user 2 sends a DNS resolution request also about the first application, the first DNS network namespace 302 can directly share the previously obtained resolution result to the LAN network namespace netns2 indicated by 303 in the figure.
  • the communication between the corresponding network namespaces on the ingress network device and the egress network device is based on a pre-built dedicated channel, for example, the communication between netns1 and netns3 is based on a dedicated channel.
  • each user’s local area network and the corresponding local area network name space on the entrance network device are also based on dedicated channels for communication. It can be seen that the network data of different user’s local area networks have independent transmission lines, which can realize network data isolation.
  • DNS resolution requests from various LAN network namespaces are processed uniformly through the DNS network namespace, which can not only realize the reuse of DNS resolution results, save network resources, and improve efficiency, and can use the DNS resolution request
  • the process of automatic configuration and distribution of routing policies can also improve the response efficiency of business requests and the classified management of business requests.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请实施例涉及通信技术领域，公开了一种网络请求处理方法及系统、入口及出口网络设备。本申请中，通过第一局域网网络命名空间对接收到的网络请求进行识别，并将识别出的DNS解析请求发送至第一DNS网络命名空间；第一DNS网络命名空间接收DNS解析请求，获取解析结果，并将解析结果响应给第一局域网网络命名空间；其中，第一局域网网络命名空间与第一DNS网络命名空间部署在第一网络设备上，第一网络设备至少包括一个第一局域网网络命名空间；第一网络设备上还部署有至少一个局域网网络命名空间，各个局域网网络命名空间将各自的DNS解析请求发送给第一DNS网络命名空间进行解析。

Description

一种网络请求处理方法及系统、入口及出口网络设备
交叉引用
本申请引用于2019年06月19日递交的名称为“一种网络请求处理方法及系统、入口及出口网络设备”的第201910530338.0号中国专利申请，其通过引用被全部并入本申请。
技术领域
本申请实施例涉及通信技术领域，特别涉及一种网络请求处理方法及系统、入口及出口网络设备。
背景技术
网络加速服务提供商往往需要同时为多个企业用户提供定制化服务，但这些定制化服务中，往往存在很多共通的需求，例如，针对相同域名的解析请求，现有技术中，针对各个企业用户的管理是相互独立的，就算是相同的需求，也会分别进行处理，以保证数据的安全隔离，在这一场景下，对于服务提供商来说，不仅需要大量的设备进行支持，且针对相同的需求处理会耗费大量资源。
发明内容
本申请实施例的目的在于提供一种网络请求处理方法及系统、入口及出口网络设备，通过网络命名空间(network-namespace，etns)，既由同个物理机隔离出来的虚拟网络设备，实现不同企业用户的网络隔离，并通过设置DNS网络命名空间，统一处理来自不同用户的请求，使得DNS解析结果可以实现共享，节省网络资源，提高了DNS解析的效率。
为解决上述技术问题，本申请的实施例提供了一种网络请求处理方法，包括以下步骤：第一局域网网络命名空间对接收到的网络请求进行识别，并将识别出的DNS解析请求发送至第一DNS网络命名空间；第一DNS网络命名空间接收DNS解析请求，获取解析结果，并将解析结果响应给第一局域网网络命名空间；其中，第一局域网网络命名空间与第一DNS网络命名空间部署在第一网络设备上，第一网络设备至少包括一个第一局域网网络命名空间；第一网络设备上还部署有至少一个局域网网络命名空间，各个局域网网络命名空间将各自的 DNS解析请求发送给第一DNS网络命名空间进行解析。
本申请的实施例还提供了一种入口网络设备，入口网络设备上部署有局域网网络命名空间和DNS网络命名空间；其中，局域网网络命名空间通过虚拟专用网络接收对应局域网发出的网络请求，并对网络请求进行识别，将识别出的DNS解析请求发送至DNS网络命名空间，基于本地路由策略将识别出的业务请求进行转发；DNS网络命名空间接收局域网网络命名空间发送的DNS解析请求，获取解析结果，并将解析结果响应给局域网网络命名空间，其中获取解析结果的方式包含将DNS解析请求转发至DNS递归服务器或出口网络设备上的DNS网络命名空间。
本申请的实施例还提供了一种出口网络设备，出口网络设备上部署有局域网网络命名空间和DNS网络命名空间；其中，DNS网络命名空间接收DNS解析请求，获取DNS解析请求对应的解析结果，并将解析结果共享给局域网网络命名空间；局域网网络命名空间为解析结果中的IP地址配置路由策略，并将路由策略发送至入口网络设备上对应的局域网网络命名空间。
本申请的实施例还提供了一种网络请求处理系统，系统包含上述的入口网络设备及出口网络设备，其中入口网络设备与至少一个局域网通信连接，接收并处理局域网发送的网络请求。
本申请实施例相对于现有技术而言，通过第一局域网网络命名空间对接收到的网络请求进行识别，可识别出DNS解析请求；通过将识别出的DNS解析请求发送至第一DNS网络命名空间，由第一DNS网络命名空间来对DNS解析请求进行统一处理，并将获得的解析结果响应给第一局域网网络命名空间，可实现对DNS解析请求的统一管理；由于第一局域网网络命名空间与第一DNS网络命名空间部署在第一网络设备上，而第一网络设备还包括至少一个第一局域网网络命名空间，当多个不同的第一局域网网络命名空间发送相同的DNS解析请求时，第一DNS网络命名空间只需要在第一次接收到这个DNS解析请求时进行解析，之后就能够直接将得到的解析结果共享给所有的发送这个DNS解析请求的第一局域网网络命名空间，避免了同样的DNS解析请求的重复解析，提高了DNS解析的效率，更重要的是，节省了设备资源。
另外，各个第一局域网网络命名空间通过各自的虚拟专用通道接收对应局域网发出的网络请求。各个局域网网络命名空间与所管理的局域网之间通过虚拟专用通道进行信息交互，可保证不同局域网之间的数据隔离。
另外，获取解析结果包含：从本地缓存中获取DNS解析请求对应的解析结果；若无法 从本地缓存中获取对应的解析结果，则对DNS解析请求进行转发。在本地有解析结果时，直接从本地获取这个解析结果，可以实现快速响应。
另外，第二DNS网络命名空间将接收到的DNS解析请求发送至DNS递归服务器，以获取解析结果，并将解析结果共享给第二网络设备上的第二局域网网络命名空间；第二局域网网络命名空间为接收到的解析结果对应的IP地址配置路由策略，并将路由策略发送至第一网络设备上对应的第一局域网网络命名空间。为解析结果对应的IP地址匹配加速路由策略，当用户发送相应的IP的业务请求时，可直接根据匹配好的路由策略进行路由转发，节省了为用户进行路由选路的时间，使用户端能够更快获取到业务数据，即使得用户请求的应用的业务数据能够得到有效的加速。
另外，第二DNS网络命名空间确定DNS解析请求对应的应用程序，将解析结果共享给第二网络设备上的包含应用程序加速需求的第二局域网网络命名空间；第二局域网网络命名空间为接收到的解析结果对应的IP地址配置路由策略，并将路由策略发送至第一网络设备上对应的第一局域网网络命名空间。仅将解析结果共享给有相应的应用程序加速需求的域网网络命名空间，使得加速资源能够更有针对性地服务于有需要的应用。
另外，第一局域网网络命名空间基于本地路由策略对识别出的业务请求进行转发，其中本地路由策略包含从第二局域网网络命名空间接收的路由策略。基于路由策略对识别出的业务请求进行转发，避免实时匹配路由策从而减慢了业务响应速度。
附图说明
一个或多个实施例通过与之对应的附图中的图片进行示例性说明，这些示例性说明并不构成对实施例的限定，附图中具有相同参考数字标号的元件表示为类似的元件，除非有特别申明，附图中的图不构成比例限制。
图1是根据本申请第一实施例提供的网络请求处理方法流程图；
图2是根据本申请第二实施例提供的获取解析结果的方法流程图；
图3是根据本申请第三实施例提供的第一网络设备结构示意图；
图4是根据本申请第四实施例提供的第二网络设备结构示意图；
图5是根据本申请第五实施例提供的网络请求处理系统结构示意图。
具体实施例
为使本申请实施例的目的、技术方案和优点更加清楚，下面将结合附图对本申请的各 实施例进行详细的阐述。然而，本领域的普通技术人员可以理解，在本申请各实施例中，为了使读者更好地理解本申请而提出了许多技术细节。但是，即使没有这些技术细节和基于以下各实施例的种种变化和修改，也可以实现本申请所要求保护的技术方案。以下各个实施例的划分是为了描述方便，不应对本申请的具体实现方式构成任何限定，各个实施例在不矛盾的前提下可以相互结合相互引用。
针对背景技术中提出的问题，本申请提出一种新的网络架构，包括入口网络设备和出口网络设备，其中入口网络设备可直接接收到来自用户的网络请求，在入口网络设备上，部署有多个用于接收用户的网络请求的局域网网络命名空间，其中，每个局域网网络命名空间分别对接到不同的企业用户，即不同的局域网，还部署有DNS网络命名空间，用于处理从各个局域网网络命名空间收集到的DNS解析请求。
出口网络设备与入口网络设备通信连接，可将接收到的网络请求通过互联网发送至目的设备，在出口网络设备上，部署有与入口网络设备上的多个局域网网络命名空间一一对应的局域网网络命名空间，用于实现各个用户局域网之间的网络隔离，还部署有与入口网络设备上的DNS网络命名空间对应的DNS网络命名空间，用于处理从入口网络设备上的DNS网络命名空间收集到的DNS解析请求。
由此可见，本方案可对来自各个局域网网络命名空间的DNS解析请求进行统一处理，以便于实现来自不同用户局域网的DNS解析请求的集中管理，并可为实现DNS解析结果的共享提供基础。
在一个实施中，由于部署有统一的DNS网络命名空间，在获取到一个用户对某个域名的DNS解析结果后，DNS网络命名空间可将这个解析结果保存下来，这样，下次当再有用户发起相同应用的DNS解析请求后，可直接返回保存的解析结果，从而实现DNS解析结果的共享。
为了清楚地体现各个接收用户的网络请求的局域网网络命名空间的具体工作方法，下面实施例中以一个局域网网络命名空间为例进行具体说明，需要说明的是，在本申请提出的网络架构中，各个局域网网络命名空间的具体工作方法相同。
本申请的第一实施例涉及一种网络请求处理方法。本实施例的核心在于第一局域网网络命名空间对接收到的网络请求进行识别，并将识别出的DNS解析请求发送至第一DNS网络命名空间；第一DNS网络命名空间接收DNS解析请求，获取解析结果，并将解析结果响应给第一局域网网络命名空间；其中，第一局域网网络命名空间与第一DNS网络命名空间部署在第一网络设备上，第一网络设备至少还包括一个第一局域网网络命名空间，以实现DNS 解析请求的统一处理，便于实现DNS解析结果的共享，提高了DNS解析的效率。下面对本实施例的网络请求处理方法的实现细节进行具体的说明，以下内容仅为方便理解提供的实现细节，并非实施本方案的必须。
本实施例中的网络请求处理方法流程图如图1所示，下面进行具体说明。
步骤101,第一局域网网络命名空间对接收到的网络请求进行识别，并将识别出的DNS解析请求发送至第一DNS网络命名空间。
具体地说，企业用户可视为一个局域网，企业可在其内部搭建通信网络，以实现各员工之间、各部门之间，以及与外网的网络交互，在本申请的实施例中，同一企业用户也可搭建有多个局域网，以便于实现跨地域、或跨部门的网络管理。
一个局域网网络命名空间对应管理一个用户局域网，并可与所管理的局域网之间搭建虚拟专用通道，第一局域网网络命名空间通过虚拟专用通道与局域网进行网络交互，以接收对应局域网发出的网络请求，可保证不同局域网之间的网络隔离。
在本实施例中，网络请求包括DNS解析请求和业务请求，当第一局域网网络命名空间识别出该网络请求为DNS解析请求后，将识别出的DNS解析请求发送至第一DNS网络命名空间。其中，可基于第一局域网网络命名空间与第一DNS网络命名空间之间建立的连接来进行DNS解析请求的发送。
需要说明的是，在本实施例中，第一局域网网络命名空间与第一DNS网络命名空间部署在第一网络设备上，第一网络设备上还部署有至少一个第一局域网网络命名空间，各个第一局域网网络命名空间将各自的DNS解析请求发送给第一DNS网络命名空间进行解析。
在一个具体的例子中，各个不同的企业用户分别对应不同局域网，而各个第一局域网网络命名空间分别接收对应的局域网发送的网络请求，即，各个第一局域网可用于接收各个不同的企业用户的网络请求并处理。例如，企业用户1对应的第一局域网网络命名空间用于接收企业用户1的网络请求，企业用户2对应的第一局域网网络命名空间用于接收企业用户2的网络请求，而企业用户2对应的第一局域网网络命名空间无法接收企业用户1的网络请求，实现了不同企业用户的数据请求在通信链路上的隔离，各第一局域网网络命名空间将各自接收到的DNS解析请求发送给第一DNS网络命名空间处理，这样，第一DNS网络命名空间就可以接收到所有企业用户的DNS解析请求，并可进行集中管理，以为DNS解析结果的共享提供基础。
步骤102，第一DNS网络命名空间接收DNS解析请求，获取解析结果，并将解析结果响应给第一局域网网络命名空间。
具体地说，第一DNS网络命名空间在接收到第一局域网网络命名空间发送的DNS解析请求后，可将DNS解析请求转发至DNS递归服务器，接收DNS递归服务器返回的解析结果并保存，在将DNS解析请求转发至DNS递归服务器之前，还可先判断本地是否缓存有该DNS解析请求的解析结果，若有，则直接获取本地的解析结果，否则将DNS解析请求转发至DNS递归服务器，第一DNS网络命名空间再将该解析结果响应给对应的第一局域网网络命名空间。当本地有解析结果时，直接从本地获取这个解析结果，可以实现快速响应。
在实施中，第一网络设备中可以有多个局域网网络命名空间，各个局域网网络命名空间将各自的DNS解析请求发送给第一DNS网络命名空间进行解析，以下以两个局域网网络命名空间为例进行说明。
netns1和netns2表示两个不同的局域网网络命名空间，分别用于接收用户1和用户2的网络请求；这两个不同的局域网网络名称空间都会将各自接收到的DNS解析请求发送给第一DNS网络命名空间进行解析。
当netns1接收到用户1发送的关于第一应用的DNS解析请求后，将这个DNS解析请求发送至第一DNS网络命名空间进行解析；第一DNS网络命名空间先判断本地是否存在该DNS解析请求的解析结果，若存在，则直接从本地获取该解析结果，若不存在，则将该DNS解析请求发送给DNS递归服务器进行解析，从而获取解析结果；在获取解析结果后，第一DNS网络命名空间将获取到的解析结果响应给netns1。
当netns2接收到用户2发送的同样关于第一应用的DNS解析请求时，第一DNS网络命名空间就可直接将之前获取的解析结果返回给netns2。
如此一来，针对相同域名的DNS解析请求，第一DNS网络命名空间所返回的解析结果是可控的。具体而言，第一DNS网络命名空间从DNS递归服务器获得的解析结果中可包含多个IP地址，第一DNS网络命名空间可直接从多个IP地址中选择其中一个或多个作响应给请求方，因此，可通过设定第一DNS网络命名空间选择IP地址的方式，优化DNS解析请求的结果，例如，第一DNS网络命名空间可从多个IP地址中选择一个IP地址，作为解析结果反馈给对应的第一局域网网络命名空间，而该被选定的IP地址可以是一个不会与用户局域网中的IP有冲突的地址，从而保证了解析结果的有效性。
本实施例相对现有技术而言，通过第一局域网网络命名空间对接收到的网络请求进行识别，可识别出DNS解析请求；通过将识别出的DNS解析请求发送至第一DNS网络命名空间，由第一DNS网络命名空间来对DNS解析请求进行统一处理，并将获得的解析结果响应给第一局域网网络命名空间，可实现对DNS解析请求的统一管理；由于第一局域网网络命名 空间与第一DNS网络命名空间部署在第一网络设备上，而第一网络设备还包括至少一个第一局域网网络命名空间，当多个不同的第一局域网网络命名空间发送相同的DNS解析请求时，第一DNS网络命名空间只需要在第一次接收到这个DNS解析请求时进行解析，之后就能够直接将得到的解析结果共享给所有的发送这个DNS解析请求的第一局域网网络命名空间，避免了同样的DNS解析请求的重复解析，提高了DNS解析的效率。
在本申请的实施例中，第一DNS网络命名空间将DNS解析请求发送至DNS递归服务器的过程中，可具体包含两种实现：直接将DNS解析请求转发至公网的DNS递归服务器，以从DNS递归服务器获得解析结果；或者将DNS解析请求转发至第二网络设备上的第二DNS网络命名空间，并从第二DNS网络命名空间接收解析结果。
以下将基于图2，对后一过程进行详细说明，图2绘示本申请第一实施例中第一DNS网络命名空间转发DNS解析请求至第二DNS网络命名空间后的处理流程。
步骤201，将DNS解析请求转发至第二网络设备上的第二DNS网络命名空间。
具体地说，在本实施例中，存在一个第二网络设备，这个网络设备上布设有与第一实施例中提到的第一网络设备上部署的各个网络命名空间分别对应的网络命名空间，即，第二网络设备上部署有与第一局域网网络命名空间对应的第二局域网网络命名空间，与第一DNS网络命名空间对应的第二DNS网络命名空间，其中，第一局域网网络命名空间与对应的第二局域网网络命名空间可通信连接，第一DNS网络命名空间与第二DNS网络命名空间可通信连接。
如上文所述，当第一DNS网络命名空间接收到DNS解析请求后，可将该DNS解析请求转发到第二DNS网络命名空间，由第二DNS网络命名空间来进行解析，第二DNS网络命名空间在接收到来自第一DNS网络命名空间的DNS解析请求后，可将DNS解析请求转发至公网的DNS递归服务器，以获得解析结果。
值得注意的是，在本申请的一个实施例中，第二DNS网络命名空间在获取到解析结果后，还可将解析结果共享给第二网络设备上的第二局域网网络命名空间，第二局域网网络命名空间可为接收到的解析结果对应的IP地址配置路由策略，并将路由策略发送至第一网络设备上对应的第一局域网网络命名空间。
第一局域网网络命名空间接收并保存路由策略，并在接收到业务请求时，可基于本地保存的路由策略确定转发路径，并通过确定的转发路径对业务请求进行转发。具体而言，第一局域网网络命名空间在接收到来接对应用户局域网的网络请求后，对网络请求进识别，若识别为业务请求，则基于本地路由策略对识别出的业务请求进行转发，这个本地路由策略包 含从第二局域网网络命名空间接收的路由策略，路由策略具体可包括将请求转发至第二网络设备上对应的第二局域网网络命名空间，并由第二局域网网络命名空间进行加速处理，或者将请求直接发送至源站服务器等，其中第二局域网网络命名空间对业务请求进行加速处理可包含基于路由策略，将业务请求转发至高质量的线路上，或将业务请求转发至加速服务器上。
更进一步的，第二DNS网络命名空间在接收到DNS解析请求后，可基于该请求中的域名信息确定发送该请求的应用程序，在获取解析结果后，仅仅将解析结果共享给包含该应用程序对应的业务的加速需求的第二局域网网络命名空间。
仍然以存在两个局域网网络命名空间为例，本实施例中的第二网络设备上设置有多个第二局域网网络命名空间，以两个为例，netns3和netns4表示两个不同的第二局域网网络命名空间，分别与第一实施例中提到的netns1和netns2对应。
当第一网络设备中的netns1接收到用户局域网发送的DNS解析请求后，将这个DNS解析请求发送给第一DNS网络命名空间，第一DNS网络命名空间再将这个DNS解析请求发送给第二网络设备上的第二DNS网络命名空间；在获取到解析结果后，第二DNS网络命名空间会将这个解析结果反馈给第一网络设备上的第一DNS网络命名空间并共享给与第二局域网网络命名空间netns3。
第二DNS网络命名空间可根据DNS解析请求中所包含的域名信息确定发送该DNS解析请求的应用程序，然后确定出第二局域网网络命名空间netns3和netns4对应的用户是否针对该应用程序存在网络加速业务，并将这个解析结果共享给存在网络加速业务的第二局域网网络命名空间netns3和/或netns4。
本实施例中假设netns4对应的用户有针对该应用程序的业务加速需求，则第二DNS网络命名空间会将解析结果发送给netns4，netns4在接收到解析结果后，可为这个解析结果中的IP地址配置路由策略，并分别共享给netns2，这样，当netns2接收到该应用程序的业务请求时，就可以直接根据这个路由策略进行路由转发。仅将解析结果共享给有订购应用程序的网络加速业务的局域网网络命名空间，使得加速资源能够更有针对性地服务于有需要的应用。
由此看见，在本申请的实施例中，通过为解析结果对应的IP地址匹配加速路由策略，为解析结果中的IP匹配路由策略，当用户发送相应的IP的业务请求时，可直接根据匹配好的路由策略进行路由转发，节省了为用户进行路由选路的时间，使用户端能够更快获取到业务数据，即使得用户请求的应用的业务数据能够得到有效的加速。
步骤202，接收第二DNS网络命名空间返回的解析结果。
上面各种方法的步骤划分，只是为了描述清楚，实现时可以合并为一个步骤或者对某 些步骤进行拆分，分解为多个步骤，只要包括相同的逻辑关系，都在本专利的保护范围内；对算法中或者流程中添加无关紧要的修改或者引入无关紧要的设计，但不改变其算法和流程的核心设计都在该专利的保护范围内。
基于同样的发明构思，本申请第二实施例提供一种入口网络设备，如图3所示，入口网络设备300上部署有局域网网络命名空间和DNS网络命名空间，其中，入口网络设备300可部署多个局域网网络命名空间，图中以两个为例，分别为图中的301所表示的局域网网络命名空间netns1和图中的303所表示的局域网网络命名空间netns2，入口网络设备300还部署有DNS网络命名空间，图中以302所表示的第一DNS网络命名空间为例；其中，301所表示的局域网网络命名空间netns1和303所表示的局域网网络命名空间netns2分别通过虚拟专用网络接收对应用户局域网发出的网络请求，并对网络请求进行识别，将识别出的DNS解析请求发送至第一DNS网络命名空间302，并基于本地路由策略对识别出的业务请求进行转发；第一DNS网络命名空间302收局域网网络命名空间发送的DNS解析请求，获取解析结果，并将解析结果响应给对应的局域网网络命名空间，其中获取解析结果的方式包含将DNS解析请求转发至DNS递归服务器或出口网络设备上的DNS网络命名空间。
不难发现，本实施例中的入口网络设备，与上述实施例中的第一网络设备相同，本实施例可与第一实施例互相配合实施。第一实施例中提到的相关技术细节在本实施例中依然有效，为了减少重复，这里不再赘述。相应地，本实施例中提到的相关技术细节也可应用在第一实施例中。
本申请第三实施例涉及一种出口网络设备，如图4所示，出口网络设备400上部署有局域网网络命名空间和DNS网络命名空间；其中，出口网络设备400可部署多个局域网网络命名空间，图中以两个为例，分别为图中的401所表示的局域网网络命名空间netns3和图中的403所表示的局域网网络命名空间netns4，出口网络设备400还部署有DNS网络命名空间，图中以402所表示的第二DNS网络命名空间为例；其中，第二DNS网络命名空间接收DNS解析请求，获取DNS解析请求对应的解析结果，并将解析结果共享给局域网网络命名空间netns3和netns4；局域网网络命名空间netns3和netns4为解析结果中的IP地址配置路由策略，并将路由策略发送至入口网络设备上对应的局域网网络命名空间。
本实施例中的出口网络设备与上述实施例中的第二网络设备相同。上述实施例中提到的相关技术细节在本实施例中依然有效，所能达到的技术效果在本实施例中也同样可以实现，为了减少重复，这里不再赘述。相应地，本实施例中提到的相关技术细节也可应用在上述实施例中。
本申请第四实施例涉及一种网络请求处理系统，如图5所示，包含如第二实施例的入口网络设备300及如第三实施例的出口网络设备400，其中入口网络设备与至少一个局域网通信连接，接收并处理局域网发送的网络请求。
在一个具体的例子中，入口网络设备300上的图中的301所表示的局域网网络命名空间netns1和图中的303所表示的局域网网络命名空间netns2表示两个不同的局域网网络命名空间，分别用于接收用户1和用户2的网络请求，其中用户1和用户2可分别对应为局域网；这两个不同的局域网网络名称空间都会将各自接收到的DNS解析请求发送给第一DNS网络命名空间302进行解析。
当netns1接收到用户1发送的关于第一应用的DNS解析请求后，将这个DNS解析请求发送至第一DNS网络命名空间302进行解析；第一DNS网络命名空间302先判断本地是否存在该DNS解析请求的解析结果，若存在，则直接从本地获取该解析结果，若不存在，则将该DNS解析请求发送给出口网络设备上的第二DNS网络命名空间402进行解析。
图中的401所表示的局域网网络命名空间netns3和图中的403所表示的局域网网络命名空间netns4表示两个不同的局域网网络命名空间，分别与第一实施例中提到的图中的301所表示的局域网网络命名空间netns1和图中的303所表示的局域网网络命名空间netns2对应，当netns1接收到用户发送的DNS解析请求后，将这个DNS解析请求转发给第一DNS网络命名空间302，第一DNS网络命名空间302再将这个DNS解析请求发送给出口网络设备400上的第二DNS网络命名空间402进行解析。
第二DNS网络命名空间402在接收到DNS解析请求后，可基于该请求中的域名信息确定发送该请求的应用程序，并对该请求进行转发，以获得解析结果；在获取到解析结果后，第二DNS网络命名空间402会将这个解析结果反馈给入口网络设备300上的第一DNS网络命名空间302，同时，第二DNS网络命名空间402可根据确定出的应用程序信息，分别判断netns3和netns4对应的用户是否针对该应用程序存在的加速业务，若有，则将这个解析结果共享给存在对应加速业务的局域网网络命名空间netns3和或netns4，使得netns3和/或netns4可以为这个解析结果中的IP地址配置相应的路由策略，并将该路由策略共享至对应的netns1和/或netns2，若没有，则不进行共享。
第一DNS网络命名空间302在获取解析结果后，可将获取到的解析结果响应给图中的301所表示的局域网网络命名空间netns1；当图中的303所表示的局域网网络命名空间netns2接收到用户2发送的同样关于第一应用的DNS解析请求时，第一DNS网络命名空间302就可直接将之前获取的解析结果共享给图中的303所表示的局域网网络命名空间netns2。
值得注意的是，在上述实施例中，入口网络设备与出口网络设备上相互对应的网络命名空间之间的通信是基于预先搭建的专用通道，例如netns1与netns3之间基于专用的通道进行通信，且如前文所述，各用户局域网与入口网络设备上对应的局域网网络命名空间也是基于专用通道进行通信，由此可见，不同用户局域网的网络数据均有独立的传输线路，可实现网络数据隔离，在此基础上，又通过DNS网络命名空间统一对来自各局域网网络命名空间的DNS解析请求进行处理，不仅可实现DNS解析结果的复用，节省网络资源，提升效率，且可借助该DNS解析请求的处理过程，实现自动配置路由策略并下发的过程，也同样可提升业务请求的响应效率，及对业务请求的分类管理。
本领域的普通技术人员可以理解，上述各实施例是实现本申请的具体实施例，而在实际应用中，可以在形式上和细节上对其作各种改变，而不偏离本申请的精神和范围。

Claims (11)

  1. 一种网络请求处理方法，其中，所述方法包括：
    第一局域网网络命名空间对接收到的网络请求进行识别，并将识别出的DNS解析请求发送至第一DNS网络命名空间；
    所述第一DNS网络命名空间接收所述DNS解析请求，获取解析结果，并将所述解析结果响应给所述第一局域网网络命名空间；
    其中，所述第一局域网网络命名空间与所述第一DNS网络命名空间部署在第一网络设备上，所述第一网络设备上还部署有至少一个第一局域网网络命名空间，各个所述第一局域网网络命名空间将各自的DNS解析请求发送给所述第一DNS网络命名空间进行解析。
  2. 如权利要求1所述的网络请求处理方法，其中，所述第一局域网网络命名空间通过虚拟专用通道接收对应局域网发出的网络请求。
  3. 如权利要求1所述的网络请求处理方法，其中，所述获取解析结果包含将所述DNS解析请求转发至DNS递归服务器，接收所述DNS递归服务器返回的解析结果。
  4. 如权利要求1所述的网络请求处理方法，其中，所述获取解析结果包含：
    将所述DNS解析请求转发至第二网络设备上的第二DNS网络命名空间；
    接收所述第二DNS网络命名空间返回的解析结果。
  5. 如权利要求3或4所述的网络请求处理方法，其中，所述获取解析结果包含：
    从本地缓存中获取所述DNS解析请求对应的解析结果；
    若无法从所述本地缓存中获取对应的解析结果，则对所述DNS解析请求进行转发。
  6. 如权利要求4所述的网络请求处理方法，其中，所述方法包含：
    所述第二DNS网络命名空间将所述解析结果共享给所述第二网络设备上的第二局域网网络命名空间；
    所述第二局域网网络命名空间为接收到的所述解析结果对应的IP地址配置路由策略，并将所述路由策略发送至所述第一网络设备上对应的所述第一局域网网络命名空间。
  7. 如权利要求4所述的网络请求处理方法，其中，所述方法包含：
    所述第二DNS网络命名空间确定所述DNS解析请求对应的应用程序，并将所述解析结果共享给所述第二网络设备上的包含所述应用程序业务加速需求的第二局域网网络命名空间；
    所述第二局域网网络命名空间为接收到的所述解析结果对应的IP地址配置路由策略，并将所述路由策略发送至所述第一网络设备上对应的所述第一局域网网络命名空间。
  8. 如权利要求6或7所述的网络请求处理方法，其中，所述方法包含：
    所述第一局域网网络命名空间基于本地路由策略对识别出的业务请求进行转发，其中所述本地路由策略包含从所述第二局域网网络命名空间接收的所述路由策略。
  9. 一种入口网络设备，其中，所述入口网络设备上部署有局域网网络命名空间和DNS网络命名空间；
    其中，所述局域网网络命名空间通过虚拟专用网络接收对应局域网发出的网络请求，并对所述网络请求进行识别，将识别出的DNS解析请求发送至所述DNS网络命名空间，基于本地路由策略将识别出的业务请求进行转发；
    所述DNS网络命名空间接收所述局域网网络命名空间发送的所述DNS解析请求，获取解析结果，并将所述解析结果响应给所述局域网网络命名空间，其中所述获取解析结果的方式包含将所述DNS解析请求转发至DNS递归服务器或出口网络设备上的DNS网络命名空间。
  10. 一种出口网络设备，其中，所述出口网络设备上部署有局域网网络命名空间和DNS网络命名空间；
    其中，所述DNS网络命名空间接收DNS解析请求，获取所述DNS解析请求对应的解析结果，并将所述解析结果共享给所述局域网网络命名空间；
    所述局域网网络命名空间为所述解析结果中的IP地址配置路由策略，并将所述路由策略发送至入口网络设备上对应的局域网网络命名空间。
  11. 一种网络请求处理系统，其中，所述系统包含如权利要求9所述的入口网络设备及如权利要求10所述的出口网络设备，其中所述入口网络设备与至少一个局域网通信连接，接收并处理所述局域网发送的网络请求。
PCT/CN2019/096168 2019-06-19 2019-07-16 一种网络请求处理方法及系统、入口及出口网络设备 WO2020252834A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP19858631.5A EP3783870A4 (en) 2019-06-19 2019-07-16 NETWORK REQUEST PROCESSING METHOD AND SYSTEM AND INPUT AND OUTPUT NETWORK DEVICES
US16/825,932 US20200403963A1 (en) 2019-06-19 2020-03-20 Method and System for Processing Network Request, Entry Network Device and Exit Network

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910530338.0 2019-06-19
CN201910530338.0A CN110324435B (zh) 2019-06-19 2019-06-19 一种网络请求处理方法及系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/825,932 Continuation US20200403963A1 (en) 2019-06-19 2020-03-20 Method and System for Processing Network Request, Entry Network Device and Exit Network

Publications (1)

Publication Number Publication Date
WO2020252834A1 true WO2020252834A1 (zh) 2020-12-24

Family

ID=68120978

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/096168 WO2020252834A1 (zh) 2019-06-19 2019-07-16 一种网络请求处理方法及系统、入口及出口网络设备

Country Status (3)

Country Link
EP (1) EP3783870A4 (zh)
CN (1) CN110324435B (zh)
WO (1) WO2020252834A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113992759B (zh) * 2021-10-22 2023-12-15 杭州博盾习言科技有限公司 应用于局域网的联合解析装置、方法及电子设备

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105554179A (zh) * 2016-01-08 2016-05-04 中国联合网络通信集团有限公司 局域网内DNS解析方法、系统、Openflow交换机及控制器
CN106067905A (zh) * 2016-02-24 2016-11-02 北京肇煜宏泰信息科技有限公司 一种虚拟网用户访问的方法及系统
EP3273666A1 (en) * 2015-03-19 2018-01-24 ZTE Corporation Method and apparatus for configuring network parameters of local area network

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101572676B (zh) * 2009-06-17 2011-06-29 杭州华三通信技术有限公司 一种数据中心双出口的负载分担方法和设备
CN102025795B (zh) * 2010-01-22 2013-03-06 中国移动通信集团北京有限公司 Dns响应报文处理方法、dns服务器及系统
CN101827136B (zh) * 2010-03-30 2013-04-24 北京网御星云信息技术有限公司 域名系统服务器缓存感染的防御方法和网络出口设备
US9525749B2 (en) * 2010-11-17 2016-12-20 Telefonaktiebolaget L M Ericsson (Publ) DNS server arrangement and method
US8671221B2 (en) * 2010-11-17 2014-03-11 Hola Networks Ltd. Method and system for increasing speed of domain name system resolution within a computing device
US10356038B2 (en) * 2015-12-14 2019-07-16 Microsoft Technology Licensing, Llc Shared multi-tenant domain name system (DNS) server for virtual networks
CN106657432B (zh) * 2016-11-17 2019-10-15 中国移动通信集团江苏有限公司 域名解析方法及装置
CN106657076B (zh) * 2016-12-26 2020-04-07 北京神州绿盟信息安全科技股份有限公司 一种网络命名空间的tcp服务实现方法及装置
CN108650244A (zh) * 2018-04-24 2018-10-12 网宿科技股份有限公司 一种域名解析方法、终端及递归dns服务器
CN109168185B (zh) * 2018-11-12 2021-01-22 杭州安恒信息技术股份有限公司 一种基于网络命名空间的网络扫描方法及装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3273666A1 (en) * 2015-03-19 2018-01-24 ZTE Corporation Method and apparatus for configuring network parameters of local area network
CN105554179A (zh) * 2016-01-08 2016-05-04 中国联合网络通信集团有限公司 局域网内DNS解析方法、系统、Openflow交换机及控制器
CN106067905A (zh) * 2016-02-24 2016-11-02 北京肇煜宏泰信息科技有限公司 一种虚拟网用户访问的方法及系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3783870A4 *

Also Published As

Publication number Publication date
EP3783870A1 (en) 2021-02-24
EP3783870A4 (en) 2021-02-24
CN110324435B (zh) 2021-05-04
CN110324435A (zh) 2019-10-11

Similar Documents

Publication Publication Date Title
US9900263B2 (en) Non-overlay resource access in datacenters using overlay networks
CN103379010B (zh) 一种虚拟网络实现方法及系统
EP2905930B1 (en) Processing method, apparatus and system for multicast
US8166538B2 (en) Unified architecture for remote network access
US20130305344A1 (en) Enterprise network services over distributed clouds
EP2901630B1 (en) Method operating in a fixed access network and user equipments
US11652791B2 (en) Consolidated routing table for extranet virtual networks
EP2922246B1 (en) Method and data center network for cross-service zone communication
CN111884902B (zh) 一种vpn场景网络分流方法及装置
WO2009094928A1 (fr) Procédé et équipement de transmission d'un message basé sur le protocole de tunnel de niveau 2
WO2014005442A1 (zh) 网络业务访问的方法及系统
US10404648B2 (en) Addressing for customer premises LAN expansion
WO2016050109A1 (zh) 一种通信方法、云管理服务器及虚拟交换机
CN101132330A (zh) 一种移动虚拟专用网用户接入系统和方法
EP2214359B1 (en) A policy control method and system for layer two devices
CN103428310A (zh) 基于虚拟ip的非http域名引导系统和方法
WO2020252834A1 (zh) 一种网络请求处理方法及系统、入口及出口网络设备
US20200328975A1 (en) Method and system segregating application traffic in a wide area network
US20200403963A1 (en) Method and System for Processing Network Request, Entry Network Device and Exit Network
WO2020029793A1 (zh) 一种上网行为管理系统、设备及方法
CN112994928B (zh) 一种虚拟机的管理方法、装置及系统
US11218918B2 (en) Fast roaming and uniform policy for wireless clients with distributed hashing
CN110719343B (zh) 业务加速处理方法及系统、入口及出口网络设备
US10812370B2 (en) Unified control plane over MPLS and internet interfaces through BGP
CN115051890A (zh) 一种报文处理方法、系统、装置、电子设备及存储介质

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 2019858631

Country of ref document: EP

Effective date: 20200316

NENP Non-entry into the national phase

Ref country code: DE