-
Notifications
You must be signed in to change notification settings - Fork 424
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
AXFR doesn't work due to additional www. lookup #631
Comments
hm, I've never thought of the resolver being used for AXFR. The client, The Resolver on the other hand is meant to resolve single records only, and probably should reject AXFR as a RecordType that can be queried. If there's a bug here, it's probably that the Resolver should just error out on AXFR requests. As an addendum to this, we may have some edge cases around large zones in the current AXFR implementation in the library, there's an existing bug open on the server for large AXFR's, not sure how that applies to the client. |
@bluejekyll thanks for the pointer, the client in the trust-dns crate is a lot closer to what I was looking for! I refactored my code from trust-dns-resolver to trust-dns and got AXFR to work that way. Regardless, is there a reason why the resolver is doing an automatic |
Well, my assumption is that because AXFR isn’t intentionally supported by the resolver, some cname or srv logic was inadvertently triggered. But I didnt look to confirm this. |
Describe the bug
I was trying to implement a zone transfer for a zone that I can transfer with dig, but can't transfer with trust-dns.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Successful AXFR reply
Actual behavior
This log indicates there are actually two lookups
AXFR zonetransfer.me
andAXFR www.zonetransfer.me
. The 2nd one is incorrect, should not happen and causes this function call to fail. I might be missing an option here to disablewww.
lookups, if there is one, please point me to it. :)Version:
Crate: resolver
Version: 0.10.0
The text was updated successfully, but these errors were encountered: