@MattProd Hello!
I have found another problem, in my homelab it does not happen but in the hetzner server it does...
I have a virtual machine with any, any, any... at the IP 192.168.1.100 as the last rule (type dmz)
The problem is that when it is active, the other virtual machines are accessible from the outside, but they cannot browse the internet...
For example, another virtual machine with IP 192.168.1.30 255.255.255.0 192.168.1.1
DNS: 1.1.1.1
Browse the internet as long as the dmz rule of 192..168.1.100... is deactivated.
Note that when the virtual machine cannot navigate and you do a ping, the one that responds is 192.168.1.100.... My idea would be that being in DMZ it captures DNS port 53 and forces it to go through 192.168.1.100 but. .. if I create a new dns rule and point it to 192.168.1.1 and place it above the dmz.... it doesn't work either.