CN106911508B - DNS configuration recovery method and device - Google Patents
DNS configuration recovery method and device Download PDFInfo
- Publication number
- CN106911508B CN106911508B CN201710114917.8A CN201710114917A CN106911508B CN 106911508 B CN106911508 B CN 106911508B CN 201710114917 A CN201710114917 A CN 201710114917A CN 106911508 B CN106911508 B CN 106911508B
- Authority
- CN
- China
- Prior art keywords
- dns server
- dns
- vpn
- configuration
- server information
- 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
Links
- 238000000034 method Methods 0.000 title claims abstract description 25
- 238000011084 recovery Methods 0.000 title description 14
- 238000001514 detection method Methods 0.000 claims description 7
- 238000010586 diagram Methods 0.000 description 4
- 230000002159 abnormal effect Effects 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 230000005856 abnormality Effects 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 238000004590 computer program Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 239000002699 waste material Substances 0.000 description 1
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]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/084—Configuration by using pre-existing information, e.g. using templates or copying from other elements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0866—Checking the configuration
-
- 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/09—Mapping addresses
- H04L61/10—Mapping addresses of different types
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The application provides a method and a device for recovering DNS configuration, comprising the following steps: detecting whether the equipment is accessed to a Virtual Private Network (VPN) or not according to a preset time period; if the device is not accessed to the VPN, detecting whether first domain name system DNS server information is stored locally; the first DNS server is a DNS server used when not accessing VPN; if the first DNS server information is locally stored, updating the current DNS configuration from second DNS server information to the first DNS server information; the second DNS server is a DNS server used when accessing the VPN. The technical scheme of the application can ensure normal network connection of the network equipment after the network equipment abnormally exits the VPN.
Description
Technical Field
The present application relates to the field of communications technologies, and in particular, to a method and an apparatus for recovering DNS configuration.
Background
Generally, when a VPN (Virtual Private Network) function is used, an intranet Domain Name resource may be configured for a Network device, and an intranet DNS (Domain Name System) server address may be configured for a local Network card in the Network device. After the network device accesses the VPN, the intranet DNS server may resolve the intranet domain name resource into an intranet IP address, and the network device may successfully access the intranet resource through the intranet IP address. After the network device normally exits the VPN, the DNS configuration of the local network card may be restored to the DNS configuration when the VPN is not accessed, so as to ensure subsequent normal network connection of the network device. However, if the network device accesses the VPN, the VPN exits abnormally, the device is powered off, the device is restarted forcibly, and the like, the DNS configuration of the local network card is still the DNS configuration when the network device accesses the VPN, which may cause subsequent network connection abnormality of the network device.
Disclosure of Invention
In view of this, the present application provides a method and an apparatus for recovering DNS configuration to solve the problem of network connection abnormality in the related art.
Specifically, the method is realized through the following technical scheme:
in a first aspect, the present application provides a method for recovering a DNS configuration, where the method includes:
detecting whether the equipment is accessed to a Virtual Private Network (VPN) or not according to a preset time period;
if the device is not accessed to the VPN, detecting whether first domain name system DNS server information is stored locally; the first DNS server is a DNS server used when not accessing VPN;
if the first DNS server information is locally stored, updating the current DNS configuration from second DNS server information to the first DNS server information; the second DNS server is a DNS server used when accessing the VPN.
In a second aspect, the present application provides a DNS configuration recovery apparatus, including:
the first detection unit is used for detecting whether the equipment is accessed to the virtual private network VPN or not according to a preset time period;
the second detection unit is used for detecting whether the first domain name system DNS server information is stored locally or not when the device is not accessed to the VPN; the first DNS server is a DNS server used when not accessing VPN;
a first updating unit, configured to update a current DNS configuration from second DNS server information to the first DNS server information if the first DNS server information is locally stored; the second DNS server is a DNS server used when accessing the VPN.
According to the technical scheme, when the network equipment is not accessed to the VPN and locally stores first DNS server information, the network equipment determines that the equipment does not normally exit the VPN, and then the current DNS configuration can be updated to the first DNS server information from the second DNS server information; the first DNS server is used when the network equipment is not accessed to the VPN, and the second DNS server is used when the network equipment is accessed to the VPN. By adopting the mode, when the network equipment abnormally exits the VPN, the DNS configuration in the equipment can be restored from the DNS configuration when the VPN is accessed to the DNS configuration when the VPN is not accessed, so that the subsequent normal network connection of the equipment is ensured.
Drawings
Fig. 1 is a flowchart illustrating a method for recovering a DNS configuration according to an exemplary embodiment of the present application;
fig. 2 is a hardware structure diagram of a device in which a DNS configured recovery apparatus is located according to an exemplary embodiment of the present application;
fig. 3 is a block diagram of a DNS-configured recovery apparatus according to an exemplary embodiment of the present application.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this application and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.
It is to be understood that although the terms first, second, third, etc. may be used herein to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present application. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.
The DNS configuration of a network device when not accessing a VPN is typically different from the DNS configuration when accessing a VPN to access different network resources. For example, the DNS configuration of the network device when not accessing the VPN may be an address of an external network DNS server, so that the network device can normally access external network resources; and the DNS configuration of the network equipment when accessing the VPN is usually the address of an intranet DNS server, so that the network equipment can normally access intranet resources.
In the related art, a program for providing a VPN service to a user in a network device may be referred to as a VPN client. The VPN client can provide a login page based on a user name and a password for a user, and when the user name and the password input by the user are successfully matched, the VPN client can be regarded as receiving a VPN access request, so that the current DNS configuration can be updated to an internal network DNS server address used when the VPN is accessed, and meanwhile, the external network DNS server address before updating can be stored. In addition, the VPN client may also provide a logout page for the user, the user may click a logout button displayed on the page to logout, and the VPN client may be considered to receive a VPN logout request when it is determined that the user logout is successful, and may further update the current DNS configuration from the internal network DNS server address to the external network DNS server address according to the stored external network DNS server address, and delete the locally stored external network DNS server address, so as to avoid an error occurring when the DNS configuration is restored next time. Therefore, when the network equipment normally exits the VPN, the subsequent normal network connection of the network equipment can be ensured.
However, when the VPN exits abnormally, the device is powered off, the device is restarted forcibly, and the like, the DNS configuration in the network device is usually the address of the internal network DNS server used when the VPN is accessed, which may cause the network device to fail to access the external network resources normally, and the problem of abnormal network connection occurs. The application provides a method and a device for recovering DNS configuration, which can recover the DNS configuration in network equipment from the DNS configuration when the VPN is accessed to the DNS configuration when the VPN is not accessed when the abnormal condition occurs, so as to avoid abnormal network connection.
Referring to fig. 1, a flowchart of a DNS configuration recovery method according to an exemplary embodiment of the present application is shown, where the method may be applied to a network device, and includes the following steps:
step 101: and detecting whether the equipment is accessed to the VPN or not according to a preset time period.
In this embodiment, the network device may detect whether the device has accessed the VPN according to a preset time period; the time period may be a value preset by a user or a default value of the system, which is not particularly limited in the present application. Specifically, the network device may detect whether a VPN client in the network device is in a running state according to the time period. When the VPN client is in a running state, the network equipment can determine that the equipment has accessed the VPN, and then can continuously detect whether the equipment has accessed the VPN according to the time period; when the VPN client is in the non-operating state, the network device may determine that the device does not access the VPN, and then step 102 may be executed.
Step 102: if the device is not accessed to the VPN, detecting whether first DNS server information is stored locally; the first DNS server is a DNS server used when the VPN is not accessed.
Similar to the related art, when determining that a VPN access request is received, a VPN client in a network device may obtain a DNS configuration when the device is not accessed to a VPN, and store the obtained DNS configuration as information of a first DNS server; the first DNS server is a DNS server used when the device is not accessed to the VPN.
In this embodiment, based on the detection result in the foregoing step 101, if the device does not access the VPN, the network device may detect whether the first DNS server information is locally stored. When the first DNS server information is not stored locally, the network device is indicated to normally exit the VPN. When the first DNS server information is locally stored, it indicates that the network device does not normally exit the VPN, and the network device may execute step 103.
Step 103: and if the first DNS server information is locally stored, updating the current DNS configuration from the second DNS server information to the first DNS server information.
In this embodiment, based on the detection result in the foregoing step 102, if the first DNS server information is locally stored, the network device may update the current DNS configuration from the second DNS server information to the first DNS server information; and the second DNS server is used when the equipment accesses the VPN. In this way, when the network device does not normally quit the VPN, the DNS configuration in the device can be restored from the DNS configuration when the VPN is accessed to the DNS configuration when the VPN is not accessed, so that subsequent normal network connection of the device can be ensured.
It should be noted that, after updating the current DNS configuration from the second DNS server information to the first DNS server information, the network device may delete the locally stored first DNS server information, so as to avoid that, after completing the recovery of the DNS configuration in the network device, the network device mistakenly considers that the device does not normally exit the VPN because the first DNS server information is still locally stored, and updates the current DNS configuration to the first DNS server information again, which causes a waste of the performance of the network device.
In an optional embodiment, after the network device is powered on and started, the network device may immediately detect whether the device has accessed the VPN, and detect whether the first DNS server information is stored locally when it is determined that the device has not accessed the VPN. If the first DNS server information is stored locally, the network device may update the current DNS configuration from the second DNS server information to the first DNS server information. Therefore, when the network equipment is not normally quitted from the VPN due to the conditions of restarting after the power failure of the equipment, forced restarting of the equipment and the like, the DNS configuration of the equipment can be recovered from the DNS configuration when the equipment is accessed to the VPN to the DNS configuration when the equipment is not accessed to the VPN in a more timely manner, so that the subsequent normal network connection of the equipment is ensured.
In general, the first DNS server information stored in the network device is a DNS server address used by the device when the VPN is not accessed, and when the DNS configuration is restored, the network device may restore the DNS configuration of the device from the DNS server address used when the VPN is accessed to the DNS server address used when the VPN is not accessed. However, when a plurality of network cards are installed in the network device and the network cards are in an active state, the first DNS server information may include: the number of local active network cards, the network card identifier of each active network card, and the DNS server address corresponding to each active network card. For example, the first DNS server information stored by the network device may be as follows:
wherein, num 2 under the [ DnsNum ] label indicates that two active network cards are locally present when the network device does not access the VPN. Name0 and name1 under the [ DnsInfo ] label represent the network adapter names of the two movable network cards respectively, and can be regarded as the network card identifiers of the two movable network cards; ip0 represents a manually configured DNS server address for the active network card corresponding to the name0, and DHCP0 represents a DNS server address automatically acquired by the active network card corresponding to the name0 based on a DHCP (Dynamic Host Configuration Protocol); similarly, ip1 represents the manually configured DNS server address for the active network card corresponding to the name1, and DHCP1 represents the DNS server address automatically acquired by the active network card corresponding to the name1 based on DHCP.
When recovering the DNS configuration, the network device may determine that DNS server addresses corresponding to two active network cards in the device need to be updated according to num ═ 2 in the first DNS server information. The subsequent network device may update the DNS server address configured for the active network card corresponding to the name0 to 202.103.24.68, and clear the DNS server address configured for the active network card corresponding to the name 1. After the network device completes the updating of the DNS server addresses corresponding to the two active network cards, it can be determined that the recovery of the DNS configuration in the device is completed. Therefore, no matter whether the DNS server address corresponding to each active network card changes when the network equipment is accessed to the VPN or not, the DNS server address corresponding to the network equipment which is not accessed to the VPN can be recovered subsequently, so that normal network connection of the network equipment is ensured.
As can be seen from the above embodiments, when the device does not access the VPN and locally stores the first DNS server information, the network device determines that the device does not normally exit the VPN, and may update the current DNS configuration from the second DNS server information to the first DNS server information; the first DNS server is used when the network equipment is not accessed to the VPN, and the second DNS server is used when the network equipment is accessed to the VPN. By adopting the mode, when the network equipment abnormally exits the VPN, the DNS configuration in the equipment can be restored from the DNS configuration when the VPN is accessed to the DNS configuration when the VPN is not accessed, so that the subsequent normal network connection of the equipment is ensured.
Corresponding to the foregoing embodiments of the DNS configuration recovery method, the present application also provides embodiments of a DNS configuration recovery apparatus.
The embodiment of the recovery device configured by the DNS can be applied to network equipment. The device embodiments may be implemented by software, or by hardware, or by a combination of hardware and software. The software implementation is taken as an example, and is formed by reading corresponding computer program instructions in the nonvolatile memory into the memory for operation through the processor of the network device where the software implementation is located as a logical means. In terms of hardware, as shown in fig. 2, a hardware structure diagram of a network device in which a recovery apparatus configured by a DNS is located in the present application is shown, except for the processor, the memory, the network interface, and the nonvolatile memory shown in fig. 2, a network device in which the apparatus is located in the embodiment may also include other hardware according to an actual function of recovering the DNS configuration, which is not described again.
Referring to fig. 3, a block diagram of a DNS configured recovery apparatus according to an exemplary embodiment of the present application is shown, where the DNS configured recovery apparatus 300 may be applied to the network device shown in fig. 2, and includes:
a first detecting unit 301, configured to detect whether the device has accessed a virtual private network VPN according to a preset time period;
a second detecting unit 302, configured to detect whether the first domain name system DNS server information is locally stored when the device does not access the VPN; the first DNS server is a DNS server used when not accessing VPN;
a first updating unit 303, configured to update the current DNS configuration from the second DNS server information to the first DNS server information if the first DNS server information is locally stored; the second DNS server is a DNS server used when accessing the VPN.
In an optional embodiment, the first detecting unit 301 may be further configured to detect whether the device has accessed to the VPN after the device is powered on and started.
In another alternative embodiment, the apparatus 300 may further include:
a saving unit 304, configured to, when receiving the VPN access request, obtain a current DNS configuration, and save the DNS configuration as the first DNS server information.
In another alternative embodiment, the apparatus 300 may further include:
a second updating unit 305, configured to update the current DNS configuration from the second DNS server information to the first DNS server information when receiving the VPN exit request.
In another alternative embodiment, the apparatus 300 may further include:
a deleting unit 306, configured to delete the first DNS server information after updating the current DNS configuration from the second DNS server information to the first DNS server information.
The implementation process of the functions and actions of each unit in the above device is specifically described in the implementation process of the corresponding step in the above method, and is not described herein again.
For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of the application. One of ordinary skill in the art can understand and implement it without inventive effort.
The above description is only exemplary of the present application and should not be taken as limiting the present application, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the scope of protection of the present application.
Claims (10)
1. A method for recovering a DNS configuration, the method comprising:
detecting whether the equipment is accessed to a Virtual Private Network (VPN) or not according to a preset time period;
if the device is not accessed to the VPN, detecting whether first domain name system DNS server information is stored locally; the first DNS server is a DNS server used when not accessing VPN;
if the first DNS server information is locally stored, updating the current DNS configuration from second DNS server information to the first DNS server information; the second DNS server is a DNS server used when accessing the VPN.
2. The method of claim 1, further comprising:
after the equipment is powered on and started, whether the equipment is accessed to the VPN or not is detected.
3. The method of claim 1, further comprising:
and when receiving a VPN access request, acquiring the current DNS configuration, and storing the DNS configuration as the information of a first DNS server.
4. The method of claim 1, further comprising:
and updating the current DNS configuration from the second DNS server information to the first DNS server information when receiving a VPN exit request.
5. The method of claim 1, further comprising:
and after the current DNS configuration is updated to the first DNS information from the second DNS information, deleting the first DNS information.
6. An apparatus for recovering a DNS configuration, the apparatus comprising:
the first detection unit is used for detecting whether the equipment is accessed to the virtual private network VPN or not according to a preset time period;
the second detection unit is used for detecting whether the first domain name system DNS server information is stored locally or not when the device is not accessed to the VPN; the first DNS server is a DNS server used when not accessing VPN;
a first updating unit, configured to update a current DNS configuration from second DNS server information to the first DNS server information if the first DNS server information is locally stored; the second DNS server is a DNS server used when accessing the VPN.
7. The apparatus of claim 6,
the first detection unit is further configured to detect whether the device has accessed the VPN after the device is powered on and started.
8. The apparatus of claim 6, further comprising:
and the storage unit is used for acquiring the current DNS configuration when receiving the VPN access request and storing the DNS configuration as the first DNS server information.
9. The apparatus of claim 6, further comprising:
and the second updating unit is used for updating the current DNS configuration from the second DNS server information to the first DNS server information when receiving the VPN exit request.
10. The apparatus of claim 6, further comprising:
and the deleting unit is used for deleting the first DNS server information after the second DNS server information of the current DNS configuration is updated into the first DNS server information.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710114917.8A CN106911508B (en) | 2017-02-28 | 2017-02-28 | DNS configuration recovery method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710114917.8A CN106911508B (en) | 2017-02-28 | 2017-02-28 | DNS configuration recovery method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106911508A CN106911508A (en) | 2017-06-30 |
| CN106911508B true CN106911508B (en) | 2020-03-06 |
Family
ID=59208343
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710114917.8A Active CN106911508B (en) | 2017-02-28 | 2017-02-28 | DNS configuration recovery method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106911508B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108093098A (en) * | 2018-01-31 | 2018-05-29 | 杭州迪普科技股份有限公司 | A kind of domain name mapping request sending method and device |
| CN113411800B (en) * | 2021-06-16 | 2023-04-25 | 杭州迪普科技股份有限公司 | Method and device for assisting client in wireless network switching |
| CN114844858A (en) * | 2022-04-13 | 2022-08-02 | 山东浪潮超高清视频产业有限公司 | Method for obtaining domain name address by multiple networks |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101043447A (en) * | 2007-04-23 | 2007-09-26 | 重庆大学 | Method for mapping dynamically inside and outside network of server based on DDNS and NAT |
| CN102801695A (en) * | 2011-05-27 | 2012-11-28 | 华耀(中国)科技有限公司 | Virtual private network communication device and data packet transmission method thereof |
| CN104008482A (en) * | 2014-06-10 | 2014-08-27 | 北京奇虎科技有限公司 | Mobile terminal and payment method and device based on mobile terminal |
| CN105516394A (en) * | 2016-01-15 | 2016-04-20 | 青岛海信移动通信技术股份有限公司 | DNS (Domain Name System) address management method and terminal |
| CN105939312A (en) * | 2015-08-26 | 2016-09-14 | 杭州迪普科技有限公司 | Data transmission method and device |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101651666A (en) * | 2008-08-14 | 2010-02-17 | 中兴通讯股份有限公司 | Method and device for identity authentication and single sign-on based on virtual private network |
| CN102299836A (en) * | 2011-09-16 | 2011-12-28 | 北京星网锐捷网络技术有限公司 | Method and device for accessing access equipment |
| CN103905579B (en) * | 2012-12-28 | 2018-01-30 | 中国移动通信集团公司 | Communication method, communication system, platform and related equipment between platform and terminal |
| EP3001647B1 (en) * | 2014-09-23 | 2017-11-01 | Siemens Aktiengesellschaft | Method for setting up a secure communication link, communication device and connection control unit |
-
2017
- 2017-02-28 CN CN201710114917.8A patent/CN106911508B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101043447A (en) * | 2007-04-23 | 2007-09-26 | 重庆大学 | Method for mapping dynamically inside and outside network of server based on DDNS and NAT |
| CN102801695A (en) * | 2011-05-27 | 2012-11-28 | 华耀(中国)科技有限公司 | Virtual private network communication device and data packet transmission method thereof |
| CN104008482A (en) * | 2014-06-10 | 2014-08-27 | 北京奇虎科技有限公司 | Mobile terminal and payment method and device based on mobile terminal |
| CN105939312A (en) * | 2015-08-26 | 2016-09-14 | 杭州迪普科技有限公司 | Data transmission method and device |
| CN105516394A (en) * | 2016-01-15 | 2016-04-20 | 青岛海信移动通信技术股份有限公司 | DNS (Domain Name System) address management method and terminal |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106911508A (en) | 2017-06-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| RU2751551C1 (en) | Method and apparatus for restoring disrupted operating ability of a unit, electronic apparatus and data storage medium | |
| US9146839B2 (en) | Method for pre-testing software compatibility and system thereof | |
| JP5075736B2 (en) | System failure recovery method and system for virtual server | |
| US7536603B2 (en) | Maintaining functionality during component failures | |
| US20140068040A1 (en) | System for Enabling Server Maintenance Using Snapshots | |
| US20070220323A1 (en) | System and method for highly available data processing in cluster system | |
| US8990608B1 (en) | Failover of applications between isolated user space instances on a single instance of an operating system | |
| CN109587331B (en) | Method and system for automatically repairing cloud mobile phone fault | |
| CN107682172B (en) | Control center device, service system processing method and medium | |
| CN106911508B (en) | DNS configuration recovery method and device | |
| CN113438292A (en) | Agent deployment method and device based on automatic operation and maintenance tool | |
| CN107506295A (en) | Method of testing, equipment and the computer-readable recording medium of virtual machine backup | |
| CN112579359B (en) | Service system reconstruction method, device, equipment and storage medium | |
| US10754753B1 (en) | Performance of virtual machine instances using machine recognition of screenshot images | |
| CN113672415A (en) | Disk fault processing method, device, equipment and storage medium | |
| US9864651B2 (en) | Receiving an update code prior to completion of a boot procedure | |
| CN114185804B (en) | Interface testing method and device and terminal equipment | |
| CN109150587B (en) | Maintenance method and device | |
| CN106685744A (en) | Fault elimination method, apparatus and system | |
| US9172584B1 (en) | Method and system for high-availability cluster data protection | |
| JP6269199B2 (en) | Management server, failure recovery method, and computer program | |
| US8359220B2 (en) | Technical support routing among members of a technical support group | |
| CN113778763B (en) | Intelligent switching method and system for three-way interface service faults | |
| CN112131185B (en) | Method and device for high availability of service in super-fusion distributed storage node | |
| CN112882871B (en) | Host conflict detection method, device, equipment and storage 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 |