CN113691647B - Domain name resolution method and device, electronic equipment and storage medium - Google Patents

Domain name resolution method and device, electronic equipment and storage medium Download PDF

Info

Publication number
CN113691647B
CN113691647B CN202110976814.9A CN202110976814A CN113691647B CN 113691647 B CN113691647 B CN 113691647B CN 202110976814 A CN202110976814 A CN 202110976814A CN 113691647 B CN113691647 B CN 113691647B
Authority
CN
China
Prior art keywords
kubernetes
cluster
address
container
service
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202110976814.9A
Other languages
Chinese (zh)
Other versions
CN113691647A (en
Inventor
胡宝涛
周子江
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Jingdong Technology Information Technology Co Ltd
Original Assignee
Jingdong Technology Information Technology Co Ltd
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 Jingdong Technology Information Technology Co Ltd filed Critical Jingdong Technology Information Technology Co Ltd
Priority to CN202110976814.9A priority Critical patent/CN113691647B/en
Publication of CN113691647A publication Critical patent/CN113691647A/en
Application granted granted Critical
Publication of CN113691647B publication Critical patent/CN113691647B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

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]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • 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/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • 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/14—Session management
    • H04L67/141—Setup of application sessions

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

The invention provides a domain name resolution method, a domain name resolution device, electronic equipment and a storage medium, wherein an IP address corresponding to a target Pod container is acquired based on a dns resolution request of kubernetess device sent by the target Pod container; if the IP address is not the IP address corresponding to any Pod container in the kubernetes cluster, analyzing a service domain name in the kubernetes cluster into an externalIP based on the hybrid plugin, and sending the externalIP to the target Pod container, so that the target Pod container establishes connection with the kubernetess device based on the externalIP. Based on the invention, the use of hardware resources can be reduced, the cost can be reduced, and the operation and maintenance efficiency can be improved.

Description

