> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.14/onboard-cortex-xsoar/disaster-recovery-and-live-backup/host-names-dns-and-disaster-recovery.md).

# Host Names, DNS, and Disaster Recovery

Configure host names and DNS for a Cortex XSOAR 6.14 disaster recovery environment.

Consider the following about host names, DNS and DR:

* When configuring Live Backup, each Cortex XSOAR server should have its own unique host name and IP address.
* You may require for analysts to always navigate to the same host name when accessing Cortex XSOAR. In this scenario, configure a separate DNS record which points to the active Cortex XSOAR server. In the event of a server failover, you are required to manually repoint this DNS record to the IP of the newly-active Cortex XSOAR server.
* It is critical that the TTL of the DNS record be set to a zero value. If it is higher, analysts are not able to access the active server using the shared host name until the TTL of the record expires and the DNS record is refreshed in the cache. This could take more than an hour.
* If you do not require a single URL to access Cortex XSOAR, when a server failover occurs, you might point your browser to the URL of the newly-active Cortex XSOAR server.


---

# 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://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.14/onboard-cortex-xsoar/disaster-recovery-and-live-backup/host-names-dns-and-disaster-recovery.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.