Network security and bind IP in MongoDB - Mini Project: Build & Apply

Configure MongoDB Network Security with Bind IP

📖 Scenario: You are setting up a MongoDB server for a small company. To keep the database secure, you need to configure the network settings so that MongoDB only listens on specific IP addresses. This prevents unauthorized access from other machines.

🎯 Goal: Configure the MongoDB mongod.conf file to set the bindIp option, allowing connections only from the local machine and a trusted internal IP address.

📋 What You'll Learn

Create a basic mongod.conf configuration with network settings

Add a net section to the configuration

Set the bindIp option to 127.0.0.1 and 192.168.1.100

Ensure the configuration file is valid YAML syntax

💡 Why This Matters

🌍 Real World

Restricting MongoDB network access to specific IP addresses helps protect sensitive data from unauthorized external access.

💼 Career

Database administrators and DevOps engineers often configure bindIp settings to secure database servers in production environments.

1

Create the base mongod.conf file

Create a file named mongod.conf and add the root level YAML key net: to start the network configuration section.

MongoDB

net:
# Your code here

Hint

The net section groups network-related settings in the MongoDB config file.

2

Add the bindIp setting

Under the net: section, add the bindIp: key and set its value to 127.0.0.1 (localhost). Use proper YAML indentation (2 spaces).

MongoDB

net:
  bindIp: 127.0.0.1
# Your code here

Hint

Indent the bindIp line exactly two spaces under net:.

3

Add a second IP address to bindIp

Modify the bindIp value to include both 127.0.0.1 and 192.168.1.100 separated by a comma, so MongoDB listens on both addresses.

MongoDB

net:
  bindIp: 127.0.0.1,192.168.1.100
# Your code here

Hint

Separate multiple IPs with a comma and no spaces.

4

Complete and validate the mongod.conf file

Ensure the mongod.conf file contains the net: section with the bindIp set to 127.0.0.1,192.168.1.100 and that the YAML syntax is correct.

MongoDB

net:
  bindIp: 127.0.0.1,192.168.1.100
# Your code here

Hint

Double-check indentation and no extra characters.

Practice

1. What does the bindIp setting in MongoDB control?

easy

A. The storage location of MongoDB data files

B. Which IP addresses can connect to the MongoDB server

C. The database user permissions

D. The port number MongoDB listens on

Solution

1. Step 1: Understand the purpose of bindIp

   The bindIp setting specifies which IP addresses are allowed to connect to the MongoDB server.

2. Step 2: Compare with other options

   Port number, user permissions, and data file locations are controlled by other settings, not bindIp.

3. Final Answer:

   Which IP addresses can connect to the MongoDB server -> Option B

4. Quick Check:

   bindIp controls allowed IPs [OK]

Hint: bindIp controls allowed IP addresses only [OK]

Common Mistakes:

• Confusing bindIp with port setting
• Thinking bindIp controls user permissions
• Assuming bindIp sets data file paths

2. Which of the following is the correct syntax to allow connections only from localhost in MongoDB's configuration file?

easy

A. bindIp: '192.168.1.1'

B. bindIp: '0.0.0.0'

C. bindIp: '127.0.0.1'

D. bindIp: 'localhost'

Solution

1. Step 1: Identify localhost IP address

   Localhost IP is 127.0.0.1, so to allow only local connections, bindIp must be set to this.

2. Step 2: Check other options

   0.0.0.0 allows all IPs, 192.168.1.1 is a specific network IP, and localhost is not valid syntax here.

3. Final Answer:

   bindIp: '127.0.0.1' -> Option C

4. Quick Check:

   Localhost IP = 127.0.0.1 [OK]

Hint: Use 127.0.0.1 to restrict to localhost [OK]

Common Mistakes:

• Using 'localhost' string instead of IP
• Using 0.0.0.0 which allows all IPs
• Confusing network IP with localhost

3. Given the following MongoDB config snippet:

net:
  bindIp: 127.0.0.1,192.168.1.100

Which clients can connect to this MongoDB server?

medium

A. Clients from 127.0.0.1 and 192.168.1.100 only

B. Clients from any IP address

C. Only clients from IP 127.0.0.1

D. Clients from 192.168.1.100 only

Solution

1. Step 1: Read the bindIp list

   The bindIp setting lists two IPs: 127.0.0.1 (localhost) and 192.168.1.100.

2. Step 2: Determine allowed clients

   Only clients connecting from these two IP addresses are allowed. Other IPs are blocked.

3. Final Answer:

   Clients from 127.0.0.1 and 192.168.1.100 only -> Option A

4. Quick Check:

   bindIp list limits clients to those IPs [OK]

Hint: bindIp list allows only those IPs [OK]

Common Mistakes:

• Assuming 0.0.0.0 allows all IPs here
• Ignoring second IP in the list
• Thinking it allows all local network IPs

4. You set bindIp: 127.0.0.1,192.168.1.50 in your MongoDB config, but remote clients from 192.168.1.50 cannot connect. What is the most likely cause?

medium

A. MongoDB service was not restarted after config change

B. The IP 192.168.1.50 is not a valid IP address

C. bindIp only accepts one IP address

D. Remote clients must use port 27018 instead of 27017

Solution

1. Step 1: Verify bindIp syntax

   Multiple IPs separated by commas is valid syntax, so the config is correct.

2. Step 2: Check common operational issues

   Changes to bindIp require MongoDB service restart to take effect. Without restart, old settings remain active.

3. Final Answer:

   MongoDB service was not restarted after config change -> Option A

4. Quick Check:

   Restart needed after config changes [OK]

Hint: Restart MongoDB after changing bindIp [OK]

Common Mistakes:

• Thinking bindIp accepts only one IP
• Assuming IP is invalid without checking
• Changing port without reason

5. You want your MongoDB server to accept connections only from your local machine and a trusted remote IP 10.0.0.5. Which bindIp setting achieves this securely?

hard

A. bindIp: localhost,10.0.0.5

B. bindIp: 0.0.0.0

C. bindIp: 10.0.0.5

D. bindIp: 127.0.0.1,10.0.0.5

Solution

1. Step 1: Identify IPs to allow

   You want to allow localhost (127.0.0.1) and the remote IP 10.0.0.5.

2. Step 2: Choose correct bindIp syntax

   Use a comma-separated list of IPs: 127.0.0.1,10.0.0.5. Using 0.0.0.0 allows all IPs, which is insecure. Using 'localhost' is invalid syntax.

3. Final Answer:

   bindIp: 127.0.0.1,10.0.0.5 -> Option D

4. Quick Check:

   List allowed IPs explicitly [OK]

Hint: List all allowed IPs separated by commas [OK]

Common Mistakes:

• Using 0.0.0.0 which allows all IPs
• Using 'localhost' string instead of IP
• Allowing only remote IP without localhost