
      <p>We tested Traefik for TCP/UDP routing to map <code>subdomain → container</code>. While TCP (Java) was fine, UDP (Bedrock) proved fragile and added operational complexity.</p>

      <h2>What we tried</h2>
      <ul>
        <li>Traefik entrypoints for <code>:25565/tcp</code> and <code>:19132/udp</code></li>
        <li>Docker labels for dynamic routers/services per container</li>
        <li>OVH firewall rules to allow UDP 19132+</li>
      </ul>

      <h2>What we shipped</h2>
      <ul>
        <li>Per-server A record → node IP</li>
        <li>Per-server SRV record → service <code>_minecraft._tcp</code> (Java) or <code>_minecraft._udp</code> (Bedrock) with the correct host port</li>
      </ul>

      <h2>Why SRV won</h2>
      <ul>
        <li>Simpler mental model: domain points directly to the node + port</li>
        <li>Less moving parts; easier debugging; works great with multiple nodes</li>
      </ul>

      <h2>Gotchas</h2>
      <ul>
        <li>Cloudflare: SRV targets must be <em>hostname</em> (we create matching A)</li>
        <li>Do not proxy Minecraft over Cloudflare; keep records unproxied</li>
      </ul>
    

GlitchNode Blog

DNS & Routing: From Traefik UDP to Cloudflare SRV

What we tried

What we shipped

Why SRV won

Gotchas