Routing Nintendo Switch Minecraft Bedrock to a Local Server Using BedrockConnect and Pi-hole DNS Overrides

Nintendo Switch routed through a Pi-hole DNS box to a local BedrockConnect Docker host

Minecraft Bedrock on Windows, Android, and iOS lets you type in a server address. The Nintendo Switch edition does not. Console policy removes the Add Server button and leaves players with a short list of Featured Partner servers, so a private family server on your LAN is invisible to the console even though every other device in the house can join it.

There is a clean workaround that needs no console modification. When a player taps a Featured Server button, the Switch asks your network's DNS resolver for that server's public hostname. If your own resolver answers with the address of a local BedrockConnect proxy, the button opens a server menu you control. This guide builds that setup with a Docker container and one Pi-hole DNS rule. If you want the family story behind it, I wrote it up in Hijacking the Galaxite Button to Put Family Minecraft on a Nintendo Switch.

<!-- more -->

Prerequisites

The setup depends on you controlling DNS for the whole LAN, so confirm each of these before you start:

  • A LAN DNS resolver you control, such as Pi-hole or any dnsmasq-based server, handed out to clients by DHCP.
  • A Docker host with a static IP address (written below as <docker-host-ip>).
  • A running Minecraft Bedrock dedicated server that listens on UDP port 19133 instead of the default 19132.
  • A Nintendo Switch on the same local Wi-Fi network.

The port swap matters. The Switch always connects on UDP 19132, so the BedrockConnect proxy takes that port and the real server steps aside to 19133. If your server currently uses the default, change SERVER_PORT to 19133 and publish 19133:19133/udp in its Compose file, then restart it.

Step 1: Deploy the BedrockConnect Proxy Container

BedrockConnect is a small proxy that presents a server selection menu to clients that cannot type an address. Create a project folder at /path/to/git/bedrockconnect and add this docker-compose.yml:

services:
  bedrockconnect:
    image: strausmann/minecraft-bedrock-connect:2
    container_name: bedrockconnect
    environment:
      - NODB=true
      - CUSTOM_SERVERS=/config/custom_servers.json
      - FETCH_FEATURED_IPS=true
    dns:
      - 1.1.1.1
      - 8.8.8.8
    volumes:
      - ./custom_servers.json:/config/custom_servers.json:ro
    ports:
      - "19132:19132/udp"
    restart: unless-stopped

Three settings carry the weight here. NODB=true and CUSTOM_SERVERS tell BedrockConnect to skip its database and read your own server list from the mounted file. FETCH_FEATURED_IPS=true makes it look up the real public addresses of the Featured Servers. The dns: entries give the container a public resolver instead of your Pi-hole. Without them, the proxy would ask your resolver about a hostname you are about to override, get its own address back, and loop. With them, kids can still join a real public lobby from the same menu.

Step 2: Configure the Server List

Add a custom_servers.json next to the Compose file so your family server shows at the top of the menu:

[
  {
    "name": "Family Bedrock Server",
    "iconUrl": "https://example.com/icon.png",
    "address": "<docker-host-ip>",
    "port": 19133
  }
]

Note that the port here is 19133, the real server. Start the proxy with docker compose up -d and watch docker compose logs -f bedrockconnect for a startup line confirming it is listening.

Step 3: Configure Pi-hole DNS Interception

Now point one Featured Server hostname at the proxy. Create /etc/dnsmasq.d/10-minecraft-switch.conf on the Pi-hole machine with a single rule:

address=/play.galaxite.net/<docker-host-ip>

Reload the resolver so the rule takes effect:

pihole restartdns

Pi-hole only reads extra dnsmasq files if that option is enabled. In recent versions it is under Settings, All Settings, Miscellaneous, as the option to load /etc/dnsmasq.d/. From any computer on the LAN, run nslookup play.galaxite.net and confirm the answer is your Docker host.

Step 4: Check the Switch Network Settings

The Switch must actually use your Pi-hole. If DHCP hands out your resolver, the console picks it up automatically. If you set DNS by hand on the console, open Settings, Internet, your network, Change Settings, and enter the Pi-hole address as the primary DNS and leave Secondary DNS empty. A public resolver such as 1.1.1.1 or 8.8.8.8 there can bypass your override some of the time.

Also confirm that nothing on the Docker host blocks UDP 19132 inbound. From another machine, nc -vzu <docker-host-ip> 19132 is a quick check, though UDP tests are only a hint, so the real proof comes in the next step.

Step 5: Test the Handshake and Connection

Launch Minecraft on the Switch, open the Servers tab, and tap the Galaxite button. Instead of the public lobby, you should see the BedrockConnect menu with Family Bedrock Server listed first. Select it, and the proxy hands your console the address and port of the local world. A few seconds later you are standing in it.

If the Galaxite button still opens the public server, the console is probably using a cached or different resolver. Toggle Airplane Mode on the Switch to flush its DNS cache, then re-run the nslookup test from Step 3.

Hardware & Gear Used in This Guide

  • Nintendo Switch OLED console running Minecraft Bedrock Edition.
  • Wi-Fi 6 access point on the home LAN.
  • Proxmox-hosted Docker host (Ubuntu guest) running BedrockConnect and the Bedrock dedicated server.
  • Raspberry Pi running Pi-hole as the LAN DNS resolver.

What You Can Do Next

Add custom icons for each world so the menu is easier for kids to scan, or add more entries to the server list for a creative world and a survival world. You can also restrict inbound UDP 19132 and 19133 to your LAN with a firewall rule so the proxy is never reachable from the internet. Finally, consider a second Pi-hole for redundancy, since the whole trick depends on DNS staying up.

Later,
     SteveO