Blocking a host also blocks DNS resolving

[seniordevel]

I created a rule to block a host, e.g.
.*doubleclick\.net

The host is blocked as expected, but now I am completely unable to resolve the host, since DNS resolution -referring this host - is blocked too.
This behaviour contradicts any known firewall behaviour, for example known from iptables for many decades.

[gustavo-iniguez-goya]

Hi @seniordevel ,

If you created a rule to block that domain name, the rule will be applied to any port.
If you want to allow DNS resolution, you'll have to create a rule to block connections to that domain + allowed destination ports ( for example: [x] To this port: ^(80|443)$)

Bear in mind that nor iptables and nor nftables block connections by process or md5 for example, so behaviour may differ from those or any other apps.