DNS and hostnames

Vesicle uses one Matrix server_name and four satellite hostnames. Set global.serverName in Helm (for example matrix.example.com). When route or ingress hosts are empty, the chart derives the rest.

Role	Hostname	Purpose
Homeserver	<serverName>	Client-server API, federation, well-known
Account	account.<serverName>	Matrix Authentication Service (MAS)
Chat	chat.<serverName>	Element Web
Admin	admin.<serverName>	Element Admin
Calls	mrtc.<serverName>	Matrix RTC authorisation and LiveKit SFU

Create DNS records for each name and point them at the ingress / Gateway address.

Homeserver behaviour

• GET / on the homeserver host redirects to Element Web (chat.<serverName>) when gateway.route.rootRedirect is enabled.
• /_matrix, /_synapse, and /.well-known stay on the gateway.
• Element Admin discovers the homeserver via https://<serverName>/.well-known/matrix/client.

server_name is part of every Matrix user ID. Changing it later is a migration, not a DNS-only update. Choose the production name before the first real users join.