DNS latency
Is DNS Actually the Slow Part?
A request is slow and DNS is suspected without a measured resolver boundary.
resolve_backend uprobeUnderstand the evidence boundary ↗
Saved on this device · Assistance is recorded · Reviews stay separate from completion.
Readiness · one concrete prerequisite
The fixture adds a 500 ms sleep inside the measured resolver wrapper. Does 500 ms wrapper duration prove server latency?
Optional tutor critique
The tutor sends the previewed material to Groq’s Qwen 3.8 27B model through this application. It is fallible and does not assign mastery. Groq may retain or process data under its applicable policies. Authored hints remain available if it is unconfigured. Your claim, mechanism, unknown, next experiment and hint count are sent only after consent and clicking Request.
Exact learner request preview (the server also includes this lab’s authored curriculum and rubric):
{
"consent": true,
"labId": "04",
"claim": "",
"reasoning": "",
"unknown": "",
"nextStep": "",
"evidence": [],
"hintsUsed": 0
}