Minecraft Bedrock Hairpin NAT Fails Ping?

RouterOS General
1

This is an odd one. If I add my server LAN IP to the app, the app reports the ping and users online.

But if I use my FQDN which is hairpin-nat’d, the ping stats do not report; yet, I can still connect to the server just fine this way.

Here are the rules I used for hairpin NAT:

/ip/firewall/nat
add action=dst-nat chain=dstnat comment="hairpin 1/3 amp1 udp" \
    dst-address-type=local dst-port=35565-35584 protocol=udp to-addresses=\
    172.16.42.65
add action=dst-nat chain=dstnat comment="hairpin 1/3 amp1 tcp" \
    dst-address-type=local dst-port=35565-35584 protocol=tcp to-addresses=\
    172.16.42.65
add action=masquerade chain=srcnat comment="hairpin 2/3" dst-address=\
    172.16.42.0/24 src-address=172.16.42.0/24
add action=masquerade chain=srcnat comment="hairpin 3/3" out-interface-list=WAN

Any ideas why the ping stats wouldn’t work for the fqdn/hairpin, but they do work for the LAN IP? The “ping” is really just a message sent over the same UDP port as used to connect to the game, and since I can still connect to the game, I can’t really understand why this doesn’t work.

2

If Minecraft does not connect, you can uninstall and reinstall it. Give it a try buddy

3

My post has nothing to do with connecting.

Using a short hostname resolving directly to the internal IP shows pings in the client on the same LAN.

Using a fqdn resolving to the external IP does not show pings in the client on the same LAN.

Due to the hairpin NAT rules I have installed, both the short hostname and fqdn connect to the server just fine. It’s just that the latter doesn’t show pings.