> For the complete documentation index, see [llms.txt](https://clients.medianova.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://clients.medianova.com/products/performance-cdn/dynamic-content-acceleration/aksela-test-steps.md).

# Test a Dynamic CDN Resource

Learn how to verify that your Dynamic CDN Resource is working correctly before updating your DNS records.

After configuring your Dynamic CDN Resource, verify that requests are served through the Medianova CDN before directing production traffic to the resource.

{% hint style="info" %}
This procedure temporarily modifies your local hosts file for testing purposes. Public DNS records are not affected.
{% endhint %}

{% stepper %}
{% step %}

### Retrieve the CDN IP address

Open a command prompt or terminal.

Run the following command using your Dynamic CDN Resource hostname.

```
ping <CDN_HOSTNAME>.mncdn.com
```

→ Record the returned IP address.
{% endstep %}

{% step %}

### Configure your local hosts file

Open the local **hosts** file with administrator privileges.

Add a new entry that maps your domain to the CDN IP address.

Example:

```
203.0.113.10    www.example.com
```

Replace the IP address and domain with your own values.

Save the file.
{% endstep %}

{% step %}

### Verify CDN delivery

Clear your browser cache.

Open your website using its normal domain.

Open the browser's Developer Tools and navigate to **Network**.

Select the HTML document and review the **Response Headers**.

Verify that the response contains:

```
Server: MNCDN
```

→ This confirms that the HTML response is being served through the Dynamic CDN Resource.
{% endstep %}
{% endstepper %}

### Next step

After verifying that the Dynamic CDN Resource is serving requests correctly, create a [CNAME record](/products/performance-cdn/static-content-delivery/advanced-configuration/cname-and-ssl.md) that points your domain to the CDN hostname.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://clients.medianova.com/products/performance-cdn/dynamic-content-acceleration/aksela-test-steps.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.