HTTPDNS is a DNS service provided for mobile applications. It sends DNS requests over the HTTP protocol instead of the DNS protocol, helping avoid DNS hijacking.
Generally, applications not based on the HTTPDNS SDK have the following problems:
1. Low access or download success rate of domain resources (Before the HTTPDNS SDK is used, the success rate is about 93% to 98%);
2. Difficulty in determining whether business exceptions occur at the DNS stage and whether application access exceptions are caused by DNS hijacking or the local DNS service.
In such cases, the HTTPDNS SDK can help improve the access or download success rate of domain resources to 99% or above. In addition, its DNS log reporting capabilities allow collecting data of DNS hijacking, query success rate, and DNS cache hit rate, improving your troubleshooting performance and application availability.
2. You have added domains to be resolved in the HTTPDNS console as instructed in Adding a Domain.
3. You have applied in the HTTPDNS console for SDK integration as instructed in SDK Activation Process.
4. After activating the service, you have been assigned the configuration information such as authorization ID, AES and DES encryption keys, and HTTPS token. You can also view them on the Development Configuration page.
5. Your application has been integrated with HTTPDNS Android SDK v4.4.0, iOS SDK 1.7.0, or later.
Directions
1. Before enabling the query monitoring feature of HTTPDNS, make sure Android SDK v4.4.0, iOS SDK 1.7.0, or later is used. For detailed directions, see Integrating iOS SDKor Integrating Android SDK.
2. On the Query monitoring page in the HTTPDNS console, toggle on Query monitoring to enable the feature. The HTTPDNS backend system will analyze the collected data and display the results.
Note
The query monitoring feature is under beta testing and will be billed after the testing ends. We will inform you the billing start time. Using this feature represents that you have agreed to the relevant agreements. You can toggle on or off Query monitoring to enable or disable this feature.
Metrics
Based on its strong data analysis capabilities, Tencent Cloud HTTPDNS has become a leading DNS data analysis platform for mobile applications in China. Its query monitoring page is as follows:
Metrics are as described below:
Total hijacks: The quantity of queries whose results returned by the local DNS and by HTTPDNS are totally inconsistent.
Prevented hijacks: The quantity of queries whose results are normally returned by HTTPDNS (err_code = 0), but these results are totally inconsistent with those returned by the local DNS.
Improvement rate: The proportion of prevented hijacks in the total hijacks.
DNS cache hit rate: The proportion of queries that hit the cache in the total queries.
Region view: The query volume, percentage of successful queries, and average query latency by country, province, or region.
ISP view: The query volume, percentage of successful queries, and average query latency by ISP (in China).
Top 10 hijacked domains: The top 10 domains for which the query results returned by HTTPDNS and by the local DNS are totally inconsistent, and the corresponding query volume.
Top 10 abnormal domains: The top 10 domains for which errors occurred (err_code != 0) to the HTTPDNS API requests. Errors are generally network exceptions, such as DNS timeout and inaccessible network.
Error codes: The following error codes (and the respective quantities) reported by the HTTPDNS SDK.
Error Code
Description
Error Code
Description
1
Failed to connect the DNS request
2
DNS timeout
1001
Failed to create the socket connection
21001
Failed to send the request
1004
Failed to change the channel to the non-blocking mode
3
No DNS data
1005
Failed to register the channel
31001
Failed to return the result. Please re-connect.
1006
Failed to create the socket address
31002
Failed to return the exception
1007
Failed to encrypt the request content
41001
Failed to decrypt the response content
1008
Failed to create the request body
41002
Failed to parse the response content
11001
Connection failed
0
Query succeeded
DNS sessions: The UV, WAU, and MAU data collected with an application cycle as a session.
Yes
No
Was this page helpful?