> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/ras-admin-guide/v20-en-us/parallels-ras-20-administrators-guide/connection-and-authentication-settings/allowing-users-to-discover-ras-connections-via-email-address.md).

# Allowing users to discover RAS connections via email address

You can allow users to log in to the RAS Farms by using their email addresses. This way, users can gain access to applications and desktops published on a Farm without knowing the server address or hostname. All native Parallels Clients support finding Parallels RAS Farms by entering an email address.

For users to connect to a Farm using their email addresses, first you need to create a new TXT record in the forward lookup zone of users’ domain on your DNS server. The specific way to do this depends on the configuration of the DNS server.

The syntax of the TXT record is as follows:

Host: `_prlsclient`

Text : `hostname:port/theme;connmode=X;authmode=X`

The following parameters are available for the text field:

* `hostname`: Hostname of the server where the Secure Gateway resides. This parameter is mandatory.
* `port:` Port on which the Secure Gateway listens for incoming connections. This parameter is optional.
* `theme`: Theme. This parameter is optional.
* `connmode`: connection mode. This parameter is optional. Possible values are `0`, `1`, `2`, `3`, where:
  * `0`: Gateway mode
  * `1`: Direct mode
  * `2`: Gateway SSL
  * `3`:Direct SSL
* `authmode`: Authentication type. This parameter is optional. Possible values are `0`, `1`, `2`, `3`, where
  * `0`: Credentials
  * `1`: SSO
  * `2`: Smartcard
  * `3`: SAML

Examples of the text value:

`hostname`

`hostname:port`

`hostname:port/theme`

`hostname;connmode=2;authmode=1`

After the DNS record is configured, users will be able to log in using their email addresses. For information on how to do that on specific clients, see Parallels Client Guides.


---

# 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://docs.parallels.com/landing/ras-admin-guide/v20-en-us/parallels-ras-20-administrators-guide/connection-and-authentication-settings/allowing-users-to-discover-ras-connections-via-email-address.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 `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.