On Friday, 1 February 2013 11:43:49 UTC, Ben Noordhuis wrote: > > Right, I can reproduce it now. > > It seems to be a c-ares quirk (the DNS resolver library we use). If a > server replies with SERVFAIL, c-ares retries the query up to four > times, then gives up with an ARES_ECONNREFUSED error. > > I don't think there is much we can do about that. Maybe you can bring > it up on the c-ares mailing list. >
Ok - I've had a look through the c-ares documentation and found the cause of this, basically SERVFAIL, NOTIMP, REFUSED and any mismatched questions are discarded by c-ares unless ares_init_options() is called with the ARES_FLAG_NOCHECKRESP flag set. See http://c-ares.haxx.se/ares_init.html I've no idea what they were thinking making this the default. I can't see any benefit to this unless you have broken nameservers in /etc/resolv.conf. In all other cases this is simply O(retries) overhead as you simply get the same result back for each retried query before receiving the ECONNREFUSED result. I'd prefer to get the relevant error back immediately (which would also be 3x faster). What do you think? Regards, Steve. -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
