What to Do When the Jail Roster Website Is Unreachable

One common sign you’re dealing with a real outage is a full-page error that says “The requested URL could not be retrieved.” For example, the roster page at http://www.daleso.com/roster_view.php?booking_num=1291 returned that message instead of loading a booking record.

Look closely at the wording under the headline. If you see phrases like “Unable to determine IP address from host name \"www.daleso.com\",” that points to a DNS problem - your device (or a server between you and the site) can’t translate the website name into an address it can connect to. You may also see something like “Name Error: The domain name does not exist.” That’s different from a normal “no results found” or “booking not located” message. It’s the system telling you it can’t reach the site name at all, not that the person isn’t in custody.

A DNS “Name Error” (and “Unable to determine IP address”) usually means the system trying to fetch the page can’t resolve the website name, so it can’t even start loading the roster. When the page also shows a generated timestamp and server details, that’s another sign you’re seeing an upstream/server-side failure rather than a normal roster search result.

Quick Checks

• ✓ Reload the page once or twice (a temporary hiccup can clear fast)
• ✓ Try a different browser (or update/close and reopen your current one)
• ✓ Switch devices if you can (phone vs. computer)
• ✓ Use a private/incognito window to rule out a bad cached session
• ✓ Try a different network (Wi‑Fi vs. cellular) to rule out a local connection issue
• ✓ Search for a cached copy of the page (search engine cache or the Wayback Machine)
• ✓ Try loading the root site (for example, www.daleso.com) to see if the whole domain is failing, not just one roster page
• ✓ Write down the exact error wording you see (don’t paraphrase)
• ✓ Note any “Generated” timestamp shown on the error page

If you end up calling for help, the fastest way to get taken seriously is to share what you saw. Copy the exact error text, and if the page shows details like “Your cache administrator is <webmaster>,” a generated timestamp, or a server name, record those too. Those bits help someone troubleshoot whether it’s a DNS/hostname issue versus a problem with the roster tool itself.

1. Call the facility or sheriff’s office - Ask to confirm whether the person is currently in custody, and if so, what their status is right now.
2. Check official state or county lookup tools (if available) - Some states have Department of Corrections search pages, and some counties post status updates outside the roster.
3. Use third-party inmate locator sites carefully - These can be helpful for leads, but they can also be delayed or wrong. Treat anything you find as unconfirmed.
4. Consider an in-person visit only if it makes sense - If you’re local and it’s safe/appropriate, staff at the front desk may be able to confirm basic custody status even when the website is down.

How When Verify Before Acting

• ✓ Whether the person is currently in custody (and where)
• ✓ Any scheduled court dates and the correct time/location
• ✓ Expected release timing and any release conditions (if staff can share them)
• ✓ Bail/bond status and what’s required to post it
• ✓ Visitation rules you need before showing up (days, check-in time, ID requirements, dress code, and whether visits must be scheduled)

When you report the outage, be specific: tell them the exact roster URL you tried (for example, the page that returned “The requested URL could not be retrieved”), the full error message, and the time it happened. If the page shows a generated timestamp, include that too - those details can help narrow down whether the problem is with the domain/DNS or with the roster system behind it.