Hi everyone!
The dns.resolve tries to send request to only the first nameserver
in /etc/resolv.conf, and if the first nameserver fails to resolve the name,
dns.resolve just returns and doesn't try to send request to the second
nameserver. Is this work-as-design?
Here is an example: the /etc/
On Wednesday, May 4, 2016 at 5:35:40 PM UTC+2, Reshma Roy wrote:
>
> Hi,
>
> I tries to run a nodejs code in a mininet host nodejs code.js and the
> error i gets is follows :
>
> events.js:72
> throw er; // Unhandled 'error' event
> ^
> Error: connect ECONNREFUSED
> at
On Thu, May 5, 2016 at 9:00 AM, Yun Feng Ma wrote:
> Hi everyone!
>
> The dns.resolve tries to send request to only the first nameserver in
> /etc/resolv.conf, and if the first nameserver fails to resolve the name,
> dns.resolve just returns and doesn't try to send request to the second
> nameserv
I saw that post, but did not know how to do that.
On Thursday, May 5, 2016 at 12:04:34 AM UTC-4, Christopher Mina wrote:
>
> Hi.
>
> I'm not familiar with the library, but your code generally look ok.
>
> Check out this StackOverflow post, maybe it's as simple as setting the
> header Content
I am getting array from angular controller like [
'572b2e5d63f338b02afa36b9', '572b3da2034e6370301943bc' ] to node.
Below code is my node
router.get('/purchaserInfo',function(req,res){
console.log(req.query.proID);
var productId = req.query.proID;
var findPurchaserInfo = function(db, callback)
在此输入代码...
在 2016年5月6日星期五 UTC+8上午9:43:50，Ben Noordhuis写道：
>
> On Thu, May 5, 2016 at 9:00 AM, Yun Feng Ma > wrote:
> > Hi everyone!
> >
> > The dns.resolve tries to send request to only the first nameserver in
> > /etc/resolv.conf, and if the first nameserver fails to resolve the name,
> >
