Mongoose 6/ Mongo Atlas: MongoNetworkError: getaddrinfo ENOTFOUND on SRV resolved address

[sadeghhosseini]

I use mongoose version 6.
I use a connection string like this to connect to Mongo Atlas. mongodb+srv://<username>:<password>@xxxx.yyyyy.mongodb.net/?retryWrites=true&w=majority&appName=zzzz. Today after a year I got MongoNetworkError: getaddrinfo ENOTFOUND ac-abcxyz-lb.yyyyy.mongodb.net error.

It seems that ac-abcxyz-lb.yyyyy.mongodb.net is the address of a node returned in the SRV DNS lookup to which Mongoose is trying to connect, but DNS fails to resolve the address and mongoose keeps using the same address, without fetching a new address and trying that.

Is there anyway that I can setup mongoose to take care of this situation by fetching and trying a new address?

[vkarpov15]

I had a lot of similar issues this week due to DNS issues with my ISP (ATT) - have you tried connecting on a different network?

[sadeghhosseini]

Restarting the application resolved the issue. After contacting MongoDB Atlas support, I learned that my cluster had recently been migrated from Serverless to Flex. During the migration, the DNS configuration for the cluster was changed, and the cached DNS entry used by my application caused the problem hence the ENOTFOUND error.

According to the support team, flushing the DNS cache on the application servers and restarting the application should resolve this type of issue. (In my case, simply restarting the application was sufficient; flushing the DNS cache was not necessary.)

I’m wondering whether Mongoose or the MongoDB Node.js driver provides any built-in mechanism to take care of such occasions automatically, since a simple reconnection to the database appears to resolve the issue.

[vkarpov15]

Neither Mongoose nor MongoDB driver provide any built in handling for this case AFAIK.