-
-
Notifications
You must be signed in to change notification settings - Fork 105
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
Add support for connection re-use by secondary for XFR #145
base: master
Are you sure you want to change the base?
Conversation
Add logging
…ow. Option not yet used.
…e checkconf unit test to support new options
does not allow new queries to be made, the connection is closed. Only existing queries and zone transfers are answered, new ones are rejected by a close of the channel.
Instead of the |
I think having the default on would be good, I thought an option might be useful so it could be disabled in case of interop problems (e.g a legacy XFR implementation behind a proxy). |
Perhaps it should be configurable per upstream then? For example in the tls-auth: declaration? |
*** FOR REVIEW ONLY AT THIS TIME***
xfrd-conn-reuse
(default no) andtcp-idle-timeout
(default 10)xfrd-conn-reuse: yes
the secondary will utilise the existing the mechanisms in place (which are currently only used whenXFRD_MAX_TCP
is exhausted) to re-use connectionstcp-idle-timeout
, which is currently a fixed timeout. A later commit will add support for EDNS0 Keepalive, so the server can signal the timeout to use (as described in draft-ietf-dprive-xfr-over-tls)tpkg\long\testplan-axfr.dir
test, will send separate email about this.