CN104993948A - DNS domain name resolution fault processing method, DNS domain name resolution fault processing system and mobile terminal - Google Patents
DNS domain name resolution fault processing method, DNS domain name resolution fault processing system and mobile terminal Download PDFInfo
- Publication number
- CN104993948A CN104993948A CN201510317468.8A CN201510317468A CN104993948A CN 104993948 A CN104993948 A CN 104993948A CN 201510317468 A CN201510317468 A CN 201510317468A CN 104993948 A CN104993948 A CN 104993948A
- Authority
- CN
- China
- Prior art keywords
- dns
- client
- service end
- http request
- domain name
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Abstract
The invention discloses a DNS domain name resolution fault processing method, a DNS domain name resolution fault processing system and a mobile terminal. The method comprises the following steps: a client initiates a HTTP request; a first server responds to the HTTP request, and sends feedback information containing HTTP request header information to the client; the client judges whether there is a DNS authentication password consistent with the client in the HTTP request header information; a server IP requested by the client is modified to a target server IP of the DNS authentication password consistent with the client and a host domain name is added to the request header if there is no DNS authentication password consistent with the client in the HTTP request header information; the client initiates a request for accessing a DNS domain name resolution platform, and acquires a second server IP list after DNS resolution; the client verifies the IP list, and judges whether there is a DNS authentication password consistent with the client; and the process ends until the server confirms that the IP after DNS resolution is the target server IP. Through the scheme, a DNS domain name resolution fault can be processed automatically.
Description
Technical field
The present invention relates to DNS name resolution field, especially relate to a kind of method of DNS name resolution troubleshooting, system and mobile terminal.
Background technology
In prior art, mobile terminal is widely used in different telecom operators, when communication, some server only carries out different domain name mappings for individual operators, and separately there is part server and cannot realize DNS name resolution, or occurs the situation that some areas cannot be resolved, DNS kidnaps and happens occasionally simultaneously, namely DNS can resolve, but the result of resolving is wrong, or is resolved on the server of forgery.Therefore be necessary to provide a kind of method that automatically can process DNS name resolution fault.
Summary of the invention
Technical problem to be solved by this invention is: a kind of method providing DNS name resolution troubleshooting, realizes process DNS name resolution fault automatically.
In order to solve the problems of the technologies described above, the technical solution used in the present invention is: a kind of method providing DNS name resolution troubleshooting, comprising:
Client initiates http request;
First service end responds described http request, and sends the feedback information with http request header to client;
Client judges whether there be the DNS authenticate password consistent with client in described http request header;
If not, then the service end IP of client-requested is revised as the destination service end IP of the DNS authenticate password consistent with client, and in request header, adds host domain name;
Client initiates the request of access DNS name resolution platform, and obtains the second service end IP list after parsing DNS;
IP list described in client certificate, judges whether the DNS authenticate password consistent with client;
If not, then return execution step " the second service end IP of client-requested to be revised as the destination service end IP of the DNS authenticate password consistent with client, and in request header, to add host domain name "; Until service end confirms that the IP after dns resolution is destination service end IP.
Wherein, client also comprises before initiating the step of http request:
Client and destination service end consult confirmation DNS authenticate password;
When compiling client, embed described DNS authenticate password.
Wherein, service end responds described http request, and client also comprises after judging whether to have in described http request header the step of the DNS authenticate password consistent with client:
If so, then service end confirms that the IP after dns resolution is destination service end IP;
The request logic of client continuation self, performs the subsequent step of described request logic.
Wherein, client initiates the request of access DNS name resolution platform, and obtain parse DNS after the step of IP list of second service end be specially:
Client initiates the request of access domain name analysis platform, and obtains the second service end IP list after parsing DNS.
Wherein, the second service end IP of client-requested is revised as the destination service end IP of the DNS authenticate password consistent with client, and the step adding host domain name in request header is specially:
Http request is revised with APP;
The second service end IP of client-requested is revised as the destination service end IP of the DNS authenticate password consistent with client;
Host domain name is added in http request head.
Wherein, IP list described in client validation, after judging whether the step of the DNS authenticate password consistent with client, also comprises;
If so, step " service end confirms that the IP after dns resolution is destination service end IP " is then performed.
Wherein, the step obtaining the IP list after parsing DNS is specially:
Collect various places DNS service end IP by domain name mapping platform, obtain the second service end IP list after parsing DNS; Or
DNS service end is specified to obtain the second service end IP list after parsing DNS.
For solving the problem, the present invention also provides a kind of system of DNS name resolution troubleshooting, comprising: client, first service end, DNS name resolution platform, second service end and destination service end; Wherein,
Client initiates http request;
First service end responds described http request, and sends the feedback information with http request header to client;
Client judges whether there be the DNS authenticate password consistent with client in described http request header;
If not, then the service end IP of client-requested is revised as the destination service end IP of the DNS authenticate password consistent with client, and in request header, adds host domain name;
Client initiates the request of access DNS name resolution platform, and obtains the second service end IP list after parsing DNS;
IP list described in client validation, judges whether the DNS authenticate password consistent with client;
If not, then return execution step " the second service end IP of client-requested to be revised as the destination service end IP of the DNS authenticate password consistent with client, and in request header, to add host domain name "; Until service end confirms that the IP after dns resolution is destination service end IP.
For solving the problem, the present invention also provides a kind of mobile terminal, and described mobile terminal comprises system described above.
Beneficial effect of the present invention is: initiate http request by client; After the response of first service end, judge in http request header, whether there be the DNS authenticate password consistent with client by client; If not, then the second service end IP of client-requested is revised as the destination service end IP of the DNS authenticate password consistent with client, and in request header, adds host domain name; Client initiates the request of access DNS name resolution platform, and obtains the second service end IP list after parsing DNS; And verify described IP list, judge whether the DNS authenticate password consistent with client; Until second service end confirm as dns resolution after IP be destination service end IP.The present invention can realize the automatic process to DNS name resolution fault.
Accompanying drawing explanation
Fig. 1 is the inventive method embodiment one schematic flow sheet;
Fig. 2 is the inventive method embodiment two schematic flow sheet;
Fig. 3 is present system embodiment three structured flowchart.
Embodiment
By describing technology contents of the present invention in detail, realized object and effect, accompanying drawing is coordinated to be explained below in conjunction with execution mode.
The design of most critical of the present invention is: when the http response DNS authenticate password that discovery http request server returns does not exist or be incorrect, then first inquired the parsing IP of regional by DNS name resolution platform; And attempt one by one, find out the IP address that can access and DNS authenticate password is correct server; The server that last mandatory requirement accesses the IP that can access reaches the object of automatic handling failure.
Please refer to Fig. 1, the inventive method embodiment one provides a kind of method of DNS name resolution troubleshooting, comprises the steps:
S1: client initiates http request;
S2: first service end responds described http request, and send the feedback information with http request header to client;
S3: client judges whether there be the DNS authenticate password consistent with client in http request header;
S4: if not, be then revised as the destination service end IP of the DNS authenticate password consistent with client, and in request header, add host domain name by the service end IP of client-requested;
S5: client initiates the request of access DNS name resolution platform, and obtain the second service end IP list after parsing DNS;
S6: IP list described in client validation, judges whether the DNS authenticate password consistent with client;
S7: if not, then return and perform step S4; Until second service end confirm as dns resolution after IP be destination service end IP.
Wherein, above-mentioned first service end or second service end can be all multiple, also corresponding corresponding IP list.The IP of first service end or second service end is that when having the DNS authenticate password consistent with client, then such service end is destination service end.
Be different from prior art, the embodiment of the present invention one initiates http request by client; After the response of first service end, judge in http request header, whether there be the DNS authenticate password consistent with client by client; If not, then the second service end IP of client-requested is revised as the destination service end IP of the DNS authenticate password consistent with client, and in request header, adds host domain name; Client initiates the request of access DNS name resolution platform, and obtains the second service end IP list after parsing DNS; And verify described IP list, judge whether the DNS authenticate password consistent with client; Until second service end confirm as dns resolution after IP be destination service end IP.The present invention can realize the automatic process to DNS name resolution fault, and the automatic process that can realize DNS name resolution fault, decrease APP and cause the non-serviceable situation of user because local dns resolution is incorrect, and can ensure that the IP automatically repaired is correct IP, the IP that can not be kidnapped by DNS, the stability of the system improved, ensures its fail safe simultaneously.
Wherein, on the basis of embodiment one, in embodiments of the invention two before step S1, also comprise:
S01: client and destination service end consult confirmation DNS authenticate password;
S02: when compiling client, embed described DNS authenticate password.
Wherein, after step S3, also comprise:
If so, then step S7 is performed: service end confirms that the IP after dns resolution is destination service end IP;
S71: the request logic of client continuation self, performs the subsequent step of described request logic.
Wherein, step S5 is specially:
S51: client initiates the request of access domain name analysis platform, and obtain the second service end IP list after parsing DNS.
Particularly, collect various places DNS service end IP by domain name mapping platform, obtain the IP list after parsing DNS, wherein domain name mapping platform can be Ali's cloud searching platform; Or specify DNS service end to obtain the IP list after parsing DNS.
Wherein, step S4 is specially:
S41: revise http request with APP;
S42: the destination service end IP service end IP of client-requested being revised as the DNS authenticate password consistent with client;
S43: add host domain name in http request head.
Wherein, as shown in Figure 3, the embodiment of the present invention three correspondence also provides a kind of system 100 of DNS name resolution troubleshooting, comprising: client 110, first service end 120, DNS name resolution platform 130, second service end 140 and destination service end 150; Wherein,
Client 110 initiates http request;
First service end 120 responds described http request, and sends the feedback information with http request header to client 110;
Client 110 judges whether there be the DNS authenticate password consistent with client 110 in http request header;
If not, then second service end IP client 110 asked is revised as the destination service end IP of the DNS authenticate password consistent with client 110, and in request header, add host domain name;
Client 110 initiates the request of access DNS name resolution platform 130, and obtains the second service end 140IP list after parsing DNS;
Client 110 verifies described IP list, judges whether the DNS authenticate password consistent with client 110;
If not, then return execution step " the service end IP that client 110 is asked to be revised as the destination service end IP of the DNS authenticate password consistent with client 110, and in request header, to add host domain name "; Until service end 140 confirm as dns resolution after IP be destination service end IP.
Wherein, the present invention also provides a kind of mobile terminal (not shown), and described mobile terminal comprises system 100 described above.
Because mobile phone terminal can control request more flexibly than web terminal, mobile phone terminal app can freely assemble http request head and content thereof simultaneously, and web terminal have sandbox filter (when not revising browser source code) cannot at browser end given server IP, can only be resolved by amendment dns server, be synchronized in operating system, reach the object of amendment dns resolution to another one available server.Therefore the present invention goes back correspondence and provides a kind of mobile terminal.
The foregoing is only embodiments of the invention; not thereby the scope of the claims of the present invention is limited; every equivalents utilizing specification of the present invention and accompanying drawing content to do, or be directly or indirectly used in relevant technical field, be all in like manner included in scope of patent protection of the present invention.
Claims (9)
1. a method for DNS name resolution troubleshooting, is characterized in that, comprising:
Client initiates http request;
First service end responds described http request, and sends the feedback information with http request header to client;
Client judges whether there be the DNS authenticate password consistent with client in described http request header;
If not, then the service end IP of client-requested is revised as the destination service end IP of the DNS authenticate password consistent with client, and in request header, adds host domain name;
Client initiates the request of access DNS name resolution platform, and obtains the second service end IP list after parsing DNS;
IP list described in client validation, judges whether the DNS authenticate password consistent with client;
If not, then return execution step " the service end IP of client-requested to be revised as the destination service end IP of the DNS authenticate password consistent with client, and in request header, to add host domain name "; Until second service end confirm as dns resolution after IP be destination service end IP.
2. the method for DNS name resolution troubleshooting according to claim 1, is characterized in that, client also comprises before initiating the step of http request:
Client and destination service end consult confirmation DNS authenticate password;
When compiling client, embed described DNS authenticate password.
3. the method for DNS name resolution troubleshooting according to claim 1, is characterized in that, client also comprises after judging whether to have in described http request header the step of the DNS authenticate password consistent with client:
If so, then service end confirms that the IP after dns resolution is destination service end IP;
The request logic of client continuation self, performs the subsequent step of described request logic.
4. the method for DNS name resolution troubleshooting according to claim 1, is characterized in that, client initiates the request of access DNS name resolution platform, and the step obtaining the second service end IP list after parsing DNS is specially:
Client initiates the request of access domain name analysis platform, and obtains the second service end IP list after parsing DNS.
5. the method for DNS name resolution troubleshooting according to claim 1, it is characterized in that, the service end IP of client-requested is revised as the destination service end IP of the DNS authenticate password consistent with client, and the step adding host domain name in request header is specially:
Http request is revised with APP;
The service end IP of client-requested is revised as the destination service end IP of the DNS authenticate password consistent with client;
Host domain name is added in http request head.
6. the method for DNS name resolution troubleshooting according to claim 1, is characterized in that, IP list described in client validation, after judging whether the step of the DNS authenticate password consistent with client, also comprises;
If so, step " service end confirms that the IP after dns resolution is destination service end IP " is then performed.
7. the method for DNS name resolution troubleshooting according to claim 1 or 4, is characterized in that, the step obtaining the second service end IP list after parsing DNS is specially:
Collect various places DNS service end IP by domain name mapping platform, obtain the second service end IP list after parsing DNS; Or
DNS service end is specified to obtain the second service end IP list after parsing DNS.
8. a system for DNS name resolution troubleshooting, is characterized in that, comprising: client, first service end, DNS name resolution platform, second service end and destination service end; Wherein,
Client initiates http request;
First service end responds described http request, and sends the feedback information with http request header to client;
Client judges whether there be the DNS authenticate password consistent with client in described http request header;
If not, then the service end IP of client-requested is revised as the destination service end IP of the DNS authenticate password consistent with client, and in request header, adds host domain name;
Client initiates the request of access DNS name resolution platform, and obtains the second service end IP list after parsing DNS;
IP list described in client validation, judges whether the DNS authenticate password consistent with client;
If not, then return execution step " the second service end IP of client-requested to be revised as the destination service end IP of the DNS authenticate password consistent with client, and in request header, to add host domain name "; Until second service end confirm as dns resolution after IP be destination service end IP.
9. a mobile terminal, is characterized in that, described mobile terminal comprises system according to claim 8.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201510317468.8A CN104993948B (en) | 2015-06-11 | 2015-06-11 | Method, system and the mobile terminal of DNS name resolution troubleshooting |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201510317468.8A CN104993948B (en) | 2015-06-11 | 2015-06-11 | Method, system and the mobile terminal of DNS name resolution troubleshooting |
Publications (2)
Publication Number | Publication Date |
---|---|
CN104993948A true CN104993948A (en) | 2015-10-21 |
CN104993948B CN104993948B (en) | 2018-05-18 |
Family
ID=54305704
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN201510317468.8A Active CN104993948B (en) | 2015-06-11 | 2015-06-11 | Method, system and the mobile terminal of DNS name resolution troubleshooting |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN104993948B (en) |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20100274970A1 (en) * | 2009-04-23 | 2010-10-28 | Opendns, Inc. | Robust Domain Name Resolution |
US7979734B2 (en) * | 2007-07-11 | 2011-07-12 | Samsung Electronics Co., Ltd. | Method and system for preventing service disruption of internet protocol (IP) based services due to domain name resolution failures |
CN102624914A (en) * | 2012-03-22 | 2012-08-01 | 北京快网科技有限公司 | Method for detecting local DNS (Domain Name Server) used by client side in Web form |
CN102790808A (en) * | 2011-05-16 | 2012-11-21 | 奇智软件(北京)有限公司 | Domain name resolution method and system, client |
-
2015
- 2015-06-11 CN CN201510317468.8A patent/CN104993948B/en active Active
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7979734B2 (en) * | 2007-07-11 | 2011-07-12 | Samsung Electronics Co., Ltd. | Method and system for preventing service disruption of internet protocol (IP) based services due to domain name resolution failures |
US20100274970A1 (en) * | 2009-04-23 | 2010-10-28 | Opendns, Inc. | Robust Domain Name Resolution |
CN102790808A (en) * | 2011-05-16 | 2012-11-21 | 奇智软件(北京)有限公司 | Domain name resolution method and system, client |
CN102624914A (en) * | 2012-03-22 | 2012-08-01 | 北京快网科技有限公司 | Method for detecting local DNS (Domain Name Server) used by client side in Web form |
Also Published As
Publication number | Publication date |
---|---|
CN104993948B (en) | 2018-05-18 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9596501B2 (en) | Remote control processing method, device and system | |
CN107147671B (en) | Website routing-based access right control method, access method and system | |
CN110324338B (en) | Data interaction method, device, fort machine and computer readable storage medium | |
CN104580553B (en) | Method and device for identifying network address translation equipment | |
US20170262263A1 (en) | Process and system for the generation of an operating program in the form of a mobile application that is capable of operating on a mobile device | |
CN109768980B (en) | Server access method, device, mobile terminal and computer readable storage medium | |
CN112073439A (en) | Secure Internet access control method, gateway equipment and storage medium | |
CN114995214A (en) | Method, system, device, equipment and storage medium for remotely accessing application | |
CN105812481A (en) | Hypertext transfer protocol request identification system and hypertext transfer protocol request identification method | |
CN109561010B (en) | Message processing method, electronic equipment and readable storage medium | |
CN105491045A (en) | Authentication-free access control method, apparatus, device and system | |
CN104660523A (en) | Network access control system | |
US20180295162A1 (en) | Communications methods, apparatus and systems for correlating registrations, service requests and calls | |
US8879556B2 (en) | Managing a home network | |
CN105101040A (en) | Resource creating method and device | |
CN101771694B (en) | Method for ensuring successful webpage browsing at client side and device therefor | |
CN112953764A (en) | Networking terminal configuration method and device, networking terminal and computer storage medium | |
CN104993948A (en) | DNS domain name resolution fault processing method, DNS domain name resolution fault processing system and mobile terminal | |
CN109165513B (en) | System configuration information inspection method and device and server | |
US10462266B2 (en) | Data communication method and apparatus | |
US10375141B2 (en) | Method for processing URL and associated server and non-transitory computer readable storage medium | |
JP2013105250A (en) | Access line specification/authentication system | |
US20190208489A1 (en) | Registration management method and device | |
CN103002063B (en) | A kind of DNS of utilization realizes the method and system that URL forwards | |
CN114338630A (en) | Domain name access method, device, electronic equipment, storage medium and program product |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
C06 | Publication | ||
PB01 | Publication | ||
C10 | Entry into substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
GR01 | Patent grant | ||
GR01 | Patent grant |