How to add max timeout on DNS query?

[yhojann-cl]

For example, the request a MX query is a very very long response, how to set by example 8 seconds to stop connection and launch the error callback?

[silverwind]

Good question. I don't think there's any timeout control exposed in dns yet, which looks like an oversight. We should evaluate adding it.

As for a possible implementation, instead of adding another static method (like the ill-conceived dns.setServers), I'd like to see a timeout added to option objects of lookup and resolve* (need to add object parameter support).

[bnoordhuis]

dns.lookup() calls getaddrinfo(3) under the hood, there is no real way to cancel that once started.

The other dns functions use c-ares. It has a configurable timeout but unfortunately that is effectively a per-process setting. It can be configured on a per-channel basis but node uses only one channel for efficiency reasons.

[yhojann-cl]

http://stackoverflow.com/questions/10777657/node-js-dns-lookup-how-to-set-timeout

The stop async thread realy stop the parent process?

[geoffreak]

Any chance of this getting added? It seems like such a simple feature to wait this long.

[silverwind]

@geoffreak try https://github.com/mafintosh/dns-socket.

[Trott]

It seems like this is a feature request that is unlikely to be implemented, at least not without changes in upstream c-ares. I'm going to close this, but please comment (or re-open) if you think that it should stay open.