DNS Asynchronous Prefresh
This behavior lets Akamai edge servers "prefresh" your origin DNS record. Prefreshing is a way of refreshing outside of the typical means, such as a request from a client, or the expiration of your origin DNS resolution's time to live (TTL).
Performance in serving clients can improve because the latency in serving objects is decreased. Clients are less likely to wait for revalidation with your origin when the objects are kept fresh, asynchronously.
This isn't a self-serviceable behavior
You'll need to work with your Akamai account team to have it added or modified.
Features and options
| Field | What it does |
|---|---|
| Enable | If this is set to On, the behavior is enabled. |
| Delay | This is an additional delay in seconds before the prefresh is applied. This is an optional setting. Talk to your account team about scenarios where this can be beneficial. |
| Timeout | If there haven't been any client requests for your origin's domain for this length of time, Akamai edge servers will send a request to perform the refresh. |
Caveats and known issues
-
There's a limit on the number of refreshes that Akamai edge servers can perform per second. If your origin server is trying to maintain a large number of names, such as origins, maps, etc, this limit might be reached and the DNS name might fail to refresh.
-
Standard methods to refresh your origin DNS still apply. If a client request to refresh the DNS is received by your origin, or its resolution TTL elapses, the origin will be refreshed. This feature works outside of these standard applications.
Updated about 1 year ago