1. Introduction
Obtaining a startup IP address is the first step in integrating with HTTPDNS through the HTTP API and is critical for all subsequent operations. This topic explains why startup endpoints use a combination of multiple IP addresses and a domain name, and lists the available endpoints.
2. "Multiple IPs + domain name" endpoints
HTTPDNS is a foundational network service whose availability directly affects your application. Startup endpoints use a multiple IPs + domain name fallback architecture to ensure high availability between the client and the scheduling server, leveraging the strengths of both IP addresses and domain names.
Advantages of IP addresses:
-
Complete independence: Startup endpoints do not rely on the local Domain Name System (DNS), ensuring HTTPDNS operates independently.
-
Hijacking prevention: Direct IP access avoids hijacking threats that can occur during DNS resolution.
-
Redundancy: Multiple built-in IP addresses prevent single points of failure (SPOFs) and improve service accessibility.
Advantages of domain names:
-
Dynamic updates: Domain names enable dynamic endpoint updates, even though they depend on the local DNS.
-
Ultimate fallback: If all IP addresses become unavailable, the domain name can still fetch the latest service endpoints.
-
O&M flexibility: Service access policies can be adjusted dynamically without releasing a new client version.
By combining these advantages, the multiple IPs + domain name fallback pattern maximizes scheduling service availability and maintainability while keeping HTTPDNS independent.
3. List of startup endpoints
Configure your application with the following HTTPDNS startup endpoints. Prioritize IP addresses and use the domain name as a fallback only in extreme scenarios.
-
Dual-purpose endpoints: Startup endpoints serve as both scheduling and resolution services. If no scheduling result has been returned, you can use the endpoint directly for domain name resolution, but this is not recommended for continuous use.
-
Functional equivalence: All startup endpoints are functionally equivalent. Choose the one closest to your clients' geographic location for optimal network performance.
-
Multi-IP retry: If a call to the scheduling API fails, retry the request with a different startup IP address or the domain name.
Endpoints outside the Chinese mainland
|
Region |
IPv4 endpoints |
IPv6 endpoints |
Domain name endpoint |
|
China (Hong Kong) |
47.56.234.194 47.56.119.115 |
240b:4000:f10::178 240b:4000:f10::188 |
resolvers-hk.httpdns.aliyuncs.com |
|
Singapore |
161.117.200.122 47.74.222.190 |
240b:4000:f10::178 240b:4000:f10::188 |
resolvers-sg.httpdns.aliyuncs.com |
|
Americas |
47.246.131.175 47.246.131.141 |
2404:2280:4000::2bb 2404:2280:4000::23e |
resolvers-us.httpdns.aliyuncs.com |
|
Europe |
47.89.80.182 47.246.146.77 |
2404:2280:3000::176 2404:2280:3000::188 |
resolvers-de.httpdns.aliyuncs.com |
4. Summary
HTTPDNS startup endpoints use the multiple IPs + domain name architecture to avoid reliance on the local DNS and provide a fallback mechanism for extreme scenarios.
Next, call the scheduling API of a startup endpoint to obtain the resolution service IP address. For more information, see Scheduling service API.