Port forwarding rule triggered when it shouldnt

Started by thelittleblackbird, Today at 09:53:17 AM

Previous topic - Next topic
Today at 09:53:17 AM Last Edit: Today at 10:01:44 AM by thelittleblackbird
Hi all,

I hope i can get some of the collective intelligence about a port forwarding rule, to explain me what i am doing wrong.

I set a port forwarding rule to redirect every DNS request to port 53 NOT addressed to the firewall to be redirected to the firewall itself. I want to avoid that some devices are forced to use other dns server that the default one.

but in the firewall log i can see that the rule is triggered always.

am i doing something wrong? important info, the rule is only triggered by Ipv6 and not ipv4.


Yes, for starters: why is the source "This firewall" - you should have the list of clients that will be forced to use your local DNS there.

See this, point 29 and what is linked there.
Intel N100, 4* I226-V, 2* 82559, 16 GByte, 500 GByte NVME, ZTE F6005

1100 down / 800 up, Bufferbloat A+

fuck!, I feel ashamed of myself.

I promise i checked that for hours and i didnt see anything wrong.

thanks for the help.

For the IPv6 I am not so worried, I only wanted to ahve a rule that could be triggered when one of the device of the network is not behaving "nominally". I dont care if dns over ipv6 are not resolved when not directed to the FW