Domain name resolution method and device, electronic equipment and storage medium
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a domain name resolution method, a domain name resolution device, an electronic device, and a storage medium.
Background
With the deep development of cloud protogenesis, kubernetes are increasingly widely applied, and in order to maintain the reliability of services, users deploy kubernetes into different machine rooms, so that a need exists for parsing services across kubernetes clusters. Wherein the service address of kubernetes has 2 types of IP addresses: cluster IP and external IP. In general, the service domain name can be resolved into a cluster IP by deployment within coredns deployed inside kubernetes, but the cluster IP is a virtual IP that can only be accessed inside kubernetes clusters, and cannot be accessed from outside the clusters.
Therefore, how to provide a domain name resolution method, by resolving the domain name of a service in a Kubernetes-1 cluster into an external IP, so as to achieve that a Pod on a VM and a Kubernetes-2 cluster establishes a connection with the service in the Kubernetes-1 cluster according to the external IP obtained by resolving, which is a problem to be solved currently in need of the present application. Among these, externalIP is a virtual IP that can be accessed from outside the Kubernetes cluster.
Disclosure of Invention
In view of the above, the present invention provides a domain name resolution method, apparatus, electronic device and storage medium, which aims to reduce the use of hardware resources and reduce the cost.
The first aspect of the present invention discloses a domain name resolution method, which is applied to coredns deployed inside kubernetes clusters, wherein hybrid plugins are deployed inside the coredns, and the coredns is connected with kubernetes APIServer in the kubernetes clusters, and the method comprises:
receiving a dns resolution request of kubernetes service sent by a target Pod container;
acquiring an IP address corresponding to the target Pod container based on the dns resolution request of kubernetes service;
judging whether the IP address is an IP address corresponding to any Pod container in the kubernetes cluster;
If the IP address is not the IP address corresponding to any Pod container in the kubernetes cluster, determining that the target Pod container is not the Pod container in the kubernetes cluster, and analyzing the domain name of kubernetes service in the kubernetes cluster into an external IP based on the hybrid plugin;
and sending the external IP to the target Pod container so that the target Pod container establishes connection with the kubernetes service based on the external IP.
Optionally, the method further comprises:
if the IP address is the IP address corresponding to any Pod container in the kuubertenes cluster, determining that the target Pod container is the Pod container in the kuubertenes cluster, and analyzing the kubernetes service domain name in the kuubenes cluster into a cluster IP based on the hybrid plug-in;
and sending the cluster IP to the target Pod container so that the target Pod container establishes connection with kubernetes service based on the cluster IP.
Optionally, before the receiving the dns resolution request of kubernetes service sent by the target Pod container, the method further includes:
the coredns monitors and caches the kubernetes service domain name information, wherein the kubernetes service domain name information comprises a cluster IP and an external IP;
When the network of the kuuberes cluster is configured as an overlay network, reading a target configuration file under a preset naming space, and acquiring network segment information of the overlay network from the target configuration file;
when the network of the kubernetes cluster is configured as an underley network, monitoring and acquiring container information of the kubernetes cluster, wherein the container information comprises an IP address of each Pod container;
and starting a dns monitoring service of the coredns based on the domain name information of the kubernetes service and the network segment information/kubernetes cluster container information of the overlay network, so that when the coredns monitors a dns analysis request of kubernetes service sent by the target Pod, the coredns receives the dns analysis request of kubernetes service sent by the target Pod container.
Optionally, if the network of the kubernetes cluster is configured as the overlay network, the determining whether the IP address is an IP address corresponding to any Pod container in the kubernetes cluster includes:
if the network of the kubernetes cluster is configured as the overlay network, judging whether the IP address belongs to a network segment in the network segment information of the overlay network;
If the IP address does not belong to the network segment in the network segment information of the overlay network, determining that the IP address is not the IP address corresponding to any Pod container in the kubernetes cluster;
and if the IP address belongs to a network segment in the network segment information of the overlay network, determining that the IP address is the IP address corresponding to the Pod container in the kubernetes cluster.
Optionally, if the network of the kubernetes cluster is configured as the underley network, the determining whether the IP address is an IP address corresponding to any Pod container in the kubernetes cluster includes:
if the network of the kubernetes cluster is configured as the underlay network, judging whether the IP address is the IP address in the container information;
if the IP address is not the IP address in the container information, determining that the IP address is not the IP address corresponding to any Pod container in the kubernetes cluster;
and if the IP address is the IP address in the container information, determining that the IP address is the IP address corresponding to any Pod container in the kubernetes cluster.
The second aspect of the present invention discloses a domain name resolution device, applied to coredns deployed inside kubernetes clusters, where hybrid plugins are deployed inside the coredns, and the coredns establishes a connection with kubernetes APIServer in the kubernetes clusters, where the device includes:
The receiving unit is used for receiving the dns resolution request of kubernetes service sent by the target Pod container;
a first obtaining unit, configured to obtain an IP address corresponding to the target Pod container based on the dns resolution request of kubernetes service;
the first judging unit is used for judging whether the IP address is an IP address corresponding to any Pod container in the kubernetes cluster;
and the first parsing unit is used for determining that the target Pod container is not the Pod container in the kubernetes cluster if the IP address is not the IP address corresponding to any Pod container in the kubernetes cluster. Resolving the kubernetes service domain name in the kubernetes cluster into an external IP based on the hybrid plug-in;
and a first sending unit, configured to send the external IP to the target Pod container, so that the target Pod container establishes a connection with the kubernetes service based on the external IP.
Optionally, the apparatus includes:
a second parsing unit, configured to determine that, if the IP address is an IP address corresponding to any one of the Pod containers in the kubernetes cluster, the target Pod container is the Pod container in the kubernetes cluster, and parse, based on the hybrid plugin, the domain name of kubernetes service in the kubernetes cluster into a cluster IP;
And the second sending unit is used for sending the cluster IP to the target Pod container so that the target Pod container establishes connection with kubernetes service based on the cluster IP.
Optionally, before executing the receiving unit, the apparatus further includes:
the monitoring unit is used for monitoring and caching the domain name information of the kubernetes service by the coredns, wherein the domain name information of the kubernetes service comprises clusterIP and externalIP;
the reading unit is used for reading a target configuration file under a preset naming space when the network of the kuubernes cluster is configured as an overlay network, and acquiring network segment information of the overlay network from the target configuration file;
the second obtaining unit is used for monitoring and obtaining container information of the kubernetes cluster when the network of the kubernetes cluster is configured as an underley network, wherein the container information comprises an IP address of each Pod container;
and the starting unit is used for starting the dns monitoring service of the coredns based on the domain name information of the kubernetes service and the network segment information/kubernetes cluster container information of the overlay network so as to enable the coredns to receive the dns analysis request of the kubernetes service sent by the target Pod container when the coredns monitors the dns analysis request of kubernetes service sent by the target Pod.
A third aspect of the present invention discloses an electronic device comprising a processor and a memory for storing program code and data for domain name resolution, the processor being adapted to invoke program instructions in the memory to perform a domain name resolution method as disclosed in the first aspect of the present invention.
The fourth aspect of the present invention discloses a storage medium, where the storage medium includes a storage program, where the program, when executed, controls a device where the storage medium is located to perform a domain name resolution method as disclosed in the first aspect of the present invention.
The invention provides a domain name resolution method, a device, electronic equipment and a storage medium, which are applied to coredns deployed inside kubernetes clusters, wherein a hybrid plug-in is deployed in coredns deployed inside kubernetes clusters, and connection between coredns and kubernetes APIServer in kubernetes clusters is established, so that the coredns obtains an IP address corresponding to a target Pod container based on kubernetes service of a dns resolution request after receiving kubernetes service of a dns resolution request sent by the target Pod container; judging whether the IP address is the IP address corresponding to any Pod container in the kubernetes cluster; under the condition that the IP address is not the IP address corresponding to any Pod container in the kubernetes cluster, determining that the target Pod container is not any Pod container in the kubernetes cluster, and further analyzing the domain name of kuberneteservice in the kubernetes cluster into an external IP based on the hybrid plug-in; and sending the external IP to the target Pod container so that the target Pod container establishes connection with kubernetes service based on the external IP. According to the technical scheme provided by the invention, the hybrid plug-in is deployed in coredns deployed in the kubernetes cluster, so that the kubernetes service domain name in the kubernetes cluster is directly resolved into the external IP based on the hybrid plug-in under the condition that the target Pod is determined not to be any Pod in the kubernetes cluster, one set of external coredns is not required to be deployed in the kubernetes cluster, and the use of hardware resources is reduced and the cost is reduced.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings that are required to be used in the embodiments or the description of the prior art will be briefly described below, and it is obvious that the drawings in the following description are only embodiments of the present invention, and that other drawings can be obtained according to the provided drawings without inventive effort for a person skilled in the art.
FIG. 1 is a schematic diagram of a domain name resolution method in the prior art;
fig. 2 is a schematic structural diagram of a kubernetes cluster according to an embodiment of the present invention;
fig. 3 is a schematic flow chart of a domain name resolution method according to an embodiment of the present invention;
FIG. 4 is a flowchart illustrating another domain name resolution method according to an embodiment of the present invention;
fig. 5 is an exemplary diagram of a domain name resolution method according to an embodiment of the present invention;
fig. 6 is a schematic structural diagram of a domain name resolution device according to an embodiment of the present invention;
fig. 7 is a schematic structural diagram of an electronic device according to an embodiment of the present invention.
Detailed Description
The following description of the embodiments of the present invention will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present invention, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
The term "including" and variations thereof as used herein are intended to be open-ended, i.e., including, but not limited to. The term "based on" is based at least in part on. The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments. Related definitions of other terms will be given in the description below.
It should be noted that the terms "first," "second," and the like in this disclosure are merely used for distinguishing between different devices, modules, or units and not for limiting the order or interdependence of the functions performed by these devices, modules, or units.
It should be noted that references to "one" or "a plurality" in this disclosure are intended to be illustrative rather than limiting, and those of ordinary skill in the art will appreciate that "one or more" is intended to be interpreted as "one or more" unless the context clearly indicates otherwise.
In the prior art, it is possible to deploy one more set of external coredns inside the kubernetes-1 cluster, with coredns external plug-ins deployed inside the external coredns, as shown in fig. 1. The domain name of the service in the Kubernetes-1 cluster can be resolved into an external IP through the coredns external plug-in, so that Pod on the VM and the Kubernetes-2 cluster is realized, and after the domain name resolution of the service in the Kubernetes-1 cluster is completed, connection can be established between the external IP obtained through resolution and the service in the Kubernetes-1 cluster. However, this approach requires one more external coredns to be deployed, which requires not only a large amount of hardware resources, but also a high cost.
Therefore, the invention provides a domain name resolution method, a device, an electronic device and a storage medium, which are characterized in that a hybrid plug-in is deployed in coredns deployed in kubernetes clusters, so that a kubernetes service domain name in kubernetes clusters is resolved into an external IP directly based on the hybrid plug-in under the condition that a target Pod is determined not to be any Pod in kubernetes clusters, and one set of external coredns is not required to be deployed in kubernetes clusters, thereby reducing the use of hardware resources and lowering the cost.
Referring to fig. 2, a schematic structural diagram of a kubenetes cluster provided by an embodiment of the present invention is shown, where the kubenetes cluster includes coredns deployed inside, kubernetes APIServer, and at least one Pod container, where hybrid plug-ins are deployed in coredns deployed inside the kubenetes cluster, and the coredns deployed inside the kubenetes cluster is connected with kubernetes APIServer inside the kubenetes cluster.
Referring to fig. 3, a flow chart of a domain name resolution method provided by the embodiment of the present invention is shown, where the domain name resolution method is applied to coredns deployed inside kubernetes clusters shown in fig. 3, and the domain name resolution method specifically includes the following steps:
S301: and receiving a dns resolution request of kubernetes service sent by the target Pod container.
In the process of specifically executing step S401, after coredns initiates its dns listening service, a dns resolution request of kubernetes service sent by a Pod container (for convenience of distinction, the Pod container that sends the dns resolution request of kubernetes service is referred to as a target Pod container) may be received.
Note that the dns resolution request of kubernetes service carries a connection manner of coredns and the target Pod container, where coredns and the target Pod container may be connected through tcp or udp.
S302: based on the dns resolution request of kubernetes service, the IP address corresponding to the target Pod container is acquired.
In the specific execution of step S302, after the corens receives the dns resolution request of kubernetes service initiated by the target Pod container, the corens may acquire the IP address corresponding to the target Pod container according to the connection mode between the corens and the target Pod container carried in the dns resolution request of kubernetes service.
For example, if the connection mode between coredns carried in the dns resolution request of kubernetes service and the target Pod container is tcp connection, coredns may find the target Pod container through tcp connection, so as to obtain the IP address corresponding to the target Pod container.
S303: judging whether the IP address is the IP address corresponding to any Pod container in the kubernetes cluster; if the IP address is not the IP address corresponding to any Pod container in the kubernetes cluster, executing the step S304; if the IP address is the IP address corresponding to any Pod container in the kubernetes cluster, step S306 is executed.
In the specific execution of step S303, after the corens acquires the IP address corresponding to the target Pod, it may determine whether the target Pod is any Pod in the kubernetes cluster according to the acquired IP address corresponding to the target Pod; under the condition that the IP address corresponding to the target Pod is the IP address corresponding to any Pod in the kubernetes cluster, determining that the target Pod is the Pod in the kubernetes cluster; and under the condition that the IP address corresponding to the target Pod container is not the IP address corresponding to any Pod container in the kubernetes cluster, determining that the target Pod container is not the Pod container in the kubernetes cluster.
S304: and determining that the target Pod container is not a Pod container in the kubernetes cluster, and analyzing the kubernetes service domain name in the kubernetes cluster into an external IP based on the hybrid plugin.
In the process of specifically executing step S304, in the case where it is determined that the target Pod container is not a Pod container in the kubernetes cluster, coredns resolves the domain name of kubernetes service in the kubernetes cluster to an external IP through a hybrid plug-in deployed in advance.
S305: the external IP is sent to the target Pod so that the target Pod establishes a connection with kubernetes service based on the external IP.
In the specific execution of step S305, after the corens resolves the domain name of kubernetes service in the kubernetes cluster into an external IP through the hybrid plugin deployed in advance, the resolved external IP is sent to the target Pod according to the IP address of the target Pod, and the external IP can realize access outside the kubernetes cluster, so after receiving the external IP returned by the corens, the target Pod can establish a connection with kubernetes service according to the external IP, and can access kubernetes service.
S306: and determining the target Pod container as any Pod container in the kubernetes cluster, and analyzing the kubernetes service domain name in the kubernetes cluster into a cluster IP based on the hybrid plugin.
In the process of specifically executing step S306, in the case where it is determined that the target Pod container is a Pod container in the kubernetes cluster, coredns resolves the domain name of kubernetes service in the kubernetes cluster to a cluster IP through a hybrid plug-in deployed in advance.
S307: the cluster IP is sent to the target Pod to cause the target Pod to establish a connection with kubernetes service based on the cluster IP.
In the specific execution of step S307, the coredns, after resolving the domain name of Kubernetes service in the Kubernetes cluster into the cluster IP by the hybrid plugin deployed in advance, sends the resolved cluster IP to the target Pod according to the IP address of the target Pod, and since the cluster IP can implement access in the Kubernetes cluster, the target Pod can establish connection with Kubernetes service according to the cluster IP after receiving the cluster IP returned by the coredns, and can access Kubernetes service.
The invention provides a domain name resolution method, which is applied to coredns deployed inside kubernetes clusters, and is characterized in that a hybrid plug-in is deployed in coredns deployed inside kubernetes clusters, and connection between coredns and kubernetes APIServer in kubernetes clusters is established, so that after the coredns receives a dns resolution request of kubernetes service sent by a target Pod container, the coredns obtains an IP address corresponding to the target Pod container based on the dns resolution request of kubernetes service; judging whether the IP address is the IP address corresponding to any Pod container in the kubernetes cluster; under the condition that the IP address is not the IP address corresponding to any Pod container in the kubernetes cluster, determining that the target Pod container is not any Pod container in the kubernetes cluster, and further analyzing the domain name of kubernetes service in the kubernetes cluster into an external IP based on the hybrid plug-in; the external IP is sent to the target Pod so that the target Pod establishes a connection with kubernetes service based on the external IP. According to the technical scheme provided by the invention, the hybrid plug-in is deployed in the coredns deployed in the kubenets cluster, if the IP address is the IP address corresponding to a certain Pod container in the kubenets cluster, the service domain name in the kubenets cluster is resolved into the cluster IP based on the hybrid plug-in, the target Pod establishes connection based on the cluster IP and kubernetes service, and further, under the condition that the target Pod is determined not to be any Pod container in the kubenets cluster, the kubernetes service domain name in the kubenets cluster is resolved into the external IP directly based on the hybrid plug-in, the target Pod establishes connection based on the external IP and kubernetes service, and one more external coredns is not required to be deployed in the kubenets cluster, so that the use of hardware resources is reduced and the cost is reduced.
Referring to fig. 4, a flow chart of another domain name resolution method provided by the embodiment of the present invention is shown, where the domain name resolution method is applied to coredns deployed inside kubernetes clusters shown in fig. 3, and the domain name resolution method specifically includes the following steps:
s401: the domain name information of kubernetes service is monitored and cached, wherein kubernetes servcice comprises a cluster IP and an external IP.
In the embodiment of the application, coredns are deployed inside the kubernetes cluster, so that the kubernetes service domain name information in the kubernetes cluster can be monitored through the coredns deployed inside the kubernetes cluster, and when kubernetes service domain name information in the kubernetes cluster is monitored, kubernetes service domain name information in the monitored kubernetes cluster is acquired and cached. The kubernetes service domain name information in the kubernetes cluster is service information, and the service information comprises a cluster IP and an external IP.
S402: judging whether the network configuration of the kubernetes cluster is an overlay network or an underley network; if the network of the kubernetes cluster is configured as an overlay network, executing step S403; if the network of the kubernetes cluster is configured as an underley network, step S404 is performed.
In the process of specifically executing step S402, the countns may determine whether the network configuration of the current kubernetes cluster is an overlay network or an underley network, and execute step S403 if it is determined that the network configuration of the kubernetes cluster is an overlay network; in the case where it is determined that the network of the kubernetes cluster is configured as an underley network, step S404 is performed.
It should be noted that the IP address of the Pod container of the kubernetes cluster is determined. For overlay networks, when a Pod container is deployed in a kubernetes cluster, the IP address of the Pod container is determined, such as 10.244. X; for an underley network, an IP address, such as 10 segments, 172 segments, 192.168 segments, etc., is pre-partitioned from the data center for allocation to Pod containers deployed within kubernetes clusters.
It should be noted that, for the overlay network, network segment information corresponding to the overlay network, for example 10.244.0.0/16, is preset, and the set network segment information is stored in a target configuration file under a preset naming space preset in the kubernetes cluster.
S403: and reading the configuration file of the flash under the kube-system naming space, and acquiring the network segment information of the overlay network from the configuration file.
In the specific execution process of step S403, in the case that it is determined that the network of the kubernetes cluster is configured as an overlay network, a target configuration file under a preset namespace is read, and network segment information of the overlay network is obtained from the target configuration file.
It should be noted that the preset namespace may be a kube-system namespace, and the target configuration file may be a configuration file of a plane, that is, in a case that it is determined that a network of a kubenetes cluster is configured as an overlay network, the configuration file of the plane under the kube-system namespace is read, and network segment information of the overlay network is obtained from the configuration file of the plane.
S404: and monitoring and acquiring container information of the kubernetes cluster, wherein the container information comprises an IP address of each Pod container.
In the specific execution process of step S404, in the case that it is determined that the network of the kubernetes cluster is configured as an underley network, the container information of the kubernetes cluster is monitored, and after the container information of the kubernetes cluster is monitored, the container information of the kubernetes cluster is obtained. Wherein the container information of the kubernetes cluster includes an IP address of each Pod container in the kubernetes cluster.
It should be noted that the obtained container information of the kubernetes cluster is also stored.
S405: based on kubernetes service domain name information and segment information of the overlay network/container information of kubernetes clusters, dns listening service of coredns is started.
In the specific execution process of step S405, if the kubernetes cluster network is configured as an overlay network, the corens receives the dns resolution request of kubernetes service sent by the target Pod container when the corens listens to the dns resolution request of kubernetes service sent by the target Pod, based on the obtained kubernetes service domain name information and the overlay network segment information after obtaining kubernetes service domain name information and overlay network segment information.
If the network of the kubernetes cluster is configured as an underley network, after acquiring the domain name information of kubernetes service and the container information of the kubernetes cluster, the coredns starts the dns monitoring service of the coredns based on the acquired domain name information of kubernetes service and the container information of the kubernetes cluster, so that when the coredns monitors the dns analysis request of kubernetes service sent by the target Pod, the coredns receives the dns analysis request of kubernetes service sent by the target Pod container.
S406: and receiving a dns resolution request of kubernetes service sent by the target Pod container.
S407: based on the dns resolution request of kubernetes service, the IP address corresponding to the target Pod container is acquired.
In the process of specifically executing steps S406 to S407, the specific execution process and implementation principle of steps S406 to S407 are the same as the specific execution process and implementation principle of steps S301 to S302 shown in fig. 3 and disclosed in the above embodiment of the present invention, and reference may be made to the corresponding parts in fig. 3 disclosed in the above embodiment of the present invention, and no further description is given here.
S408: judging whether the IP address is the IP address corresponding to any Pod container in the kubernetes cluster; if the IP address is not the IP address corresponding to any Pod container in the kubernetes cluster, executing step S409; if the IP address is the IP address corresponding to any Pod container in the kubernetes cluster, step S411 is executed.
In the embodiment of the application, under the condition that the network configuration of the kuubernes cluster is determined to be an overlay network, judging whether the IP address belongs to a network segment in the network segment information of the overlay network; if the IP address does not belong to the network segment in the network segment information of the overlay network, determining that the IP address is not the IP address corresponding to the Pod container in the kubernetes cluster, and further determining that the target Pod container is not the Pod container in the kubernetes cluster; if the IP address belongs to the network segment in the network segment information of the overlay network, determining that the IP address is the IP address corresponding to the Pod container in the kubernetes cluster, and further determining that the target Pod container is the Pod container in the kubernetes cluster.
S409: and determining that the target Pod container is not a Pod container in the kubernetes cluster. And based on the hybrid plug-in, resolving the kubernetes service domain name in the kubernetes cluster into an external IP.
S410: the external IP is sent to the target Pod so that the target Pod establishes a connection with kubernetes service based on the external IP.
S411: and determining the target Pod container as the Pod container in the kubernetes cluster, and analyzing the kubernetes service domain name in the kubernetes cluster into a cluster IP based on the hybrid plugin.
S412: the cluster IP is sent to the target Pod to cause the target Pod to establish a connection with kubernetes service based on the cluster IP.
In the process of specifically executing steps S409 to S412, the specific execution process and implementation principle of steps S409 to S412 are the same as the specific execution process and implementation principle of steps S304 to S307 shown in fig. 3 and disclosed in the above-mentioned embodiment of the present invention, and reference may be made to the corresponding parts in fig. 3 disclosed in the above-mentioned embodiment of the present invention, and no further description is given here.
In the embodiment of the present application, in the case that the network of the kubernetes cluster is configured as an overlay network, the coredns may start its own dns monitoring service based on the obtained domain name information of kubernetes service and the network segment information of the overlay network, so as to receive the dns analysis request of kubernetes service sent by the target Pod when the coredns monitors the dns analysis request of kubernetes service sent by the target Pod; when the kubernetes cluster network is configured as an underley network, the coredns can start its own dns monitoring service based on the obtained kubernetes service domain name information and kubernetes cluster container information, so that when the coredns monitors the dns analysis request of kubernetes service sent by the target Pod, the coredns receives the dns analysis request of kubernetes service sent by the target Pod container.
For a better understanding of the foregoing, examples are provided below.
For example, as shown in FIG. 5, one Pod container, APIServer (kubernetes APIServer in this application), and coredns of the hybrid plug-in are deployed in the kubernetes-1 cluster (k 8 s-1). kubernetes-2 cluster (k 8 s-2) deploys a Pod container, where the kubernetes service domain name information includes cluster IP:10.10.1.2 and external IP:192.168.0.58, IP address of Pod container deployed in kubernetes-1 cluster (k 8 s-1) is 10.244.0.1; the IP address of the Pod container deployed in the kubernetes-2 cluster (k 8 s-2) was 10.10.0.1. The IP address corresponding to the Pod container corresponding to the VM is 10.10.0.3.
If the kubernetes cluster network is configured as an overlay network, after the coredns starts the dns monitoring service of the coredns according to the domain name information of kubernetes service and the network segment information (10.244.0.0/16) of the overlay network, if the dns analysis request of kubernetes service sent by the target Pod is a dns analysis request of kubernetes service, acquiring the IP address of the target Pod container as (10.10.0.1); according to the acquired IP address and the network segment information of the overlay network, the target Pod container can be determined to be not a Pod container in the kubernetes-1 cluster, and further, based on the hybrid plug-in, the kubernetes service domain name in the kubernetes-1 cluster is resolved into an externalIP:192.168.0.58; and resolving data externalIP according to the IP address of the target Pod container: 192.168.0.58 sends the target Pod container (Pod container in kubernetes-2 cluster (k 8 s-2)) so that the target Pod container receives the externalIP returned by coredns: 192.168.0.58, it is possible according to externalIP:192.168.0.58 establishes a connection with kubernetes service and can access kubernetes service.
If the dns resolution request of kubernetes service sent by the target Pod is received, acquiring the IP address of the target Pod container as (10.244.0.1) according to the received dns resolution request of kubernetes service; according to the acquired IP address and the network segment information of the overlay network, the target Pod container can be determined to be a Pod container in the kubernetes-1 cluster, and further the kubernetes service domain name in the kubernetes-1 cluster is analyzed into a cluster IP based on the hybrid plug-in: 10.10.1.2; and resolving the data cluster IP according to the IP address of the target Pod container: 10.10.1.2 sends the target Pod container (Pod container in kubernetes-1 cluster (k 8 s-1)) so that the target Pod container receives the clusterIP returned by coredns: 10.10.1.2, it is possible according to cluster IP:10.10.1.2 establishes a connection with kubernetes service and can access kubernetes service.
Based on the domain name resolution method disclosed in the embodiment of the present invention, the embodiment of the present invention also correspondingly discloses a domain name resolution device, where the domain name resolution device is applied to coredns deployed inside kubernetes clusters, hybrid plugins are deployed inside coredns, and the coredns is connected with kubernetes APIServer in kubernetes clusters, as shown in fig. 6, the domain name resolution device includes:
A receiving unit 61, configured to receive a dns resolution request of kubernetes service sent by the target Pod container;
a first obtaining unit 62, configured to obtain an IP address corresponding to the target Pod container based on the dns resolution request of kubernetes service;
a first judging unit 63, configured to judge whether the IP address is an IP address corresponding to any Pod container in the kubernetes cluster;
the first parsing unit 64 is configured to determine that the target Pod container is not a Pod container in the kubernetes cluster if the IP address is not an IP address corresponding to any Pod container in the kubernetes cluster. Based on the hybrid plug-in, resolving the kubernetes service domain name in the kubernetes cluster into an external IP;
the first sending unit 65 is configured to send the external IP to the target Pod, so that the target Pod establishes a connection with kubernetes service based on the external IP.
The specific principle and the implementation process of each unit in the domain name resolution device disclosed in the above embodiment of the present invention are the same as those of the domain name resolution method disclosed in the above embodiment of the present invention, and may refer to the corresponding parts in the domain name resolution method disclosed in the above embodiment of the present invention, and will not be described in detail here.
The invention provides a domain name resolution device, which is applied to coredns deployed inside kubernetes clusters, and is used for deploying hybrid plug-ins in the coredns deployed inside kubernetes clusters and establishing connection between the coredns and kubernetes APIServer in the kubernetes clusters so that the coredns can acquire an IP address corresponding to a target Pod container based on the dns resolution request of kubernetes service after receiving a dns resolution request of kubernetes service sent by the target Pod container; judging whether the IP address is the IP address corresponding to any Pod container in the kubernetes cluster; under the condition that the IP address is not the IP address corresponding to any Pod container in the kuubertenes cluster, determining that the target Pod container is not any Pod container in the kuubertenes cluster, and further analyzing the KubernetesService domain name in the kuubenes cluster into an external IP based on the hybrid plug-in; the externalIP is sent to the target Pod to cause the target Pod to establish a connection with kubernetes service based on the externalIP. According to the technical scheme provided by the invention, the hybrid plug-in is deployed in coredns deployed in the kubernetes cluster, so that kubernetes service domain names in the kubernetes cluster are directly resolved into external IPs based on the hybrid plug-in under the condition that the target Pod container is determined not to be any Pod container in the kubernetes cluster, one external coredns is not required to be deployed in the kubernetes cluster, and therefore, the use of hardware resources is reduced and the cost is reduced.
Further, the domain name resolution device provided by the invention further comprises:
the second analyzing unit is configured to determine that the target Pod is a Pod container in the kubernetes cluster if the IP address is an IP address corresponding to any Pod container in the kubernetes cluster, and analyze a domain name of kubernetes service in the kubernetes cluster into a cluster IP based on the hybrid plugin;
and the second sending unit is used for sending the cluster IP to the target Pod container so that the target Pod container establishes connection with kubernetes servicer based on the cluster IP.
Further, the domain name resolution device provided by the invention further comprises:
a monitoring unit, configured to monitor and cache kubernetes service domain name information by coredns, where kubernetes service domain name information includes a cluster IP and an external IP;
the reading unit is used for reading the target configuration file under the preset naming space when the network of the kuuberes cluster is configured as an overlay network, and acquiring network segment information of the overlay network from the target configuration file;
the second obtaining unit is used for monitoring and obtaining container information of the kubernetes cluster when the network of the kubernetes cluster is configured as an underley network, wherein the container information comprises an IP address of each Pod container;
The starting unit is used for starting the dns monitoring service of coredns based on the domain name information of kubernetes service and the network segment information/kubernetes cluster container information of the overlay network, so that when the coredns monitors the dns analysis request of kubernetes service sent by the target Pod, the coredns receives the dns analysis request of kubernetes service sent by the target Pod container.
Optionally, if the network of the kubernetes cluster is configured as an overlay network, the first determining unit includes:
the second judging unit is used for judging whether the IP address belongs to a network segment in the network segment information of the overlay network if the network of the kuuberes cluster is configured as the overlay network;
the first determining unit is configured to determine that the IP address is not an IP address corresponding to any Pod container in the kubernetes cluster if the IP address does not belong to a network segment in the network segment information of the overlay network;
and the second determining unit is used for determining that the IP address is the IP address corresponding to the Pod container in the kubernetes cluster if the IP address belongs to the network segment in the network segment information of the overlay network.
Optionally, if the network of the kubernetes cluster is configured as an underley network, the first determining unit includes:
the third judging unit is used for judging whether the IP address is the IP address in the container information if the network configuration of the kuubernes cluster is an underley network;
The third determining unit is configured to determine that the IP address is not an IP address corresponding to any Pod container in the kubernetes cluster if the IP address is not an IP address in the container information;
and the fourth determining unit is used for determining that the IP address is the IP address corresponding to any Pod container in the kubernetes cluster if the IP address is the IP address in the container information.
An embodiment of the present application provides an electronic device, as shown in fig. 7, where the electronic device includes a processor 701 and a memory 702, where the memory 702 is configured to store program codes and data for domain name resolution, and the processor 701 is configured to invoke program instructions in the memory to execute steps for implementing a domain name resolution method as shown in the foregoing embodiment.
The embodiment of the application provides a storage medium, which comprises a storage program, wherein when the program runs, equipment where the storage medium is controlled to execute the domain name resolution method shown in the embodiment.
In this specification, each embodiment is described in a progressive manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment mainly describes differences from other embodiments. In particular, for a system or system embodiment, since it is substantially similar to a method embodiment, the description is relatively simple, with reference to the description of the method embodiment being made in part. The systems and system embodiments described above are merely illustrative, wherein elements illustrated as separate elements may or may not be physically separate, and elements shown as elements may or may not be physical elements, may be located in one place, or may be distributed over a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment. Those of ordinary skill in the art will understand and implement the present invention without undue burden.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative elements and steps are described above generally in terms of functionality in order to clearly illustrate the interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
The foregoing is merely a preferred embodiment of the present invention and it should be noted that modifications and adaptations to those skilled in the art may be made without departing from the principles of the present invention, which are intended to be comprehended within the scope of the present invention.

