Hijacking the Galaxite Button to Put Family Minecraft on a Nintendo Switch (Part 2)

A Nintendo Switch tricked by Pi-hole DNS into rerouting an official partner button directly to a private Proxmox Minecraft server

     Picking up from Part 1, I had a brand-new private Minecraft server running on Proxmox, two eager kids sitting on the couch with their Nintendo Switches, and a missing button. Connecting to a private server on a PC is trivial; you just type the IP and click join. On the Switch, however, players are locked inside a strict walled garden. The custom server button is completely missing, replaced by a fixed menu of seven commercial partner servers - names like The Hive, CubeCraft, and Galaxite. Explaining console restrictions to kids who just want to tame virtual wolves together is a unique parenting challenge; especially when the server they want is humming away thirty feet downstairs in our basement.

     I was not about to let a missing text box defeat the homelab, so I teamed back up with my AI assistant to trick the Nintendo Switch into talking to our local Proxmox container. The secret to outsmarting a locked console is remembering that even the strictest walled garden still has to ask your local network for directions. The Switch refuses to let a player enter an arbitrary IP address, but tapping an official partner button forces the console to send a standard DNS query to locate that server on the internet. That gave me the exact opening I needed for a little network misdirection.

     Since all Wi-Fi traffic in our house passes through a local Pi-hole DNS resolver, I decided to commandeer one of those official buttons for the family. I added a custom DNS routing rule inside Pi-hole that intercepts lookups for Galaxite's domain (`play.galaxite.net`) and quietly replies with the local IP address of my Proxmox server instead. As far as the Switch is concerned, it is phoning home to an approved cloud network; in reality, my local DNS resolver is politely ushering traffic straight down to the basement.

     As I dug into the network traffic, however, I realized a raw DNS redirect is only half the puzzle. When the Switch taps a featured server button, it expects a specific handshake on standard Bedrock port 19132 and gets picky about UDP and TCP NetherNet port bindings. To solve that, my AI agent deployed a lightweight proxy container called BedrockConnect right alongside our game server. Because the Switch is hardcoded to knock on port 19132, I assigned port 19132 to BedrockConnect and shifted our family Minecraft server to port 19133. When the DNS rule redirects the Switch to Proxmox, BedrockConnect answers on port 19132, presents a clean menu, and hands the connection across to our private world on port 19133. Even better, I had the agent enable direct public IP resolution in the proxy (`BC_FETCH_FEATURED_IPS=true`); that way, if the girls ever want to visit a real public server, the proxy routes them around my DNS rule without getting caught in a loop.

     There is a quiet satisfaction in watching a locked console ecosystem yield to a couple of clever networking rules. When we called the girls back over to test it out, they fired up their Nintendo Switches, opened the Servers tab, and tapped the big official Galaxite button they had been staring at earlier. Instead of a crowded commercial lobby full of strangers, the screen blinked and dropped both of them straight into our private family world. No hardware modifications, no monthly subscriptions, and zero complicated connection steps for the kids to remember; they just pick up their handhelds, tap one button, and build safely together on our own hardware - which made the extra networking detour worth every single minute.

     If you want to build this setup step by step, check out Routing Nintendo Switch Minecraft Bedrock to a Local Server Using BedrockConnect and Pi-hole DNS Overrides on By Design Won't Fix.

Later,
     SteveO