Auto-discovery for the Axigen mobile apps is available starting with Axigen X7 (10.7.x).
When a user signs in to the Axigen mobile app for the first time, the app reads a _axigen.<domain> TXT record from public DNS and uses its value as the WebMail URL. This lets your users sign in with just their email address and password — without having to type the server URL by hand.
If the record is not published, the app falls back to the manual server entry screen.
How It Works
The user enters their email address (e.g.,
john.doe@example.com).The app extracts the domain part (
example.com) and looks up the TXT record_axigen.example.comover public DNS.The app prepends
https://to the record's value and uses it as the WebMail URL for all subsequent communication.
The lookup uses public DNS, so the record must be resolvable from outside your network.
Record Format
Field | Value |
|---|---|
Name |
|
Type |
|
Value | The WebMail hostname (e.g., |
TTL | 3600 (1 hour) recommended |
The value is the hostname only — without the https:// scheme. The app prepends it automatically. If your WebMail is on a non-default port, append it to the value (e.g., webmail.example.com:8443).
If multiple TXT records exist at this name, the app uses the first one returned by the DNS resolver. We recommend keeping a single record.
Examples
BIND zone file:
Cloudflare DNS: Add a record with type TXT, name _axigen, content webmail.example.com, TTL Auto.
AWS Route 53: Create a record with name _axigen, type TXT, value "webmail.example.com" (with surrounding quotes), TTL 3600.
Generic registrar / cPanel: Add a TXT record with host _axigen and value webmail.example.com.
Verification
After publishing, allow time for DNS propagation, then verify with:
Expected output:
On Windows, use nslookup -type=TXT _axigen.example.com.
Troubleshooting
The app still shows the manual server entry screen.
DNS may still be propagating. Wait up to the TTL and retry.
Confirm the record name is
_axigen.<your-email-domain>(with the leading underscore).Confirm the value is the hostname only — no
https://prefix.
The app connects to the wrong URL.
The app prepends
https://and connects directly to the value. Make sure the hostname points to your public, HTTPS-enabled WebMail listener (not an internal-only address) and that the certificate is valid.
The record works for some users but not others.
The lookup uses public DNS resolvers. Make sure the record is published in your public-facing zone — split-horizon or internal-only DNS will not work for users outside your network.