-
-
Notifications
You must be signed in to change notification settings - Fork 48
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
Support AXFR transfers to secondaries #579
Comments
Per-user AXFR could be supported by the means of a separate daemon that answers AXFR requests by first authenticating the request, then doing an AXFR internally, then replying to the request. |
I understand that the DNSSEC records are problematic with AXFR and secondary providers. Not sure whether disabling DNSSEC in deSEC is an option, though the goal of deSEC is to promote DNSSEC. |
no way 🤓 |
This topic (redundancy via zone transfer) has become more relevant today due to the DDoS related outage. Please also consider RFC9103 Zone Transfer over TLS when implementing AXFR support. |
Looks like DDoS issues will become more frequent. We are committing to donate 100€ if AXFR support gets implemented sometime before 2024. |
Hi! Just wanting to say that I was considering moving all my domains to deSEC given the wonderful things that it seems to offer, but sadly I need to be able to do AXFR to internal DNS mirrors to be able to have high-availability when transit outages happen. E.g. offices need to be able to print on the printer without internet connectivity. |
I would like to use deSEC as primary while having other secondary DNS services for redundancy.
Please consider adding AXFR support with TSIG.
Thank you.
The text was updated successfully, but these errors were encountered: