getdns-node
getdns-node copied to clipboard
getdnsapi
Node.js bindings of getdns, a modern asynchronous DNS API.
We seem to be having an issue getting RRSIG records when using stub resolver. Command line utilities `getdns_query` and `dig` return the expected RRSIG records. When doing the same through...
The module fails to install with the following error: ``` $ node -v v7.10.1 $ npm install --save getdns > [email protected] install /Users/test/projects/test-getdnsapi/node_modules/getdns > npm run --silent rebuild CXX(target) Release/obj.target/getdns/src/GNContext.o...
- `Nan::MakeCallback`, `Nan::Callback::Call`, and have been deprecated. - The recommended approach is `Nan::AsyncResource`. - Hobbled together the commit from test code and random examples. - Does not seem to affect...
Deprecation warnings (since Node.js v10): - `Nan::MakeCallback(...)` - `Call(...)` on `Nan::Callback` Should either use/pass in `Nan::AsyncResource`, or switch to `Nan::AsyncWorker` (which builds upon `Nan::AsyncResource`). The effect on asynchronous DNS requests...
I've tested it multiple times with multiple versions of the getdns library and the getdns-node module and node (v6, v8 and v9) and it seems as if I send a...
Hi, I want to use this library in a desktop application (electron). Will end users need to install the c++ library? Or is that only required to build? Cheers
While writing tests, a few "magic numbers" popped up. Turns out no all [@getdnsapi/getdns](https://github.com/getdnsapi/getdns) API constants have been implemented in `getdns-node/src/GNConstants.cpp`. - Might more be missing? - How can changes...
The list of records used in the DNSSEC tests for [portal.rootcanary.org](http://portal.rootcanary.org/) should be a good start for both bogus and secure records.
Had two issues where a few "too modern" pieces of javascript code [got pushed to getdns-node](https://github.com/getdnsapi/getdns-node/pull/22). Apart from setting up full a transpilation system, a simpler build/commit time test would...
When running the test suite for v2.0.0-alpha.1, it might happen that a `SIGSEGV` is thrown. The cause is unclear, and it only happens every few hundred test cases or few...