Development configuration

更新时间:
复制 MD 格式

To add a security signature to your API requests, obtain the authentication secret key required for API authentication and parsing. You can also enable or disable direct access to APIs without authentication.

Procedure

  1. Log on to the EMAS console.

  2. In the navigation pane on the left, choose HTTPDNS > Integration Configuration > Development Configuration.

What you can get

Item

Description

AccountID

This ID is automatically generated when you activate HTTPDNS. It is bound to your current logon account.

You need this ID to call HTTP APIs or initialize SDKs.

Signing secret key

Use this key to generate the security key for authenticated APIs. For more information, see Signature generation and authentication mechanism.

AES data encryption secret key

Use this key to decrypt data from the parsing API.

Signing access

Control whether API requests require authentication:

  • Enable: Requests cannot be accessed directly. Authentication is required.

  • Disable: Requests can be accessed directly without authentication.

Refresh server-side domain name cache

If you change the authoritative server configuration for a domain name and want the changes to take effect immediately, refresh the HTTPDNS server-side cache for that domain name. After refreshing, HTTPDNS fetches new results from the authoritative server.

  1. Only domain names are supported. Wildcard domain names are not supported.

  2. Each AccountID can trigger up to five cache refreshes per day. This limit includes calls made through OpenAPI.

  3. Client-side caches are not refreshed. To refresh client-side caches, see the following topics:

Enable DoH

To enable DNS over HTTPS (DoH), see Configure DoH service.