Skip to content
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

ecs question #342

Open
schm0 opened this issue Apr 20, 2023 · 1 comment
Open

ecs question #342

schm0 opened this issue Apr 20, 2023 · 1 comment

Comments

@schm0
Copy link

schm0 commented Apr 20, 2023

Hi!
What does the edns_client_subnet_private actually do?
Does this set some flag in the edns options to inform the (configured in stubby) recursive resolvers
not to send the client subnet to the root servers (or whatever dns server they use)?
Or does this toggle if stubby sends the actual client subnet to the (configured in stubby) recursive resolvers?
If the latter is the case, what subnet is used?
In a typical home network where stubby is running most likely on a router, this would make no sense because it would send the clients private IP address?
I think there is no way to prevent ecs leak when the (configured in stubby) recursive resolver is configured with ecs support.
Except there first case with flag is actually a thing...

@saradickinson
Copy link
Contributor

Hi - it is the first behaviour you describe - it is an instruction to the recursive resolver not to use ESC when resolving the query (so the client subnet doesn't get sent to the authoritative servers upstream). Of course, this only works if the recursive resolver honours the flag, but most 'privacy' servers do. If you want more detail see here: https://datatracker.ietf.org/doc/html/rfc7871#section-7.1.2

Using this option increases privacy but at the potential cost of not getting a geo located answer (which can make accessing web content slower). The stubby default is to use the option.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants