forced_tunnels.json required to resolve host

[PyrusofImpetus]

Describe the bug
When using modflared, I'm unable to access my server by hostname. Other services running on the same server resolve, but not the Minecraft server. When I add the same domain name to the forced_tunnels.json and place in .minecraft/modflared, it does resolve and I'm able to connect. No blocks/errors appear on cloudflared side as far as I can see.

Which version of the mod/game are you using?
1.21.5, modflared 1.3.0 release.79

To Reproduce
Steps to reproduce the behavior:

1. Start game without forced_tunnels.json present
2. Attempt to connect to server
3. Close game, add forced_tunnels.json with server domain name, restart game
4. Connection succeeds.
5. Removing the forced_tunnels.json at this point once again prevents domain resolution

Expected behavior
Modflared should resolve with or without the use of forced tunnels, if it works with forced tunnels.

User error?

[HttpRafa]

Have you added the required TXT DNS entry?

[HttpRafa]

https://github.com/HttpRafa/modflared?tab=readme-ov-file#example-dns-entries

[PyrusofImpetus]

I have, my DNS on cloudflared looks like such:

I've also restarted my tunnel on the host server to make sure it applies the changes.

[PyrusofImpetus]

After being away for a weekend and trying again, modflared now appears to be working. I don't believe I changed anything at all, be it on the client, server, or cloudflare.

Not sure if this can just be marked resolved or if I ran into some odd corner case of a potential legit issue, but I'll update if it crops back up.

[HttpRafa]

Sorry, I completely forgot about this issue. It might have been due to Cloudflare DNS propagation — it’s possible that it just took a bit longer than expected.

[PyrusofImpetus]

That's a good call. I was wondering the same, but had my doubts as I was able to ping the subdomain and get a response quickly. Seems stable enough for now!