Claims (10)

1. A domain name resolution method, which is applied to coredns deployed inside kubernetes clusters, wherein hybrid plugins are deployed inside the coredns, and the coredns establishes a connection with kubernetes APIServer in the kubernetes clusters, the method comprising:
receiving a dns resolution request of kubernetes service sent by a target Pod container;
acquiring an IP address corresponding to the target Pod container based on the dns resolution request of kubernetes service;
judging whether the IP address is an IP address corresponding to any Pod container in the kubernetes cluster;
if the IP address is not the IP address corresponding to any Pod container in the kubernetes cluster, determining that the target Pod container is not the Pod container in the kubernetes cluster, and analyzing the domain name of kubernetes service in the kubernetes cluster into an external IP based on the hybrid plugin;
And sending the external IP to the target Pod container so that the target Pod container establishes connection with the kubernetes service based on the external IP.
2. The method according to claim 1, wherein the method further comprises:
if the IP address is the IP address corresponding to any Pod container in the kuubertenes cluster, determining that the target Pod container is the Pod container in the kuubertenes cluster, and analyzing the kubernetes service domain name in the kuubenes cluster into a cluster IP based on the hybrid plug-in;
and sending the cluster IP to the target Pod container so that the target Pod container establishes connection with kubernetes service based on the cluster IP.
3. The method of claim 1, wherein prior to receiving the dns resolution request of kubernetes service sent by the target Pod container, the method further comprises:
the coredns monitors and caches the kubernetes service domain name information, wherein the kubernetes service domain name information comprises a cluster IP and an external IP;
when the network of the kuuberes cluster is configured as an overlay network, reading a target configuration file under a preset naming space, and acquiring network segment information of the overlay network from the target configuration file;
When the network of the kubernetes cluster is configured as an underley network, monitoring and acquiring container information of the kubernetes cluster, wherein the container information comprises an IP address of each Pod container;
and starting a dns monitoring service of the coredns based on the domain name information of the kubernetes service and the network segment information/kubernetes cluster container information of the overlay network, so that when the coredns monitors a dns analysis request of kubernetes service sent by the target Pod, the coredns receives the dns analysis request of kubernetes service sent by the target Pod container.
4. The method of claim 3, wherein if the network of the kubernetes cluster is configured as the overlay network, the determining whether the IP address is an IP address corresponding to any Pod container in the kubernetes cluster includes:
if the network of the kubernetes cluster is configured as the overlay network, judging whether the IP address belongs to a network segment in the network segment information of the overlay network;
if the IP address does not belong to the network segment in the network segment information of the overlay network, determining that the IP address is not the IP address corresponding to any Pod container in the kubernetes cluster;
And if the IP address belongs to a network segment in the network segment information of the overlay network, determining that the IP address is the IP address corresponding to the Pod container in the kubernetes cluster.
5. The method of claim 3, wherein if the network of the kubernetes cluster is configured as the underley network, the determining whether the IP address is an IP address corresponding to any Pod container in the kubernetes cluster includes:
if the network of the kubernetes cluster is configured as the underlay network, judging whether the IP address is the IP address in the container information;
if the IP address is not the IP address in the container information, determining that the IP address is not the IP address corresponding to any Pod container in the kubernetes cluster;
and if the IP address is the IP address in the container information, determining that the IP address is the IP address corresponding to any Pod container in the kubernetes cluster.
6. A domain name resolution device, characterized by being applied to coredns deployed inside kubernetes clusters, wherein hybrid plug-ins are deployed inside the coredns, and the coredns establishes a connection with kubernetes APIServer in the kubernetes clusters, the device comprising:
The receiving unit is used for receiving the dns resolution request of kubernetes service sent by the target Pod container;
a first obtaining unit, configured to obtain an IP address corresponding to the target Pod container based on the dns resolution request of kubernetes service;
the first judging unit is used for judging whether the IP address is an IP address corresponding to any Pod container in the kubernetes cluster;
a first resolving unit, configured to determine that the target Pod container is not the Pod container in the kubernetes cluster if the IP address is not the IP address corresponding to any of the Pod containers in the kubernetes cluster, and resolve, based on the hybrid plugin, the domain name of the kubernetes service in the kubernetes cluster into an external IP;
and a first sending unit, configured to send the external IP to the target Pod container, so that the target Pod container establishes a connection with the kubernetes service based on the external IP.
7. The apparatus of claim 6, wherein the apparatus comprises:
a second parsing unit, configured to determine that, if the IP address is an IP address corresponding to any one of the Pod containers in the kubernetes cluster, the target Pod container is the Pod container in the kubernetes cluster, and parse, based on the hybrid plugin, the domain name of kubernetes service in the kubernetes cluster into clusterIP;
And the second sending unit is used for sending the clusterIP to the target Pod container so that the target Pod container establishes connection with kubernetes service based on the clusterIP.
8. The apparatus of claim 6, wherein prior to executing the receiving unit, the apparatus further comprises:
the monitoring unit is used for monitoring and caching the domain name information of the kubernetes service by the coredns, wherein the domain name information of the kubernetes service comprises clusterIP and externalIP;
the reading unit is used for reading a target configuration file under a preset naming space when the network of the kuubernes cluster is configured as an overlay network, and acquiring network segment information of the overlay network from the target configuration file;
the second obtaining unit is used for monitoring and obtaining container information of the kubernetes cluster when the network of the kubernetes cluster is configured as an underley network, wherein the container information comprises an IP address of each Pod container;
and the starting unit is used for starting the dns monitoring service of the coredns based on the domain name information of the kubernetes service and the network segment information/kubernetes cluster container information of the overlay network so as to enable the coredns to receive the dns analysis request of the kubernetes service sent by the target Pod container when the coredns monitors the dns analysis request of kubernetes service sent by the target Pod.
9. An electronic device comprising a processor and a memory, the memory for storing program code and data for domain name resolution, the processor for invoking program instructions in the memory to perform the domain name resolution method of any of claims 1-5.
10. A storage medium comprising a stored program, wherein the program, when run, controls a device in which the storage medium resides to perform the domain name resolution method according to any one of claims 1-5.
CN202110976814.9A 2021-08-24 2021-08-24 Domain name resolution method and device, electronic equipment and storage medium Active CN113691647B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110976814.9A CN113691647B (en) 2021-08-24 2021-08-24 Domain name resolution method and device, electronic equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110976814.9A CN113691647B (en) 2021-08-24 2021-08-24 Domain name resolution method and device, electronic equipment and storage medium

