Documentation does not cover how to set up hostnames for use with MongoDB Replica Sets (DOCS-567)

[DOCS-611] 2.2 is more sensitive to DNS, update examples accordingly Created: 15/Oct/12  Updated: 30/Oct/23  Resolved: 29/Oct/12

Status: Closed
Project: Documentation
Component/s: Server
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Sub-task Priority: Minor - P4
Reporter: Ed Costello Assignee: Sam Kleinman (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-7367 Make replica set members pick up thei... Closed
Related
Participants:
Days since reply: 11 years, 16 weeks, 2 days ago

 Description   

See related SO question.
If you do not specify a bind_ip then mongod relies on the hostname returned by gethostname(). If that hostname is not fully qualified (eg gethostname() returns "host" and not "host.example.net") then further lookups may fail, especially when trying to set up replica sets.

Net: for examples relying on localhost, make that explicit with bind_ip 127.0.0.1 or hostname localhost, otherwise use fully qualified domain names and note that the hostname of the system mongod is running on must be fully resolvable in DNS.



 Comments   
Comment by Sam Kleinman (Inactive) [ 29/Oct/12 ]

Not changing because fix is in 2.2.1, and documenting it will probably cause more confusion than it will resolve.

Generated at Thu Feb 08 07:39:05 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.