> 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/dns/redirect.md).

# Redirect

Forward traffic from one URL to another directly in the Medianova Control Panel.

Redirect allows you to forward traffic from one URL to another directly within the DNS section of the Medianova Control Panel. Use this feature to manage permanent, temporary, or advanced redirect rules.

### In this section

* [**Getting Started with Redirect**](/products/dns/redirect/getting-started-with-redirect.md)\
  Learn the basics of redirect, the difference between DNS records and HTTP redirects, and common use cases.
* [**Manage Redirect**](/products/dns/redirect/manage-redirect.md)\
  Step-by-step guide to create, edit, and delete redirects in the Medianova Control Panel.
* [**Types of Redirects**](/products/dns/redirect/types-of-redirects.md)\
  Detailed explanation of permanent (301), temporary (302), and masking redirects, with best practices.
* [**Redirect Options**](/products/dns/redirect/redirect-options.md)\
  Advanced configuration such as Path Forwarding, Query Forwarding, and HTTPS settings.


---

# 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/dns/redirect.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.
