It turns out that that queries ".", which is an empty string in the packet, which throws an error (but shouldn't).
This is really a dns-suite.js issue, but I'll file it hear for now since I'm better at tracking these issues.
However, I think what should be returned is not an empty array but rather an NXDOMAIN
```bash
dig +trace coolaj86.com @ns1.coolaj86.com
```
It turns out that that queries ".", which is an empty string in the packet, which throws an error (but shouldn't).
This is really a `dns-suite.js` issue, but I'll file it hear for now since I'm better at tracking these issues.
However, I think what should be returned is not an empty array but rather an `NXDOMAIN`
Partial fix in digd.js#v1.2.2, dig.js#v1.3.8, and dns-suite.js#v1.2.11 - no longer causes a crash (though I'm not sure if the exactly correct response is returned)
dig.js '' @ns1.coolaj86.com
Partial fix in `digd.js#v1.2.2`, `dig.js#v1.3.8`, and `dns-suite.js#v1.2.11` - no longer causes a crash (though I'm not sure if the exactly correct response is returned)
```
dig.js '' @ns1.coolaj86.com
```
It turns out that that queries ".", which is an empty string in the packet, which throws an error (but shouldn't).
This is really a
dns-suite.jsissue, but I'll file it hear for now since I'm better at tracking these issues.However, I think what should be returned is not an empty array but rather an
NXDOMAINPartial fix in
digd.js#v1.2.2,dig.js#v1.3.8, anddns-suite.js#v1.2.11- no longer causes a crash (though I'm not sure if the exactly correct response is returned)