> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/qna/on-premise/domain-requirements-for-on-premise.md).

# Domain requirements for On-Premise

Register an A-type DNS record pointing to your server to enable SSL certificates and HTTPS. Optional: separate domains for API and admin panel

## Do I need to use a domain for my instance?

It is not mandatory, but it is highly recommended. Only domains can issue SSL certificates and therefore provide a secure HTTPS connection. If you configure to use only an IP address, you only have an unsecured HTTP connection. This is why configuring a web server to use an IP address is recommended only on classified subnets that are not accessible from the outside.

## What are requirements for the domain?

The only requirement is that it must be an "A" type DNS record pointing to your server.

## Do I need to register dedicated domains for API and admin panel?

This is optional and not a requirement. You can do this for your convenience. In the absence of dedicated domains, access to API and admin panel can be provided via subdirectories of the base domain of your instance, for example:

* domain.com/api/
* domain.com/panel/


---

# 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://navixy.com/docs/qna/on-premise/domain-requirements-for-on-premise.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.