错误的根源是什么:getaddrinfo EAI_AGAIN? [英] What's the source of Error: getaddrinfo EAI_AGAIN?

问题描述

我的服务器今天抛出了这个，这是我从未见过的Node.js错误:

My server threw this today, which is a Node.js error I've never seen before:

Error: getaddrinfo EAI_AGAIN my-store.myshopify.com:443
    at Object.exports._errnoException (util.js:870:11)
    at errnoException (dns.js:32:15)
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:78:26)

我想知道这是否与DynDns DDOS攻击有关，该攻击影响了Shopify和当今的许多其他服务. 此处是有关此的文章.

I'm wondering if this is related to the DynDns DDOS attack which affected Shopify and many other services today. Here's an article about that.

我的主要问题是dns.js的作用是什么?它属于节点的哪一部分?如何在其他域中重新创建此错误?

My main question is what does dns.js do? What part of node is it a part of? How can I recreate this error with a different domain?

推荐答案

如果Firebase Cloud Functions出现此错误，则是由于免费套餐的限制(仅允许Google服务使用的出站网络).

If you get this error with Firebase Cloud Functions, this is due to the limitations of the free tier (outbound networking only allowed to Google services).

升级到火焰或 Blaze 计划使其工作.

Upgrade to the Flame or Blaze plans for it to work.

这篇关于错误的根源是什么:getaddrinfo EAI_AGAIN?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！