Publications (2)

Publication Number Publication Date
CN113691647A CN113691647A (en) 2021-11-23
CN113691647B true CN113691647B (en) 2024-01-16

Family

ID=78582073

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110976814.9A Active CN113691647B (en) 2021-08-24 2021-08-24 Domain name resolution method and device, electronic equipment and storage medium

Country Status (1)

Country Link
CN (1) CN113691647B (en)

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107707688A (en) * 2017-10-19 2018-02-16 杭州数梦工场科技有限公司 A kind of method and device of kubernetes clusters parsing host host name
CN110086895A (en) * 2019-04-11 2019-08-02 天津字节跳动科技有限公司 Domain name analytic method, device, medium and electronic equipment
CN110611697A (en) * 2019-08-02 2019-12-24 杭州网银互联科技股份有限公司 Network architecture and network deployment method of hybrid cloud
CN111800458A (en) * 2020-05-22 2020-10-20 浙商银行股份有限公司 Dynamic load balancing method and system for Kubernetes container cloud platform
CN111866206A (en) * 2020-06-24 2020-10-30 北京金山云网络技术有限公司 Distributed domain name resolution method, device and equipment
WO2021017279A1 (en) * 2019-07-30 2021-02-04 平安科技（深圳）有限公司 Cluster security management method and apparatus based on kubernetes and network domain, and storage medium
CN112671860A (en) * 2020-12-15 2021-04-16 杭州溪塔科技有限公司 Service access method, system, electronic device and medium for kubernets cluster

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3270573B1 (en) * 2016-07-13 2020-04-01 DNSthingy Inc. Method and router to permit or block internet protocol (ip) connectivity based on originating domain name server (dns) requests
CN106657431B (en) * 2016-11-17 2019-11-19 腾讯科技（深圳）有限公司 A kind of method, server, terminal and the system of business platform address resolution

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107707688A (en) * 2017-10-19 2018-02-16 杭州数梦工场科技有限公司 A kind of method and device of kubernetes clusters parsing host host name
CN110086895A (en) * 2019-04-11 2019-08-02 天津字节跳动科技有限公司 Domain name analytic method, device, medium and electronic equipment
WO2021017279A1 (en) * 2019-07-30 2021-02-04 平安科技（深圳）有限公司 Cluster security management method and apparatus based on kubernetes and network domain, and storage medium
CN110611697A (en) * 2019-08-02 2019-12-24 杭州网银互联科技股份有限公司 Network architecture and network deployment method of hybrid cloud
CN111800458A (en) * 2020-05-22 2020-10-20 浙商银行股份有限公司 Dynamic load balancing method and system for Kubernetes container cloud platform
CN111866206A (en) * 2020-06-24 2020-10-30 北京金山云网络技术有限公司 Distributed domain name resolution method, device and equipment
CN112671860A (en) * 2020-12-15 2021-04-16 杭州溪塔科技有限公司 Service access method, system, electronic device and medium for kubernets cluster

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
基于云平台的分布式高性能网络爬虫的研究与设计;石恩名;肖晓军;卢宇;;电信科学(08);全文 *

