Server not showing up under LAN when specific IP address selected for port

So I am trying to run more than one version of the server in docker. One that is set to creative mode and one that is set to survival mode.

To allow port 19132 to be the default I added a couple of IP addresses to my host. Then I bind a specific IP address to each docker container. When I do this the server does not show up under LAN games. If I do not specify the IP address it shows up fine.

For example...

This command will work fine:
```docker
docker run --name mc-survival --restart=unless-stopped -e EULA=TRUE -v /opt/docker-minecraft/survival:/data -p 19132:19132/udp itzg/minecraft-bedrock-server
```

This command will run the container fine and I can use it if I define it as a server but it does not show up as a LAN game:
```docker
docker run --name mc-survival --restart=unless-stopped -e EULA=TRUE -v /opt/docker-minecraft/survival:/data -p 192.168.94.13:19132:19132/udp itzg/minecraft-bedrock-server
```

I've specified the port in `server.properties`. I also use a `whitelist.json` but that shouldnt matter.

Are there other ports I need to expose on that IP address?

As mentioned the server runs fine. Can connect and use it if I manually specify it. I just want it to show up under LAN games so that my kids can find it easily (and any others I create).

Start by reproducing the two `docker run` commands and comparing their network behavior, then inspect the configured `server.properties`; `whitelist.json` is also mentioned but reported as unrelated. Done means a container bound to `192.168.94.13:19132` appears under LAN games while remaining manually reachable.

Written by the indexing model from the issue text.