fix(ops/net): fix panic in op_dns_resolve

[kt3k]

Deno.resolveDns() panics with non registered dns record. This PR changes it to JS error.

$ ./target/debug/deno run --unstable -A https://deno.land/posts/v1.7/dig.ts not-found-example.com
error: Uncaught (in promise) Error: no record found for name: not-found-example.com.local. type: A class: IN
    throw new ErrorClass(res.err.message);
          ^
    at processResponse (deno:core/core.js:212:11)
    at Object.jsonOpAsync (deno:core/core.js:229:12)
    at async https://deno.land/posts/v1.7/dig.ts:6:17

closes #9186

[magurotuna]

Thanks so much for the fix! I should have taken this case into account...

I think this is fine for the moment, but in the future, at latest before this API gets stabilized, it should return the cause of the error as precise as it can.
Looking at the other languages, in the case of failure, Golang returns DNSError type, and Node.js returns Error object with these error codes. It would be nice if we returned errors likewise.

[kt3k]

Looking at the other languages, in the case of failure, Golang returns DNSError type, and Node.js returns Error object with these error codes. It would be nice if we returned errors likewise.

Sounds reasonable to me 👍 Let's do that in follow up issues.

[ry]

LGTM