1. What will we learn?
We will learn the foundational networking concepts that allow applications to communicate across the internet: IP addresses, Ports, DNS, HTTP, and Firewalls.
2. Why do we need this?
When you deploy an application, users need a way to reach it. If a user complains "the website is down", you need to know if the application crashed, or if a firewall blocked the port, or if the DNS is pointing to the wrong IP. Networking knowledge is mandatory for troubleshooting.
3. What is it?
- IP Address: A unique string of numbers that identifies a computer on the internet.
- Port: A specific "door" on that computer dedicated to a specific service.
- DNS: The phonebook of the internet that translates human names (google.com) into IPs.
4. Simple analogy
Think of a computer as a giant Apartment Building:
- The IP Address is the building's street address (e.g., 123 Main St).
- The Port is the specific apartment number inside the building (e.g., Room 80 for the Web Server).
- DNS is the contacts app in your phone. You don't memorize your friend's phone number (IP address); you just search their name (google.com) and the phone dials the number.
- The Firewall is the security guard at the door who only allows authorized people into specific rooms.
5. How it works
When you type https://mydeenblog.vercel.app in your browser:
1. Your computer asks a DNS server: *"What is the IP address for this domain?"*
2. DNS answers: *"It is 76.76.21.21"*
3. Your computer travels to that IP Address.
4. It knocks on Port 443 (the standard port for HTTPS secure traffic).
5. The Firewall allows it in.
6. The server replies with the website's HTML!
6. Step-by-step practical example
Public vs Private IP
- Public IP: Reachable by anyone in the world (e.g., Google's servers).
- Private IP: Reachable only within your local network (e.g., your home Wi-Fi assigns your laptop an IP like
192.168.1.5).
Important Ports to memorize:
- Port 80: HTTP (unencrypted web traffic)
- Port 443: HTTPS (encrypted, secure web traffic)
- Port 22: SSH (securely logging into a Linux server via terminal)
- Port 3306: MySQL database
- Port 5432: PostgreSQL database
7. What just happened?
By understanding these components, you now understand the journey of web traffic. When we deploy our DevOps project later, we will open Port 80 on our AWS Firewall so the world can see our application!
8. Common beginner mistakes
- Opening Port 22 to the whole world: Port 22 (SSH) gives terminal access to your server. If you leave it completely open in your AWS firewall without strict security, bots will constantly try to hack into your server.
- Confusing Public and Private IPs: Trying to access a private database IP from a public internet connection will never work.
9. Interview questions
Q: What is DNS?
A: Domain Name System. It resolves human-readable domain names (like github.com) into machine-readable IP addresses.
Q: If a user cannot access your web application, but they can ping the server's IP, what might be the issue?
A: The web server might be down, or a firewall is blocking Port 80 / Port 443.
10. What we learned
We learned that computers communicate using IP addresses and Ports, shielded by Firewalls. DNS makes the internet usable for humans by replacing numbers with names.
11. What's next?
Now that we understand Linux and Networking, we are ready to rent a server on the internet! In Article 5 โ AWS Basics, we will explore Cloud Computing!
