[Autogenerated] single anything is usually
bad in networking. We want to have fault,
tolerance, load balancing and redundancy.
If Global ticket DNA servers are
configured is forwarders to Globomantics
DNA servers, then Globomantics DNS servers
are forwarders to whomever the company
internet provider is boom. Single point of
failure at are for the Globomantics
servers to perform the Ricker versions
themselves. It's great to have a backup,
but if both of your providers use the same
point of presence or pop and hurricane
comes through, you can lose them both. At
the same time. You could only manage what
you could measure, which is just a take
off of the Peter Drucker quote. But if
you're not monitoring DNAs and something
does happen and it always does, how will
you know? Very angry users will tell you
not a pretty picture. We've talked about
DNA's when it's silent. Now let's look at
what happens when it's slow or we receive
an error is slow. Internet DNA's could be
the problem, or it could be something
else. Gabriella, our help desk technician,
is going to focus on drones while the
others on the team approach the network
connections and firewall. Gabriella asks
the first question of troubleshooting. Can
you ping it? If pinging a device on the
internet yields silence, that is the best
place to start. If Gabriella tried to ping
a name and resolution failed, but then
pink to the address on the Internet,
Google's eight dead eight that eight. That
eight is perfect for this. And she got a
response. She would know to start looking
at DNA s versus the network or firewall.
Of course, that doesn't mean that we might
not have to circle back to them later.
Gabriella thinks the silence is DNA's. If
this issue this issue is affecting
everyone than the outage might be the
local DNS servers, she'll ping them first
to see if she gets a response. If she gets
one, she knows that they're up, but
nothing about the health of DNA's. Let's
say she gets a response and we know
they're up. Gabriella needs to check if
she's getting any DNA nested errors. She
can check the log files on the server, or
she can capture the packets. She wants to
go right for wire shark at the packets.
Probably a good thing. Jaden Arden's admin
may or may not have enabled logging well,
look at the wire Shark peak app during the
demo to see if there are any DNA errors.
If there is not in the errors, Gabriella
will have to look for slow response time.
Maybe her users think they can't get to
the internet only because it's too slow.
Gabriella will check during the demo the
response time for cache versus recursive
responses to see if that's the issue. Then
we just go through steps of creating
hypothesis, testing it and making
adjusting adjustments until we find that
root cause approaching in a methodical
manner gives Gabriella the best chance of success.