Mongodb reporting ENOTFOUND issue

Question

I am developing a node application that points to a QA database. The database has 2 replica sets. When I start my node app, an ENOTFOUND issue was logged in the console.

C:\Users\xliu\WebstormProjects\gns-pages\api\node_modules\mongodb\lib\replset.js:365
      process.nextTick(function() { throw err; })
MongoError: failed to connect to server [ip-10-16-89-129:27017] on first connect [MongoError: getaddrinfo ENOTFOUND ip-10-16-89-129 ip-10-16-89-129:27017]
at Pool.<anonymous> (C:\Users\xliu\WebstormProjects\gns-pages\api\node_modules\mongodb-core\lib\topologies\server.js:336:35)
at emitOne (events.js:96:13)
at Pool.emit (events.js:188:7)
at Connection.<anonymous> (C:\Users\xliu\WebstormProjects\gns-pages\api\node_modules\mongodb-core\lib\connection\pool.js:280:12)

However, when I pinged the server in the console, it showed no package was lost in transmission.

Pinging sports-pages-dev-mongo-db-a.labs.gracenote.com [10.16.89.169] with 32 bytes of data:
             Reply from 10.16.89.169: bytes=32 time=143ms TTL=240
             Reply from 10.16.89.169: bytes=32 time=167ms TTL=240
             Reply from 10.16.89.169: bytes=32 time=179ms TTL=240
             Reply from 10.16.89.169: bytes=32 time=105ms TTL=240

I am using Mongoose 4.11.10 and Window 10 for OS. Can anyone share some thoughts on this, I will be very appreciated.