> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/hardware/creating-controllers/configuring-dns-servers-for-controllers.md).

# Configuring DNS Servers for Controllers

### Introduction

Controllers must be able to make use of Domain Name Servers (DNS) in disaster recovery situations, especially where backup servers reside on different subnets.

Operators with the “Edit Site” operator privilege can configure DNS at Controller level, (i.e. specifically set for each Controller), using this procedure.

### Procedure

1. Click **Configure** from the menu bar, then **Hardware**.

   The **Hardware** List Window opens (in [tree view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/tree-view.md)).
2. Highlight the Controller you want to configure a DNS Server(s) for.
3. **Right click** and select **Properties**.
4. Click the **Network** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-90597163aab60cb451e5cbb1d4c4384a3f8ca9bd%2Fcontroller6000_networktab_defaultsettings.png?alt=media)
5. Click the radio button for the appropriate **Server Address**, (i.e. either **Default Server Address** or **Custom Server Address** ).

   If you selected **Automatic (DHCP)** for the "Network Method", and you select **Custom Server Address**, this section will change as shown below:

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-78fe37918cc46b64318f4ea5a50fb34e7bf9b6d9%2Fcontroller6000_networktab_customserveraddress_automaticnwmethod.png?alt=media)

   **Automatic (DHCP)** is the preferred "Network Method", but if you selected **Manual**, and you select **Custom Server Address**, this section will change as shown below:

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-ba84d4309ea4cb51aeb10548cc61854a995aa7f9%2Fcontroller6000_networktab_customserveraddress_manualnwmethod.png?alt=media)
6. Enter either an IP address, (e.g. 192.168.1.198) or a Hostname, (e.g. myserver.mydomain.com), not both.

   **Note:** The DNS server configuration only appears after you type in a DNS name for the server, as shown below:

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-3d3bd11a5238e39e2153e96b19d2dbc282d02c73%2Fcontroller6000_networktab_dnsserverconfig.png?alt=media)
7. Tick the **Enable Custom DNS** checkbox if required.

   Did you tick this option?

   <table><thead><tr><th width="94">If...</th><th>then...</th></tr></thead><tbody><tr><td>no,</td><td>the controller will be configured with the same DNS addresses as the server.<br>Go to Step 8.</td></tr><tr><td>yes,</td><td><p>the <strong>Primary</strong>, <strong>Secondary</strong> and <strong>Tertiary</strong> fields allow up to three DNS Server IP addresses to be specified, and the order of priority in which they should be referenced, for determining the IP address of the Controller’s server. Invalid IP addresses are not accepted.<br><br><strong>Notes:</strong></p><ul><li>When the Controller attempts to resolve the hostname the DNS Servers are queried beginning with the Primary one. If that fails to reply, the Secondary one is attempted, and finally the Tertiary.</li><li>If all attempts to connect to the specified DNS Servers fail, then the Controller will use the fixed Server IP address it was given.</li><li>Only the first IP address returned by a successful DNS reply is used.</li></ul></td></tr></tbody></table>
8. Click **OK** to exit and save your changes.

   Click **Cancel** to exit without saving your changes.

   Click **Apply** to save your changes and stay in this window.

### Result

A Controller has been configured for DNS.


---

# 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://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/hardware/creating-controllers/configuring-dns-servers-for-controllers.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.
