we took a look at our D. N s. Now let's take this and put it into practice on our chart here. We have an example of our network here. Now, our neck network is connected to the Internet,
which we have identified up here. I'll just put a big eye next to it.
is our local network
and then everything outside that is our
Then everything outside that is Arab external network. So in our model here we have our internal network, and then we also have our external network outside that so our external network is going to be the Internet.
So we have our client computer here, and our client computer
connects to our router, which connects to our sales server as well as our internal D. N s server,
our internal being s servers also going to be our domain controller.
Now, our internal D. N s server is going to provide resolution for our internal names. Now, why do we need a new internal D. N s server? Why don't we just use our default dina servers that say, our say our Internet service provider gives us or use an external dina server such as 8888888
Well, these external being s servers don't have records for our internal servers, and they're not gonna let us write records for our internal servers on them. So we need to have an internal D. N s server, which is able to which is able to know which is able to help us find our internal devices.
So we have our client computer here,
and it's looking to save a file, or it's looking to pull a file off of the sales server.
sales that cyber it out local? Um, we don't know its full path. Maybe we're just entering in a share path, so we type in that we want to access
ford slash ford slash sales,
And that's our shared folder for our sales documents.
our computer is going to say, OK,
get rid of the slash docks for sec.
I need to identify forward slash forward slash sales.
this is not a fully qualified domain name.
This is just a r shorthand for our server name. So how does our computer know? How does it know where to begin searching for its local are our local server.
Well, the first thing on computers going to do is it's going to tack on what? Whatever local domain we're on. So
we are on the same domain as this sales, not cyber readout. Local server.
So we're going to talk. We're gonna tack on, okay?
Sales thought cyber eri
dot local. And that's what our computer's going to do automatically for us.
Now, the first place is going to check for resolution is not gonna be our d. N s server is gonna check our local hosts file as well as our cash.
Now, our computer, in order to speed up and in order to save time, doesn't immediately
go out and search for D. N s on our server. It checks. It's local cash. And as we resolve different names, it saves those saved searches in our local cash so that we can find them quicker in the future. It takes time for a request to go out, go out to a D. N s server, bring back its i P address and begin to route.
So in order to speed that up,
we have a we have a cache that we save in addition to our cash. We also have a hosts file.
Now what is our hosts? File? Do
Our host file is going to provide us with a manual way to set on our local computer D. N s entries
back in the dawn of the Internet. This is where we kept all of our d. N s entries for everything was a giant host file, but that very, very quickly became too large to unmanageable toe have for all of the computers and all of the servers on the Internet. So we developed a D. N s.
our host file is still a location where we may edit or we may want to modify in order to change where our computer looks for certain servers. Certain locations say, if we wanted to, if we if we needed to have our sales, that cyber without local server,
if we were doing some tests and we wanted that toe look at a different server that we were planning on implementing,
we could edit that hosts file, and then, instead of having and setting, have instead of having our computer go out and checking our D n s. Our computer would check our hosts file first.
So our computer's gonna check for sales that cyber dot local in our cash and our hosts file
now, it doesn't find it in either of those places. It doesn't find the d. N s entry in either of those two places because we've never connected to the server before. It's not gonna be in our cash. Or maybe we just recently performed an I p config flush D N s, which flushes this cash and clears it all out,
so it's not gonna find anything there.
So our computer is now going to send our d. N s query to our D. N s server that we have set up in our I p r I p configuration and we're going to set our default D. N s server to be our internal being s server here.
So our computer's gonna send its first query over too.
Our internal being s
Now our internal being s is going to look for sales. That's I really doubt local, and it will find it in its entry, and it's going to say OK, sale starts. I buried out local is 1 92.1 68 That one about 17.
So our dina service going to return our query
and let us know. Okay, I found sales, not cyber dot local and it said this address. So then our computer just simply goes to that address after that, and it saves that search in its cash. V N s not only performs Ford Lookups,
which is a fully qualified domain name, translated directly to an i p address, but it can also do reverse lookups
reverse lookups are where we type in where we search for the i p address to the fully qualified domain name. So if we didn't know who sails, that cyber dot local was and we wanted to search for it on we searched for 1 92.1 68 at one that 17 it would perform that reverse lookup and then let us know. So
we had our Ford look ups
and we found our sales that cyber dot local.
Now, how do we find something that's gonna be outside of our domain? How do we find something that's going to be outside of our domain? How do we find a server such as a Google server Over here
Now, we don't wanna have every single website in the entire Internet
saved on our D. N s servers as the location that it goes to
our internal Deanna servers. Rather, that would be way too unmanageable. That would be way too risky that someone's going to attempt to affect this D n a server. And it would just be the configuration in the management of that would be just too incredible. So what we have set up are we have the ability to forward D. N s requests
What that means is we have our
client here searches for google dot com. Maybe we just recently flushed our cash. So the location is not in our cash.
It's not in our host file because we've never manually configured it.
So we send the request out to our router.
Our router sends the request over to our local DNF server, and our local Dina server says,
I've never seen this one before
and I don't have any record for this. So I'm going to send this off to who I have set up as my for order.
So our d. N s server. We know that our internal, the N s server isn't gonna find everything. So when we set it up, we manually configure a location. It goes and looks
four looks four dresses if it can't find them, and it's local set in its local manual configurations. So we set
eight dot a dot a 188.8.131.52
as our Deena's border for
are the internal D. N s server. So our internal DINA server can't find google dot com So it's going to search.
It's going to send this query on back to our router
and then out to the Internet.
this Internet Vienna server is going to say, Oh, yeah, I know where google dot com iss So it's going to send that reply back
to our internal D. N s server,
who will then pass that along
to our computer, who can now go out to Google and find where it's at, which is right here. So then it goes out to Google.
that's how are being s works. That's how our
clients and our servers,
that's our sales server, our clients and our D. N s servers work together.
We know now that D N s resolves fully qualified domain names toe I p addresses and can also do a reverse look up sort results I p addresses to fully qualified cola fall fully qualified domain names.
So let's go ahead. And now let's move on. And we're gonna take a little bit of a closer look at Dina servers and D. N s clients.