u/Sampl3x

If you're using Fastmail with custom DNS and want to point supported services at their EU infrastructure, this is the generic setup I ended up with.

Replace yourdomain.com with your own domain.

MX — ROOT DOMAIN
Domain                           Data
-------------------------------  -------------------------------------------
yourdomain.com                   10 eu1-smtp.messagingengine.com
yourdomain.com                   20 eu2-smtp.messagingengine.com

Allows you to receive email at standard addresses, e.g. user@yourdomain.com


MX — WILDCARD SUBDOMAINS
Domain                           Data
-------------------------------  -------------------------------------------
*.yourdomain.com                 10 eu1-smtp.messagingengine.com
*.yourdomain.com                 20 eu2-smtp.messagingengine.com

Allows you to receive email at subdomain addresses, e.g. foo@user.yourdomain.com


A — MAIL
Domain                           Data
-------------------------------  -------------------------------------------
mail.yourdomain.com              204.75.18.65

Allows you to use http://mail.yourdomain.com as a Fastmail login redirect.
At the time of testing, this IP hit Fastmail's Amsterdam frontend.


MX — MAIL
Domain                           Data
-------------------------------  -------------------------------------------
mail.yourdomain.com              10 eu1-smtp.messagingengine.com
mail.yourdomain.com              20 eu2-smtp.messagingengine.com

The A record for mail.yourdomain.com overrides the wildcard MX lookup.
These MX records preserve mail delivery to addresses such as:
foo@mail.yourdomain.com


SRV — MAIL CLIENT DISCOVERY
Domain                           Data
-------------------------------  -------------------------------------------
_submission._tcp.yourdomain.com  0 0 0 .
_imap._tcp.yourdomain.com        0 0 0 .
_pop3._tcp.yourdomain.com        0 0 0 .

_submissions._tcp.yourdomain.com 0 1 465 eu-smtp.fastmail.com
_imaps._tcp.yourdomain.com       0 1 993 eu-imap.fastmail.com
_pop3s._tcp.yourdomain.com       10 1 995 eu-pop.fastmail.com
_jmap._tcp.yourdomain.com        0 1 443 eu-api.fastmail.com
_autodiscover._tcp.yourdomain.com
                                 0 1 443 eu-autodiscover.fastmail.com

Allows compatible email clients to automatically discover the EU Fastmail endpoints.


SRV — CARDDAV
Domain                           Data
-------------------------------  -------------------------------------------
_carddav._tcp.yourdomain.com     0 0 0 .
_carddavs._tcp.yourdomain.com    0 1 443 eu-carddav.fastmail.com

Allows CardDAV clients to automatically discover the EU CardDAV endpoint.MX — ROOT DOMAIN
Domain                           Data
-------------------------------  -------------------------------------------
yourdomain.com                   10 eu1-smtp.messagingengine.com
yourdomain.com                   20 eu2-smtp.messagingengine.com

Allows you to receive email at standard addresses, e.g. user@yourdomain.com


MX — WILDCARD SUBDOMAINS
Domain                           Data
-------------------------------  -------------------------------------------
*.yourdomain.com                 10 eu1-smtp.messagingengine.com
*.yourdomain.com                 20 eu2-smtp.messagingengine.com

Allows you to receive email at subdomain addresses, e.g. foo@user.yourdomain.com


A — MAIL
Domain                           Data
-------------------------------  -------------------------------------------
mail.yourdomain.com              204.75.18.65

Allows you to use http://mail.yourdomain.com as a Fastmail login redirect.

At the time of testing, this IP hit Fastmail's Amsterdam frontend.


MX — MAIL
Domain                           Data
-------------------------------  -------------------------------------------
mail.yourdomain.com              10 eu1-smtp.messagingengine.com
mail.yourdomain.com              20 eu2-smtp.messagingengine.com

The A record for mail.yourdomain.com overrides the wildcard MX lookup.
These MX records preserve mail delivery to addresses such as:
foo@mail.yourdomain.com


SRV — MAIL CLIENT DISCOVERY
Domain                           Data
-------------------------------  -------------------------------------------
_submission._tcp.yourdomain.com  0 0 0 .
_imap._tcp.yourdomain.com        0 0 0 .
_pop3._tcp.yourdomain.com        0 0 0 .

