[Autogenerated] Welcome back to protocol.
Deep dive DNA. CSS. We've seen the client
query for the sales server. But how did
they know who to send the query to? Where
are the records? Cashed. What about the
fact that our queries are in clear text?
Helping the client out is our goal in this
module. Have you ever had trouble
accessing local servers or an Internet
site? DNA's configuration is one of the
first things to check. We'll see what
happens in wire shark and then tested by
clearing our cache. Then we'll up the
privacy level. So our I s P can't track us
Dynamic host configuration protocol is
your friend statically Assigning
information to clients is slow, are prone
and has no place beyond a network of a
client and a router. In fact, the
Pluralsight course protocol deep dive D
HTTP is the perfect place to learn all
about it for our purposes. Let's just say
that clients request their configuration
information upon Buddha or if the address
is released. Part of that configuration is
these IP address of the DNS server or
servers. We'll talk about having multiple
servers in just a moment. It's most common
for the D she API offer an acknowledgement
to be relayed through an IP helper service
on a router or layer three. Switch the
Discover packet, and sometimes the whole
process is sent as a broadcast. There is
no way that having a D to be server on
each sub net would scale. So the IP helper
function was created and runs on the
default gateway multiple DNS servers.
Convey added to the GHB scope for the
clients. Why have multiples? One could go
down, need an upgrade or be busy. We need
to think about load balancing and fault
tolerance. Another reason might be if we
have multiple locations. We always want at
least one Dina server to be as close to
our clients as possible just to make things faster.