-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
doggo supports osx scoped queries on accident, but doesn't report correctly #49
Comments
logikal
changed the title
doggo supports scoped queries on accident, but doesn't report correctly
doggo supports osx scoped queries on accident, but doesn't report correctly
Jul 28, 2022
None of the other cli tools I've checked leak queries to the scoped resolver.
|
To be clear, I like that doggo ends up respecting the scoped queries configuration, but think that it should be explicit/not silently leaking. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I use OSX's DNS configuration for scoped queries. I use this so my work-related private/internal domains are resolved using DNS servers in our infrastructure, but the rest of the internet is resolved using the "normal" resolvers.
It looks like doggo is doing a lookup that respects the scoped query functionality in osx, but it's happening transparently and causing doggo to "lie" about the origin of the answer. This suggests that resolver-specific queries are leaking to other resolvers silently.
doggo reports that the normal resolvers are answering for domains that should be responding with NXDOMAIN, and don't list the resolver for the scoped query at all:
My resolver configuration
The text was updated successfully, but these errors were encountered: