-
Notifications
You must be signed in to change notification settings - Fork 921
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
Access to TSIG key name #7766
Comments
It would not be. I don't think we can currently do what you are asking for, indeed. |
Is this also missing from AXFR question too ? Just trying to setup supermaster axfr between a slave and a master (single IP on each) and steering the notifications and AXFR to the appropriate instance. Notify i can workaround as that can directly target a non standard port, however supermaster does not seem to support that, so steering on dnsdist (or a second IP address, which i am trying to resist) would seem a sensible approach. If you have any alternative suggestions, please let me know. Thanks |
There is no TSIG logic anywhere in dnsdist, as far as I know.
That should work - you can get help with that via IRC or our mailing list. Details are at https://www.powerdns.com/opensource.html |
ok, thanks, |
Is there any work being done on this issue? I really need this functionality... |
Hello Roman, no work is being done on this. We'll consider patches if somebody sends them. Sorry! |
Maybe there's an update on this topic? ) |
Is there any news about this feature? =) |
Maybe you could add this feature? Please :) |
Hello, repeating this question is not useful. This ticket is milestoned "dnsdist-helpneeded", which means we think it's a fine idea, but do not currently plan to work on it. However, if somebody (you?) sends a PR, we will take that very seriously. |
Short description
Allow access to TSIG data from DNSQuestion object
Having access to the TSIG key name for notify ops would be useful
Usecase
To be able to steer notify messages towards distinct pools based on a TSIG key name regex match
Description
dnsdist to make available this information so that it can be used for steering decisions.
No validation / verification desired, just access to the TSIG key name.
I did wonder if this would be in trailing data, however it appears not in initial testing.
Apologies if this is already present and i just did not spot it
Thanks
The text was updated successfully, but these errors were encountered: