Overview of the HTTP API integration solution
HTTPDNS employs multi-IP endpoints and soft scheduling to prevent DNS hijacking and ensure high availability, even if service IPs are blocked, under DDoS attacks, or in the event of an extreme natural disaster. The official SDKs already implement this pattern. If you do not want to integrate an SDK, you can use the HTTP API to resolve domain names directly.
Process for using the HTTP API
Call the HTTPDNS scheduling API to dynamically obtain a list of service endpoints, and then access an endpoint to resolve a domain name to an IP address:
-
Obtain a service endpoint for resolution
HTTPDNS deploys multiple service clusters worldwide, each with an IP address serving as a service endpoint. To help you access the nearest endpoint while maintaining high availability, HTTPDNS provides a mechanism for acquiring and maintaining available service endpoints.
-
Use the domain name resolution API to resolve domain names
After you obtain the service endpoints, call the domain name resolution API to resolve domain names. The API supports batch resolution, parameter encryption, and request signing.
NoteThe original APIs for resolving a single domain name, resolving domain names in batches, and implementing authorized access have been moved to the Legacy APIs section.
Using of the resolution result
After you obtain the resolution result, use the returned IP addresses in your business network requests. The way to handle resolution results with direct IP connections is the same as when you use the HTTPDNS SDK on each platform. For more information, see the following topics:
Use optimization
For recommendations on using HTTPDNS through the HTTP API in a stable and efficient manner, see Best practices.