All Products
Search
Document Center

HTTPDNS:Common scenarios

Last Updated:Jun 10, 2026

HTTPDNS protects terminal applications from ISP-level DNS hijacking and gives you precise control over DNS resolution routing, making it well-suited for mobile apps, gaming clients, video players, automotive systems, and IoT devices.

Protect your app from domain hijacking

Standard DNS resolution relies on ISP-operated recursive resolvers. When those resolvers are compromised or misconfigured, users get redirected to wrong IP addresses—resulting in failed connections, unauthorized ad injections, data interception, or an app that simply stops working.

HTTPDNS bypasses ISP resolvers by sending DNS queries directly over HTTP. Terminal applications—including mobile apps, automotive applications, and IoT devices—resolve domains through HTTPDNS servers, so hijacked or poisoned resolver responses never reach your users.

This is especially critical for:

  • Gaming: Player login and matchmaking failures caused by redirected DNS responses

  • Video streaming: Playback interruptions or traffic diverted to unauthorized CDN nodes

  • Automotive apps: Navigation or telematics failures from unstable cellular DNS resolution

  • IoT devices: Device-to-cloud communication failures from hijacked local resolver responses

Control how traffic is routed across your network

Standard DNS returns a single IP address, or a fixed set of IP addresses, per domain. If traffic conditions change—a region goes down, a data center is overloaded, or a test requires isolated traffic—you cannot adjust routing without updating DNS records globally.

HTTPDNS uses software-defined DNS (SDNS) to let you define custom resolution rules per request, with full control over parameters and return values. You can:

  • Intelligent scheduling: Distribute traffic dynamically based on real-time conditions such as latency, load, or availability.

  • Custom routes: Return different IP addresses or endpoints based on caller identity, region, or any custom parameter you define.

  • Targeted traffic scheduling: Route specific traffic segments to designated servers—useful for A/B testing, canary releases, or regulatory isolation.