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

middleware: edns0-client-subnet #46

Closed
miekg opened this issue Mar 26, 2016 · 4 comments
Closed

middleware: edns0-client-subnet #46

miekg opened this issue Mar 26, 2016 · 4 comments

Comments

@miekg
Copy link
Member

miekg commented Mar 26, 2016

Add this as middleware?

@miekg
Copy link
Member Author

miekg commented Apr 28, 2016

should possibly check it the ecs payload as passed through the proxy. Also proxy might need an ecs setting that add the clients IP as an ecs payload.

@miekg miekg added priority and removed later labels Apr 29, 2016
@miekg
Copy link
Member Author

miekg commented Apr 29, 2016

Think this is really handy to add soonish, esp when deploying in cloud scenarios when you want to have the IP from the sending vm. Also should fairly easy to add, I think.

@miekg
Copy link
Member Author

miekg commented Apr 30, 2016

For the proxy we could add an ecs option that adds ecs, but finding out what you current address is and which one to add is really hard. We can give it an option: add this address, but that is rather static.

@miekg
Copy link
Member Author

miekg commented Oct 12, 2016

This is fixed by adding helper functions. A generic middleware fix would be harder and adds overhead.

@miekg miekg closed this as completed Oct 12, 2016
sgreene570 pushed a commit to sgreene570/coredns that referenced this issue Dec 11, 2020
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

1 participant