-
Notifications
You must be signed in to change notification settings - Fork 7
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
Error on response (-3) by AXFR on TLDs #1
Comments
Thanks for reporting. Fixed on commit 6cbb196 and published on npm with version 0.1.4. Let me know if you have any other issues. |
Hi jpenalbae, thx for your very fast response, but the "bug" is already there. [root@localhost examples]# time dig AXFR gov.ph @dostmis.dost.gov.ph > /dev/null real 0m31.571s dns.resolveAxfr('dostmis.dost.gov.ph', 'gov.ph', function(err, addr) {
}); any idea? [root@localhost examples]# node -v is my node sufficient? thx you! |
Its was my fault. I wasn't expecting DNS requests producing more than one DNS response. Fixed on commit fe6bada and published on npm with version 0.1.5. Please test it and let me know if you have any other problems. |
yeah! all works now! thx a lot for this fast fix! |
Hi,
thx for this nodejs module. On the most by me tested domains it work fine, but i need it to make a AXFR on a TLD and become anytime the -3 errorcode.
this is my code:
var dns = require('dns-axfr');
var util = require('util');
with dig works the AXFR fine:
$ dig AXFR MO @b.monic.MO
...
i dont realy good in speaking DNS like you do it so i cant fix it by myself.
thank you!
The text was updated successfully, but these errors were encountered: