DNS response history for geek.dunlap.org

geek.dunlap.org is a DNS nameserver monitored by NameServerHistory. This page provides historical DNS response-time data, nameserver uptime signals, DNS latency observations, resolved IP history, successful response counts, failed response counts, and reliability indicators for this nameserver.

The selected UTC date is 2026-08-26. For this date, NameServerHistory found 27 DNS check records, 27 successful responses, 0 failed responses, and 298 ms average response time. Current selected-date status: At least one successful DNS response was recorded for the selected date.

  • Use this report to investigate historical DNS uptime and nameserver reliability.
  • Compare DNS latency changes, failed DNS checks, and response behavior over time.
  • Review the latest resolved IP address and raw DNS check history for geek.dunlap.org.
Records on Selected Date

27

Historical checks stored for this nameserver on selected date

Average Latency

298 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 08:56

All timestamps shown in UTC

Latest Resolved IP on Selected Date

192.168.1.30

Most recently resolved hosting IP on selected date

Successful Responses

27

Checks that returned a measurable response

Failed Responses

0

Checks with no response or no returned latency

Failure Rate

0%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for geek.dunlap.org

Showing DNS history for 2026-08-26 UTC. Newest records appear first.

Latency bars are scaled to a maximum of 5000 ms for quick visual comparison.

# Query Time (UTC) Correlation ID Latency Response IP Address
27 2026-08-26 08:56 639233308387917838
240 ms 192.168.1.30
26 2026-08-26 08:39 639233297961740122
162 ms 192.168.1.30
25 2026-08-26 08:22 639233287487159094
474 ms 192.168.1.30
24 2026-08-26 08:04 639233276995531707
233 ms 192.168.1.30
23 2026-08-26 07:46 639233266521568229
102 ms 192.168.1.30
22 2026-08-26 07:29 639233256081047431
320 ms 192.168.1.30
21 2026-08-26 06:35 639233223620132921
160 ms 192.168.1.30
20 2026-08-26 06:18 639233213287814244
158 ms 192.168.1.30
19 2026-08-26 06:01 639233202925983161
365 ms 192.168.1.30
18 2026-08-26 05:43 639233192644780696
160 ms 192.168.1.30
17 2026-08-26 05:26 639233182401183833
171 ms 192.168.1.30
16 2026-08-26 05:09 639233172074181051
196 ms 192.168.1.30
15 2026-08-26 04:52 639233161808421455
232 ms 192.168.1.30
14 2026-08-26 04:35 639233151357344052
181 ms 192.168.1.30
13 2026-08-26 04:17 639233141034116946
143 ms 192.168.1.30
12 2026-08-26 04:00 639233130828334142
96 ms 192.168.1.30
11 2026-08-26 03:43 639233120373450007
174 ms 192.168.1.30
10 2026-08-26 03:26 639233110066216193
446 ms 192.168.1.30
9 2026-08-26 02:32 639233078065410564
157 ms 192.168.1.30
8 2026-08-26 02:15 639233067787457832
167 ms 192.168.1.30
7 2026-08-26 01:58 639233057501801162
378 ms 192.168.1.30
6 2026-08-26 01:41 639233047089431703
447 ms 192.168.1.30
5 2026-08-26 01:24 639233036754790688
99 ms 192.168.1.30
4 2026-08-26 01:06 639233026412602472
95 ms 192.168.1.30
3 2026-08-26 00:49 639233016064066127
97 ms 192.168.1.30
2 2026-08-26 00:32 639233005922655772
169 ms 192.168.1.30
1 2026-08-26 00:15 639232995672256907
2411 ms 192.168.1.30