Also Published As

Publication number Publication date
CN113691647A (en) 2021-11-23

Similar Documents

Publication Publication Date Title
CN111431740B (en) Data transmission method, device, equipment and computer readable storage medium
CN112989330B (en) Container intrusion detection method, device, electronic equipment and storage medium
CN107547565B (en) Network access authentication method and device
CN110650112B (en) Universal authentication method and device and cloud service network system
CN103442026A (en) Application program processing method, device and system
CN110968356B (en) Method and device for acquiring configuration information
CN114205342B (en) Service debugging routing method, electronic equipment and medium
CN107566518B (en) Method and device for managing equipment information in file installation process
CN111273924A (en) Software updating method and device
CN113923008B (en) Malicious website interception method, device, equipment and storage medium
CN112468545A (en) Cloud host creation method, device, system, equipment and readable storage medium
CN106790077B (en) Method and device for detecting DNS full-flow hijacking risk
CN114979286A (en) Access control method, device and equipment for container service and computer storage medium
CN112162873B (en) Remote calling method, electronic device and storage medium
CN113014573B (en) Monitoring method, system, electronic device and storage medium of DNS (Domain name Server)
CN113691647B (en) Domain name resolution method and device, electronic equipment and storage medium
CN106790071B (en) Method and device for detecting DNS full-flow hijacking risk
CN108011801B (en) Data transmission method, equipment, device and system
CN112104698A (en) Method for accessing vehicle-mounted terminal to gateway, related equipment and medium
CN115801653A (en) Network detection method, system, electronic device and readable storage medium
CN113347239B (en) Communication request processing method, device, system, electronic equipment and storage medium
CN114585055B (en) Vehicle-mounted WiFi access method, vehicle controller, cloud server and mobile terminal
CN112702441B (en) Container-based access data processing method, device, system and storage medium
CN111736944A (en) Docker container positioning method and device based on Kubernetes
CN112367415B (en) Generation method and device of attribute information, electronic equipment and computer readable medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant