Configuring Forced Hosts for Subdomain Routing // NodeFlux Docs

Route players connecting via different subdomains (e.g., play.domain.com vs pvp.domain.com) to specific backend servers. ## Steps 1. Ensure your custom domain DNS has CNAME or A records pointing subdomains to your proxy NodeFlux documentation for free Minecraft, Node.js and application hosting.

Route players connecting via different subdomains (e.g., play.domain.com vs pvp.domain.com) to specific backend servers. ## Steps 1. Ensure your custom domain DNS has CNAME or A records pointing subdomains to your proxy

Route players connecting via different subdomains (e.g., play.domain.com vs pvp.domain.com) to specific backend servers. ## Steps 1. Ensure your custom domain DNS has CNAME or A records pointing subdomains to your proxy IP. 2. Open your proxy configuration file (velocity.toml or BungeeCord config.yml). 3. Locate the forced-hosts section. 4. Map subdomains to backend server names: "pvp.mynetwork.com" = ["pvp-server"]. 5. Map default domain: "play.mynetwork.com" = ["lobby-server"]. 6. Save configuration and reload proxy settings. 7. Test joining with different subdomains to verify automatic server routing. ## Notes - Forced hosts allow creating distinct community entry points without needing multiple proxy instances. - Subdomain casing in proxy configuration should be lowercase.