[DOCS-567] Documentation does not cover how to set up hostnames for use with MongoDB Replica Sets Created: 01/Oct/12  Updated: 29/Oct/12  Resolved: 29/Oct/12

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

Type: Improvement Priority: Minor - P4
Reporter: William Zola Assignee: Sam Kleinman (Inactive)
Resolution: Done Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Issue Links:
Depends
Related
Sub-Tasks:
Key
Summary
Type
Status
Assignee
DOCS-611 2.2 is more sensitive to DNS, update ... Sub-task Closed Sam Kleinman  
Participants:
Days since reply: 11 years, 20 weeks, 2 days ago

 Description   

If you're going to be using MongoDB with a replica set, your local host must be properly configured in order to find its own name in the set. If not you'll get errors of the form:

 [rsStart] couldn't connect to alpha-RS1:27018: couldn't connect to server alpha-RS1:27018



 Comments   
Comment by Ed Costello [ 01/Oct/12 ]

Can you look at this and add something first to release notes and then update the existing documentation?

Comment by William Zola [ 01/Oct/12 ]

Here's what you have to do to make sure that the hostname is resolvable:

1) Make sure the FQDN is present in the hostname:

$ hostname
alpha-RS1.example.com
$ hostname -f
alpha-RS1.example.com

2) Make sure that the FQDN is resolvable: the following commands should complete without error (and properly resolve the hostname):

$ nslookup $(hostname)
$ host -v $(hostname)

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