_submissions._tcp.yourdomain.com 0 1 465 eu-smtp.fastmail.com
_imaps._tcp.yourdomain.com       0 1 993 eu-imap.fastmail.com
_pop3s._tcp.yourdomain.com       10 1 995 eu-pop.fastmail.com
_jmap._tcp.yourdomain.com        0 1 443 eu-api.fastmail.com
_autodiscover._tcp.yourdomain.com
                                 0 1 443 eu-autodiscover.fastmail.com

Allows compatible email clients to automatically discover the EU Fastmail endpoints.


SRV — CARDDAV
Domain                           Data
-------------------------------  -------------------------------------------
_carddav._tcp.yourdomain.com     0 0 0 .
_carddavs._tcp.yourdomain.com    0 1 443 eu-carddav.fastmail.com

Allows CardDAV clients to automatically discover the EU CardDAV endpoint.

A few notes:

• eu1-smtp.messagingengine.com and eu2-smtp.messagingengine.com are used for inbound MX.
• eu-smtp.fastmail.com, eu-imap.fastmail.com, eu-pop.fastmail.com, etc. are the regional client endpoints.
• 204.75.18.65 is Fastmail's EU redirect frontend; in my testing it returned X-Frontend: ams-frontend-01.
• The records with target . intentionally disable the non-TLS discovery service.
• I would still keep Fastmail's normal SPF and DKIM records unless Fastmail explicitly documents EU-specific replacements, since those are authentication records rather than client-routing records.

I tested the regional endpoints with DNS lookups, openssl s_client, and curl, and they were terminating on Fastmail infrastructure in Amsterdam.

Hi all,

We’re currently running our full Citrix backend on Windows Server 2019:

• 2x DDC
• 2x StoreFront
• 2x FAS

Environment is currently on CVAD 2402 CU3 LTSR.

Since 2402 CU3 doesn’t support Windows Server 2025, the plan is to first upgrade the Citrix environment to CVAD 2503 CU1 LTSR. That part is pretty straightforward.

The bigger question is the OS migration.

As far as I know, in-place OS upgrades for Citrix infrastructure servers are still not supported, so I’m wondering what the best practice is nowadays.

Is the recommended way still to build new Server 2025 machines alongside the existing servers, add them to the environment, move the roles/configuration over, and then remove the old 2019 servers?

We have close to 1,000 VDIs and quite a lot of Machine Catalogs and Delivery Groups, so I’d really like to keep downtime and risk to a minimum.

For the DDCs in particular, would you simply add two new Server 2025 DDCs to the existing Site, update VDAs/policies if needed, and then decommission the old controllers? This give me a headache bcause i have to open extra firwall rules regarding Netscalers in the DMZ.

And for StoreFront and FAS, same idea: build new, join/migrate, test, then remove the old servers?

Has anyone done a similar 2019 → 2025 migration in a larger Citrix environment?

Would be interested to hear what migration order you used and if there were any gotchas.

Hi all,

I want to switch from Terramaster OS (TOS) to Unraid because the lack of updates from Terramster and would like some advice before I set things up.

My hardware:

• TerraMaster F4 SSD (4x NVMe slots, no HDD support)
• Goal is a fully NVMe-only setup (4 x Crucial 2TB NVME)

After reading multiple Reddit threads and forum posts, I’m a bit confused about the “right” approach in Unraid.

From what I understand:

• Using NVMe/SSD in the main array is not recommended (no TRIM, potential long-term performance issues)
• Most people suggest using pools instead of the array
• ZFS (RAIDZ1 or mirrors) seems to be the preferred option for NVMe-only setups

My questions:

1. Is it correct that for an NVMe-only system, I should avoid the array completely and just use a ZFS pool or can i use XFS?
2. Does Unraid still require a disk in the array, or is a pool-only setup fully supported nowadays?
3. For 4x NVMe, what would you recommend:
   • RAIDZ1?
4. Are there any downsides I should be aware of when running apps/VMs/shares entirely on a ZFS pool?
5. Is there any valid use case where putting NVMe drives in the array would still make sense?

Use case:

• Docker containers (Plex, *arr stack, uptimekuma, etc.)
• General storage (no massive bulk data, media)

I’m mainly aiming for a quiet and reliable setup, maximum capacity, redundacy.

Any best practices or “gotchas” specific to NVMe-only builds on Unraid would be greatly appreciated.

Thanks you adnvance!

Having a F4 SSD nas im must say Terramaster is realy slow with bringing out new firmware updates. A package like Docker is realy an old version, no security updates. No new firmware out now for more then 5 months now for TOS6 :(

With Synology you see a lot more updates.