Chris Buijs
Chris Buijs
@charlieporth1 That is very similar what I do today, I have front-ended RouteDNS with NGINX. Using different "ports" listening with RouteDNS and let NGINX make the decision which port connect...
This works great! One thing, which is actually more related to `routers` in general. For logging purposes, could there be an identifier which route/rule was selected/used, e.g. the argument(s) that...
Perhaps additional on logging, when a query comes in on `doh`, the doh-path is added to the log-output? Today it shows this: `msg="received query" addr="[::]:443" client="192.168.1.10" id=doh-listener protocol=doh qname=www.google.com.` Add...
Looks like it is working as expected, great! On the routes logging, is seems that the field/info for the `type` (without 's') one is missing, `types` is in there.
Got it, cool. Thanks!
Running this now for more then 20 hours straight without any issues. Looking great. My thumbs up for the merge.
Works as expected, please merge if not done already.
Not a strong one, but it makes duplicated instances less for example. One that I would use is to resolve local domains, do a "replace" action adding a local (search...
It doesn't have to be mutual exclusive or unique, it is fine to answer multiple answers (but you can max it for example to the 10 first ones to not...
Will check it out, returning the first entry should suffice for most applications anyway.