Unfortunately, you really need to understand the fundamentals to understand a wireshark capture. What you asked is kind of like saying, "I tried to read this book that's only available in French, but I didn't understand it. Is there a step-by-step guide to reading this book?"

The solution: learn the language. Then the meaning of what you're trying to read becomes clear, not because someone explained it to you, but because you understand the language well enough to grasp the meaning.

http://amzn.com/0470450606

EDIT: Adding on to say, why don't you describe the symptoms rather than saying you think it's a DNS issue? My most frustrating service calls are when a customer tells me it's obviously due to Issue A because Google said so, when my research shows that Issue A is a symptom of a completely different problem that you won't find on Google because it's so rare and conflicts with the symptoms of Issue A. This makes me understand why doctors are sad when patients walk in saying they think they have some disorder because <<symptoms>>, when in fact those symptoms can be common to hundreds of unrelated disorders.

u/lingual_panda · 2 points r/cscareerquestions

I'm a first-year CS student and I just started reading TCP/IP for Dummies. Depending on the book's level of accuracy, I think it would be a good introduction for answering these kinds of questions.

Related categories:

Reddit mentions of TCP / IP For Dummies

idea-bulb Interested in what Redditors like? Check out our Shuffle feature

Found 3 comments on TCP / IP For Dummies:

Interested in what Redditors like? Check out our Shuffle feature