> 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/on-premise/on-premise/how-to-guide/requirements/domains.md). # Domains Configure domain names and DNS A-records for Navixy on-premise. Set up records for the API, admin panel, and monitoring service to enable platform access. Navixy is a web-based platform that is usually deployed in a public network. Therefore, a domain name is typically required to access the platform. While using an IP address is possible, domain names significantly improve the presentation and ease of use of the service. To use a domain name, an account with a public DNS hosting service is necessary. Many DNS hosting services are available, with one of the most popular being GoDaddy. Typically, a DNS hosting service provides an admin panel to create and control domain names. For Navixy, several A-type DNS records are needed, pointing to the Navixy server. Suppose the domain name is "[your-domain.com](http://your-domain.com)"; here's an example of the domain configuration: * [api.your-domain.com](http://api.your-domain.com): domain used for API calls and backend operations * [panel.your-domain.com](http://panel.your-domain.com): domain used for accessing the admin panel. It can also be [admin.your-domain.com](http://admin.your-domain.com) or anything else. * [my.your-domain.com](http://my.your-domain.com): domain used for accessing the monitoring service. This domain will be used by users. It can also be [gps.your-domain.com](http://gps.your-domain.com), [pro.your-domain.com](http://pro.your-domain.com), or anything else. After creating the A-type records, they can be used for the Navixy On-premise installation. --- # 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 dynamically 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/on-premise/on-premise/how-to-guide/requirements/domains.md?ask=&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 `build a script that syncs our docs to a CMS` 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.