DNS, IP Addresses & Ports - Rest APIs In Depth

Let's learn how DNS, IP Addresses and Ports work in the context of networking so we can better prepare for working with REST APIs.

We start by looking at the URL structure and how it allows us to request information from a particular resource on a network in a structured way.

Then, we look at the domain name system which translates domain names to ip addresses for the computer. We then use these ip addresses to lookup servers on the network or Internet. We also take a look at a tool called nslookup in our terminal.

To wrap up the video we look at network ports and reserved port numbers and how this might impact our applications. We also pull up Insomnia to make some requests to ip addresses to see that they work just as well as domain names!

Chapters:
00:00 Introduction
01:13 What happens to URLS?
03:18 What is a URL?
08:00 DNS - Domain Name System
11:14 The nslookup tool
13:12 IP Addresses
17:13 nslookup IPv6
20:32 Network Ports
22:40 Reserved Ports
24:10 Bringing it Together
25:40 Insomnia URLs and IPs
30:28 Next Steps

[up_code]

Thank you so much for going through this in a slow and detailed manner!

[sikut]

I am 48 years old trying to change my profession. It seems that this course finally opened my old brain and let it absorb the tricky knowledge

[mikelautensack]

I would absolutely love some network programming in c content. It’s a topic I am very curious about. I’ve never written any c but I am going to start learning and writing it as a academic language and for a web dev I think network programming would be the most useful.

[dualasus]

DNS allows us to group multiple IP's to a single domain name. Which is also very useful for globally distributed systems like google that have many different servers across the world. Also public IP's aren't static meaning that you would have to look up the IP for google every time it changes to a new IP but with DNS we can automatically get a reference to the most recent IP through the DNS lookup. Though with google their domain name is likely tied to a Load Balancer to distribute to other Load Balancers based on geolocation.

[Abulkhair]

what a content ...Whish I could have been able to support you on Patreon....

[clairelist]

Maybe your query arg is not working with nslookup because it's supposed to be a flag? -query=A (according to IBM docs)