Hypixel.net is both their website and mc server adress.

Is it just that https is on port 443 and minecraft is on port 25565?

And if that is the case, can i do something similar by making a reverse proxy have two seperate server blocks for the one domain, with different ports?

    • Blisterexe@lemmy.zipOPEnglish
      48·
      12 days ago

      Good to know i was right, i will now carry this newfound confidence into every subject

          • zzx@lemmy.worldEnglish
            7·
            12 days ago

            Most games use UDP as the latency induced by TCP is unacceptable for games

              • My Password Is 1234@lemmy.worldEnglish
                21·
                12 days ago

                Minecraft is a building game where latency does not matter as much as in shooter games. For example, if your latency is 200 ms, you can play Minecraft smoothly, while in FPS games it is unacceptable 😉

                Edit: In addition, the Minecraft server can use UDP protocol to serve the server status (but only for this purpose and it is not, nor has it ever been used by the game client). In the past, it was used to display the number of players on websites with server listings, but this can be considered deprecated now – today they use the same protocol as the game client.

      • Possibly linux@lemmy.zipEnglish
        9·
        11 days ago

        You are sort of right

        TCP is on layer 4 of the OSI model. Http is layer 7 which runs on top of layer 4 (TCP)

        In sort Minecraft and http are both tcp

      • owsei@programming.devEnglish
        105·
        11 days ago

        TCP is the way that you send information, HTTP is what it means.

        The difference, in your case, is the port. You can’t CAN have TCP and UDP on the same port, but you can’t have the same protocol on the same port.

        edit: I didn’t knew you could have different transfer protocols on the same port, ty!

        • peregus@lemmy.worldEnglish
          10·
          11 days ago

          You can’t have TCP and UDP on the same port.

          Why not? They are 2 completely separated set of ports. You can have a service listening on port 88 TCP while having another listening on port 88 UDP and they never know about each other.

        • undefined@lemmy.hogru.chEnglish
          41·
          12 days ago

          You can’t have UDP and TCP on the same port? I don’t think that makes sense, I have DNS listening on UDP and TCP both on port 53.

  • chiisana@lemmy.chiisana.netEnglish
    561·
    11 days ago

    The amount of confidently incorrect responses is exactly what one could expect from Lemmy.

    First: TCP and UDP can listen on the same port, DNS is a great example of such. You’d generally need it to be part of the same process as ports are generally bound to the same process, but more on this later.

    Second: Minecraft and website are both using TCP. TCP is part of layer 4, transport; whereas HTTP(S) / Minecraft are part of layer 7, application. If you really want to, you could cram HTTP(S) over UDP (technically, QUIC/HTTP3 does this), and if you absolutely want to, with updates to the protocol itself, and some server client edits you can cram Minecraft over UDP, too. People need to brush up on their OSI layers before making bold claims.

    Third: The web server and the Minecraft server are not running on the same machine. For something that scale, both services are served from a cluster focused only on what they’re serving.

    Finally: Hypixel use reverse proxy to sit between the user and their actual server. Specifically, they are most likely using Cloudflare Spectrum to proxy their traffic. User request reaches a point of presence, a reverse proxy service is listening on the applicable ports (443/25565) + protocol (HTTPS/Minecraft), and then depending on traffic type, and rules, the request gets routed to the actual server behind the scenes. There are speculations of them no longer using Cloudflare, but I don’t believe this is the case. If you dig their mc.hypixel.net domain, you get a bunch of direct assigned IP addresses, but if you tried to trace it from multiple locations, you’d all end up going through Cloudflare infrastructure. It is highly likely that they’re still leaning on Cloudflare for this service, with a BYOIP arrangement to reduce risk of DDOS addressed towards them overflow to other customers.

    In no uncertain terms:

    1. Hypixel.net has Cloudflare DNS for their domain.
    2. For their website, it has orange cloud enabled to proxy traffic through CF’s global CDN and DDOS protection service.
    3. For their Minecraft server, they advertise mc.hypixel.net, but also have a SRV record for _minecraft._tcp.hypixel.net set for 25565 on mc.hypixel.net
    4. The mc.hypixel.net domain has CNAME record for mt.mc.production.hypixel.io. which is flattened to a bunch of their own direct assigned IP addresses.
    5. Traceroute towards those direct assigned IP addresses goes through Cloudflare infrastructure but final destination is obscured, just like their website, to protect them from DDOS attacks.
    • SteveTech@programming.devEnglish
      12·
      11 days ago

      TCP and UDP can listen on the same port, DNS is a great example of such. You’d generally need it to be part of the same process as ports are generally bound to the same process

      They don’t even need to be the same process. I’m pretty sure that’s just a common practice if something needs both protocols, but there’s nothing stopping you from having a web server on TCP 443 and a VPN server on UDP 443. Ports are an abstraction brought by each protocol, they aren’t in anyway related.

    • Bottabottabotta@lemmy.worldEnglish
      3·
      12 days ago

      Does Bedrock support SRV records yet? I honestly haven’t checked in a year or two, but I tried to use SRV records to host a survival game and creative game on different ports but found out it didn’t quite support them yet where as Java edition did.

  • Flax@feddit.ukEnglish
    131·
    12 days ago

    Minecraft allows for SRV records. It’s pretty nifty.

  • just_another_person@lemmy.worldEnglish
    101·
    12 days ago

    DNS A record points to an IP destination. Ports are then handled by the requests for a specific port thing.

    Example: A record for www.dududu.com points to IP 1.2.3.4, but different service ports are listening there to pick up different traffic.

    • Blisterexe@lemmy.zipOPEnglish
      2·
      12 days ago

      Thanks, that’s what i figured.

      I got confused by so many game servers using seperate domains for the site and server, i assumed there was a good reason for that

      • Lucy :3@feddit.orgEnglish
        3·
        12 days ago

        Maybe most smaller ones have hosted both things separately, e.g… with a dedicated minecraft server hoster and a common website-building+hosting service, and don’t want to run an extra server for a proxy just for this.

        With bigger servers (eg. Hypixel, 2b2t) or selfhosted servers (eg. mine), everything is on the same physical (or virtual) machine anyway and therefore everything has the same address, so you wouldn’t even need a proxy.

      • catloaf@lemm.eeEnglish
        1·
        12 days ago

        Flexibility. Maybe they get a hosting package that includes domain registration and hosting, but they can’t put anything else under that name.

  • Droolio@feddit.ukEnglish
    9·
    12 days ago

    Don’t forget, you can also use SRV records to point a domain to another target, where you can also omit the port number. So connecting to server.org say, can point to mc.server.org:25565 under the hood.

    This prolly isn’t what hypixel are doing as everything’s likely on the same network and their router/firewall is just forwarding traffic onto different machines, but SRV is one way to redirect a minecraft connection (and you could combine the technique with subdomains).

    • bulwark@lemmy.worldEnglish
      3·
      12 days ago

      This is how I set up my reverse proxy and it works really well with wildcard SSL certs. Only need one certificate for as many sites as I want!

      • Oisteink@lemmy.worldEnglish
        1·
        12 days ago

        Or you can use something like caddy that will set up certs automatically using tls-alpn-01 challenge, so no need for dns challenge .

        • bulwark@lemmy.worldEnglish
          2·
          12 days ago

          I haven’t tried caddy but I’ve heard good things. I’ve used nginx in the past. I’m currently using Traefik and have been for a few years now. Once it’s set up its pretty great.

          • iggy@lemmy.worldEnglish
            1·
            11 days ago

            Caddy can do both. If you’re using a wildcard already, stick with it. In fact, I’d say it’s more prudent to use wildcards (with DNS challenges) than http challenges.Then you aren’t listing all of your domains in letsencrypt’s public database for everyone to see. Nobody needs to know you’ve got a site called bulwarksdirtyunderpants.bulwark.ninja

    • 4am@lemm.eeEnglish
      31·
      12 days ago

      You cannot specify ports in a DNS A or AAAA record. www.example.com cannot resolve to 1.2.3.4:443 and app.domain.com cannot resolve to 1.2.3.4:5555

      If the application (be it a game or whatnot) supports it, SRV records can identify a port for a hostname. So, you could have minecraft1.domain.com and an SRV record to specify port 25565, and minecraft2.domain.com SRV 25566.

      This means you can have multiple Minecraft servers with the same IP address, but you won’t need to give people the port numbers to remember; the hostname allows the game to look up the port via the SRV record.

      This is great for selfhosters because we generally only get one IP (until they rollout IPv6; probably half the reason they don’t)

      • foggy@lemmy.worldEnglish
        1·
        12 days ago

        I didn’t say to specify a port in the DNS. I just said that it is a way that we can resolve a resource.

        In the case of ports we’d configure it through whatever webserver (Apache, nginx, traefik, whatever) configs necessary on that machine. The DNS in this scenario would only be for the machines IP where our webserver then routes traffic to different ports.

        I was accounting for both valid setups.