[BUG] Subdomains seem to be ignored for white listed hosts

[boernsen-development]

[BUG] Subdomains seem to be ignored for white listed hosts

[IngoZenz]

it supports only 1 forward per host per IP4 / IP6

[boernsen-development]

I just found a workaround:
Instead of putting !googlevideo.com below *google* put !*googlevideo.com above it. It has to be wildcarded and above.

If there is no deeper issue behind it, I think this issue could be solved by correcting the comments in additionalHosts.txt and possibly change the predefined ordering in it.

[IngoZenz]

yes it seems it works as designed. In your first sample, there was no explicit entry for test.googlevideo.com, therefore it was blocked via the *google* rule hitting first. In your 2nd sample it hits the !*googlevideo.com rule first, thererfor it is whitelisted, whereas e.g. googleads.com would be blocked by *google* rule.

[boernsen-development]

So is !googlevideo.com not considered explicit or is it only considered explicit for googlevideo.com, but not for any sub-domain? I think this is what I misunderstood from:

# PRIORITIES in case of conflicting entries
# 1. Explicit entries without wildcards
# 2. Wildcard entries prioritized along the sequence in this file
# 3. Downloaded blocklist

[IngoZenz]

Exactly... Expicit means that there is an explicit entry for a domain /sub domain

[boernsen-development]

Thanks for clarifying!

Technically, I would say this issue can be closed. Only a few suggestions for additionalHosts.txt I would like to leave here for consideration to avoid confusion for others:

• mention the role of subdomains in the description of priorities as it seems that automatically derived subdomains are neither treated as explicit nor as wildcard
• move the whitelist section of the default file to the top and/or mention that if one wants to whitelist subdomains of matching wildcarded blacklist entries, this has to be done at the top AND using wildcards

[mosajjal]

another question that might be relevant here or needs its own issue: does "forward to custom ip" support wildcards? I'm keen to use this project as a companion piece to my SNI proxy and hard-coding some dns suffixes will save the users a bunch of useless road trips to the server

[IngoZenz]

Today the custom IP forwards do not support wildcards.
What is possible is to change the IP used for filtered hosts - maybe that's an option.

[mosajjal]

yes I saw a few "127.0.0.1" strings hardcoded in the app. would you be open to a PR for a setting to customize that? it'll solve my issue for sure :) could be a good one for some honeypot/fakenet implementations too

[IngoZenz]

You can customize it already today via following dnsfilter.conf settings:

# Returned IP for resolving blocked host
ipV4BlockedHost = 0.0.0.0
ipV6BlockedHost = ::

[mosajjal]

oh nice. yes just saw it and it works flawlessly :) thanks!

[zwrmueller]

Today the custom IP forwards do not support wildcards

Hi,
is it possible to forward 1 host to 2 IPs?

Like:

myhost 192.168.1.21
myhost 192.168.1.22

That example above seems not to work, as (allways) the last entry is used ...

[zwrmueller]

Ok, thanx.
Would love it to see it the other way round, but thanx for quick response.