# The humble DNF: why a "Did Not Find" log matters
Most geocachers recognize the feeling: you reach the published coordinates, search for a long time, and still can't find the cache. You either walk away frustrated or you log a DNF — "Did Not Find." This article explains why that small, sometimes embarrassing log is actually useful to you, to the cache owner, and to the community.
A DNF record signals that a cache may be missing or that the hide is unexpectedly difficult. When a cache shows many months of inactivity and a recent DNF appears, the owner may check and replace a missing container. One anecdote in the source describes a multi-cache at the University of Texas where a DNF led directly to owner maintenance and cache replacement.
Logging a DNF doesn't always end the story. It can create curiosity: was the cache gone or just well hidden? The author recounts a Seattle-area cache where an initial DNF was followed by a find a few days later, proving the hide was very good rather than missing. That uncertainty — and the follow-up — becomes a separate, enjoyable challenge.
A DNF can be a conversation starter. The author describes moving to Seattle, logging a DNF on a challenging cache near Geocaching HQ, then returning with co-workers and finding the cache together. The teamwork required after a DNF can produce stronger social ties than a quick solo find.
Sometimes the DNF simply marks a future plan. The writer attempted a cache on Penny Lane in Liverpool and couldn't find it during that visit. Seeing later "Found it" logs tells the writer the cache still exists and should be tried again on a future trip. DNFs can create a short list of caches you'll want to revisit.
- Log facts, not assumptions. State what you searched and any useful observations (e.g., visible damage, missing container, changed surroundings).
- Give the owner clear signals. A succinct DNF can prompt an owner check sooner than a long gap in activity.
If you invest time and leave a DNF, you've added information other players might not have. That single log can prompt maintenance, encourage collaboration, and turn a failed search into a new bit of the geocaching story.