[Autogenerated] we're back at Gabrielle is
computer, and she's just done a release
and renew. Now she's having problems
browsing anywhere, so she'll go ahead and
start wire shark. She'll flush her DNA's
cache first and then start wire shark so
we can see what's really happening. Once
again, we seem to have those ICMP port
unreachable packets. When Gabriella tries
to browse to W w dot Globomantics, she
gets that dreaded are message that the
name is not resolving. What if she tries
the sales server that's in our own zone?
Hey, that loads just fine. However, when
Gabriella displays her Deena's cache, she
doesn't have any. Seems the Windows
computer held something in cache that it
doesn't want to tell the user about. Let's
see what her IP configuration is
interesting. That DNA server address isn't
going to take her anywhere. Apparently,
someone changed the scope on the D. H. C P
Server and put in the wrong IP address for
the DNS server. All right, I'll admit it.
I'm the one who did it for the demo, but
you can see how easily that would happen.
That IP address doesn't belong to any of
our hosts. So how did Gabriella, get the
DNAs information for sales. Let's look at
the peak app. Oh my lots more ICMP are
messages, but we're interested in the DNS
queries for sales, so we'll put it in the
filter. DNA's matches sales. So there's
Gabriella's queries for sales, and you'll
notice the response. Is Port unreachable?
And she cleared her cache. What that tells
us is the operating system held that
address in its cache but didn't tell us
about it when she did an IP could fig
slash displayed nested that happens a lot
more on the client and server sides than you would think.