-
Notifications
You must be signed in to change notification settings - Fork 251
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
dnsproxy with configuration DoT, forward IP #7
Comments
Well, it makes sense as |
Can it forge package to change IP ? |
In order for your DNS server to see the real the real client IP, you'll need to spoof the source address in the UDP packet (which is hard by itself). The second problem with that is that in this case the response will be sent not to I've got another idea that might work, though. There is a EDNS Client Subnet extension which allows indicating the client subnet to the upstream DNS server. Maybe if To test it add this code to https://github.com/AdguardTeam/dnsproxy/blob/master/proxy/proxy.go#L224
|
I tried like that :
Without success |
Does your local DNS support ECS? |
Oh, that's not ECS support, this looks as this is simply a part of the resolver description. Btw, on a side note, full DOH/DOT support will be in the next version of AdGuard Home: |
Hum ok, i gonna ask pi-hole to support ECS so |
pi-hole use dnsmasq which one seems supporting EDNS |
I guess I might've been unclear. All modern DNS servers support EDNS, that's not the point. What I mean by supporting ECS is somehow indicating it in the interface/logs. I've outlined the idea it here: AdguardTeam/AdGuardHome#558 |
Ok sorry, i think we can close this :-) |
Hello,
I run dnsproxy like that :
dnsproxy -p 5353 --tls-port=853 -u 127.0.0.1:53 --tls-crt=/fullchain.pem --tls-key=privkey.pem
But my internal DNS server (127.0.0.1) see request coming from 127.0.0.1 instead original IP, is it possible to fix that ?
The text was updated successfully, but these errors were encountered: