Docs

TrafficRoute DNS Suite

Product Overview

Advantages

This document introduces the product advantages of HTTPDNS.

Risks of traditional DNS

In the traditional DNS process, the client sends a DNS query request to the Local DNS server using the UDP protocol. This will bring the following risks:

UDP protocol does not have encryption capability. Therefore, DNS query requests based on the UDP protocol may be intercepted or hijacked.

The local DNS server is managed and maintained by the local ISP. Due to differences in the management approaches and maintenance capabilities of different ISPs, Local DNS servers may encounter the following issues:

Cache refresh cannot be controlled: The update time of the cache on the local DNS server cannot be controlled. For example, after an A record is updated on the authoritative DNS server, Local DNS servers operated by different ISPs do not receive the update at the same time. This will result in some users accessing the new IP, while others will still access the old IP.

DNS hijacking: Records in the local DNS server cache are maliciously tampered with, causing them to point to phishing websites or advertisement pages.

Cross-network resolution result: The client's IP address and the IP address returned by the Local DNS server do not belong to the same ISP, resulting in poor network connection quality. In the following situations, parsing results may span networks:

DNS query forwarding: During recursive resolution, ISP A's Local DNS server may forward DNS queries to ISP B's Local DNS server. During the process in which ISP B initiates a recursive DNS query, the authoritative DNS server returns an IP address that belongs to ISP B.

Multiple egress IP addresses: The local DNS server converts internal IP addresses to internet egress IP addresses through network address translation (NAT). Local DNS servers typically have multiple egress IPs. Assume the client's IP address belongs to ISP A. When the local DNS server sends a DNS query request to the authoritative DNS server, it will perform NAT translation based on the IP address of the authoritative DNS server. After conversion, there is a certain probability that the egress IP will belong to ISP B. As a result, the IP address returned by the authoritative DNS server also belongs to ISP B.

Resolution timeout: Due to network latency, issues with the local DNS server, and other factors, the client's DNS query request times out. The client cannot obtain the IP address of the domain name.

Advantages of HTTPDNS

Compared with traditional DNS, HTTPDNS offers the following advantages:

Hijacking protection

HTTPDNS bypasses the Local DNS server and sends DNS query requests to the HTTPDNS server using the HTTP/HTTPS protocol. This reduces the risk of DNS query requests being eavesdropped on or hijacked.

Precise DNS resolution results

HTTPDNS ensures that you obtain accurate DNS resolution results through the following methods.

Granularity: city and ISP: In the HTTPDNS server-side DNS record cache, each DNS record contains both city and ISP information. When the client requests DNS resolution, the server returns a matching DNS record based on the city and ISP of the request IP, providing higher accuracy than the Local DNS server.

Accurate traffic routing: HTTPDNS has hundreds of server-side cache replicas. When distributing traffic based on the weight of DNS records, the accuracy of traffic distribution within a single TTL is higher than that of Local DNS servers.

Use a self-built IP database: HTTPDNS determines the city and ISP of the request IP based on the self-built IP database. The IP database is updated in real time and is guaranteed in terms of accuracy and coverage.

Monitor resolution accuracy: To ensure the accuracy of DNS resolution results, HTTPDNS has established a quality baseline. When the city and ISP of the requested IP do not match those of the resolved IP, technical support personnel will receive an alert and resolve the issue.

Resolution timeliness guarantee: The TTL of each DNS record in the server-side DNS record cache is identical to the TTL of the corresponding DNS record in the authoritative DNS. The issue of uncontrollable cache refresh for local DNS servers will no longer exist.

Customize DNS resolution results

To map certain domain names to custom IP addresses, configure custom DNS records in the HTTPDNS console. For example, you can set the IP address mapped to www.example.com to 192.168.2.2.

Last updated: 2025.11.04 20:49:37