On Sat, May 5, 2012 at 7:07 PM, Schakko <[email protected]> wrote: > Hello everybody, > I am trying to do a manually IPv4 DNS resolve (because > of https://groups.google.com/forum/?fromgroups#!topic/nodejs/GDeSo3zu1eM) in > a forked process which should be easy (https://gist.github.com/2603955). > > Everytime I do this in a forked process (not in the main process, that > works!), the callback functions of dns.resolve(), dns.resolve4() or > dns.lookup() won't be called. > Fun fact: Wireshark shows that the DNS request and the response between > client and server has been done. > But: The client produces an ICMP message (Type 3 = Destination unreachable, > Code 3 = Port unreachable) which marks the DNS request as failed and so > propably won't be passed from the operating system to node.js. > > Running the forked process with setsid option or running the server script > as root user does not have any influence. > Firewall is deactivated > No SELinux > Every other program can resolve the DNS addresses, so I assume it is a > node.js specific problem > > > I can reproduce this behaviour with Ubuntu 10.04 and node.js > > v0.7.6 > v0.6.6 > v0.6.17 > > What I am doing wrong?
Does it also happen when your test case only uses core modules? -- 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
