i do not understand why i am getting error, i have try with three new id but getting same error.
this is my connection string : mongodb+srv://:@cluster0.ejctebw.mongodb.net/?retryWrites=true&w=majority
i have written correct name, password and database name.
i have try with database name and without database name in my connection string.
can anyone help me regarding this issue. i have try the Stackflow answer and also try to implement
like IP addresss , allow from anywhere, delete and create IP address along with 0.0.0.0
i have check my driver which is node with latest version.
I am trying to connect mongo application and also check user name and password.
i have also try creating database under collection, try every way i but nothing resolve my error
Hello , Can you please check all IP details added in whitlist(security/network access) ? this seems DNS not resolving the server validation . let me know if it helps
If you go to the connect modal for your cluster and choose an older version of the Node driver (ex: 2.2.12 or later) it’ll give you the legacy connection string:
Using the legacy mongodb:// protocol as opposed to the mongodb+srv:// protocol will allow you to avoid the additional DNS queries that appear to be failing.
Actually you are correct it seems its DNS issue. facing the same problem when trying to connect to Atlas from my machine.
when checking my windows event log -----> System
the following was thrown:
Name resolution for the name myatlasXXXXX.XXXXX.mongodb.net timed out after none of the configured DNS servers responded.
I am having a similar problem which I cannot seem to track down.
Local Compass is connected with the Atlas Cluster and I can edit in either.
But the AI Generate Query which brings up a modal to connect then fails with this message:-
Sign in failed
listen EADDRNOTAVAIL: address not available fe80::1:27097
I don’t understand that message apart from an address is not available.
Can anyone help me with this?
The SRV format requires 2 DNS queries to be performed (an SRV query and a TXT query), the results of which are used to construct a standard connection string formatted string that is used by the drivers to establish a connection to the cluster.
If those DNS queries fail, connection string construction will fail and you’ll typically get an error such as querySrv ETIMEOUT or queryTxt ETIMEOUT.
how can i connect through latest version too, i have fix the DNS problem too like 8.8.8.8 and the other one 8.8.4.4 in adapter settings in ipv4 properties but it was not the issue in my case
You can use the standard connection string format with the latest driver. The UI in Atlas is a little misleading (we’re working on improving this) as it makes it seem as though you need to use an older driver to use the older connection string format - which isn’t true.
Just select 2.2.12 from the UI to get the mongodb:// connection string then use that to connect using the latest Node.js driver.
Correct - if you’re having a DNS issue resolving the SRV record then you’d need to use teh 2.2.12 connection string with 5.5. The difference is one connection string begins with mongodb:// and the other begins with mongodb+srv://.
The first one doesn’t require DNS queries, which is why you wouldn’t see the associated errors.
