You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've tried experimenting with $dnsrewrite and added an invalid rule: ||example.org^$dnsrewrite=A:NOERROR:127.0.0.1
The result was that the rule was applied, but the response was NXDOMAIN, which is unexpected.
Instead of that, I suggest simply discarding this kind of rules at the moment when they're parsed by urlfilter.
The text was updated successfully, but these errors were encountered:
The thing that is happening is that the parser interprets your input as a shorthand form of a new CNAME, and so it returns the rewrite that tries to resolve the host A:NOERROR:127.0.0.1. That means we have to define what exactly makes a host valid and use that.
I've tried experimenting with $dnsrewrite and added an invalid rule:
||example.org^$dnsrewrite=A:NOERROR:127.0.0.1
The result was that the rule was applied, but the response was NXDOMAIN, which is unexpected.
Instead of that, I suggest simply discarding this kind of rules at the moment when they're parsed by urlfilter.
The text was updated successfully, but these errors were encountered: