FetchError: request failed, reason: getaddrinfo EAI_AGAIN

[doug-wade]

I left my bot up and running for about 15 days, and after about 2 weeks of polling every 10 minutes, I started to get this error on every request:

FetchError: request to https://lemmy.world/api/v3/post/list?type_=Subscribed&auth=<redacted> failed, reason: getaddrinfo EAI_AGAIN lemmy.world
    at ClientRequest.<anonymous> (/home/doug/workspace/Lemmy-Mega-Bot/node_modules/node-fetch/lib/index.js:1505:11)
    at ClientRequest.emit (node:events:518:28)
    at TLSSocket.socketErrorListener (node:_http_client:495:9)
    at TLSSocket.emit (node:events:518:28)
    at emitErrorNT (node:internal/streams/destroy:169:8)
    at emitErrorCloseNT (node:internal/streams/destroy:128:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  type: 'system',
  errno: 'EAI_AGAIN',
  code: 'EAI_AGAIN'
}

I think what's happened is that we're doing too many dns queries. I think we might want to investigate caching our dns lookups with something like cacheable-lookup to reduce the number of dns queries for the same server.

[doug-wade]

This seems to have been a problem with Comcast's DNS lookup -- it was resolved when I changed my dns nameserver to 8.8.8.8.