DNS response history for dns2.dazone.co.kr

dns2.dazone.co.kr 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 35 DNS check records, 35 successful responses, 0 failed responses, and 553 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 dns2.dazone.co.kr.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

553 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:40

All timestamps shown in UTC

Latest Resolved IP on Selected Date

121.156.55.7

Most recently resolved hosting IP on selected date

Successful Responses

35

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 dns2.dazone.co.kr

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
35 2026-08-26 11:40 639233403515141099
433 ms 121.156.55.7
34 2026-08-26 10:45 639233370841350248
391 ms 121.156.55.7
33 2026-08-26 10:28 639233360361507238
415 ms 121.156.55.7
32 2026-08-26 10:11 639233350067824371
388 ms 121.156.55.7
31 2026-08-26 09:53 639233339545274518
431 ms 121.156.55.7
30 2026-08-26 09:36 639233329214918079
676 ms 121.156.55.7
29 2026-08-26 09:19 639233318749762337
591 ms 121.156.55.7
28 2026-08-26 09:01 639233308387917838
825 ms 121.156.55.7
27 2026-08-26 08:44 639233297961740122
648 ms 121.156.55.7
26 2026-08-26 08:26 639233287487159094
564 ms 121.156.55.7
25 2026-08-26 08:09 639233276995531707
614 ms 121.156.55.7
24 2026-08-26 07:51 639233266521568229
440 ms 121.156.55.7
23 2026-08-26 07:34 639233256081047431
419 ms 121.156.55.7
22 2026-08-26 06:40 639233223620132921
857 ms 121.156.55.7
21 2026-08-26 06:23 639233213287814244
604 ms 121.156.55.7
20 2026-08-26 06:05 639233202925983161
566 ms 121.156.55.7
19 2026-08-26 05:48 639233192644780696
854 ms 121.156.55.7
18 2026-08-26 05:31 639233182401183833
403 ms 121.156.55.7
17 2026-08-26 05:14 639233172074181051
436 ms 121.156.55.7
16 2026-08-26 04:57 639233161808421455
585 ms 121.156.55.7
15 2026-08-26 04:40 639233151357344052
587 ms 121.156.55.7
14 2026-08-26 04:22 639233141034116946
594 ms 121.156.55.7
13 2026-08-26 04:05 639233130828334142
658 ms 121.156.55.7
12 2026-08-26 03:48 639233120373450007
393 ms 121.156.55.7
11 2026-08-26 03:31 639233110066216193
433 ms 121.156.55.7
10 2026-08-26 02:37 639233078065410564
600 ms 121.156.55.7
9 2026-08-26 02:20 639233067787457832
588 ms 121.156.55.7
8 2026-08-26 02:03 639233057501801162
436 ms 121.156.55.7
7 2026-08-26 01:46 639233047089431703
580 ms 121.156.55.7
6 2026-08-26 01:28 639233036754790688
605 ms 121.156.55.7
5 2026-08-26 01:11 639233026412602472
571 ms 121.156.55.7
4 2026-08-26 00:54 639233016064066127
589 ms 121.156.55.7
3 2026-08-26 00:37 639233005922655772
588 ms 121.156.55.7
2 2026-08-26 00:20 639232995672256907
590 ms 121.156.55.7
1 2026-08-26 00:03 639232985300872416
405 ms 121.156.55.7