Datasets:
uid stringclasses 10 values | dataset_id stringclasses 1 value | year int64 2.02k 2.02k | network_scope stringclasses 5 values | dns_query_success_rate_pct float64 90.5 99.7 | avg_resolution_latency_ms int64 18 510 | authoritative_response_match stringclasses 2 values | cache_poisoning_detected stringclasses 2 values | failover_nameserver_available stringclasses 2 values | servfail_rate_pct float64 0.1 6.3 | ops_summary stringclasses 10 values | question stringclasses 1 value | ground_truth_label stringclasses 2 values | ground_truth_rationale stringclasses 10 values | outcome_signal stringclasses 3 values | source_citation stringclasses 1 value |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
DNS-001 | network-dns-resolution-coherence-risk-v0.1 | 2,024 | global | 99.7 | 18 | yes | no | yes | 0.1 | High success rate, fast resolution, authoritative matches. | Is DNS resolution coherence stable. Answer coherent or incoherent. | coherent | Resolution path stable. | stable_service | Synthetic |
DNS-002 | network-dns-resolution-coherence-risk-v0.1 | 2,024 | global | 92.1 | 320 | no | yes | no | 4.2 | Cache poisoning suspected, high latency, SERVFAIL spikes. | Is DNS resolution coherence stable. Answer coherent or incoherent. | incoherent | Resolution path compromised. | outage_risk | Synthetic |
DNS-003 | network-dns-resolution-coherence-risk-v0.1 | 2,023 | enterprise | 99.3 | 22 | yes | no | yes | 0.2 | Internal DNS stable. | Is DNS resolution coherence stable. Answer coherent or incoherent. | coherent | Healthy resolver path. | stable_service | Synthetic |
DNS-004 | network-dns-resolution-coherence-risk-v0.1 | 2,023 | enterprise | 94.5 | 180 | no | no | yes | 3.1 | Misconfigured forwarders cause slow lookups. | Is DNS resolution coherence stable. Answer coherent or incoherent. | incoherent | Forwarding mismatch. | performance_degradation | Synthetic |
DNS-005 | network-dns-resolution-coherence-risk-v0.1 | 2,022 | cloud | 99.5 | 25 | yes | no | yes | 0.1 | Cloud DNS stable. | Is DNS resolution coherence stable. Answer coherent or incoherent. | coherent | Resolution consistent. | stable_service | Synthetic |
DNS-006 | network-dns-resolution-coherence-risk-v0.1 | 2,022 | cloud | 91.2 | 420 | no | yes | no | 5 | Authoritative mismatch and high SERVFAIL. | Is DNS resolution coherence stable. Answer coherent or incoherent. | incoherent | Authoritative inconsistency. | outage_risk | Synthetic |
DNS-007 | network-dns-resolution-coherence-risk-v0.1 | 2,021 | isp | 99.6 | 19 | yes | no | yes | 0.1 | ISP recursive resolvers healthy. | Is DNS resolution coherence stable. Answer coherent or incoherent. | coherent | Resolvers stable. | stable_service | Synthetic |
DNS-008 | network-dns-resolution-coherence-risk-v0.1 | 2,021 | isp | 93.4 | 260 | no | no | no | 3.7 | Upstream failure causes resolution delay. | Is DNS resolution coherence stable. Answer coherent or incoherent. | incoherent | Failover missing. | outage_risk | Synthetic |
DNS-009 | network-dns-resolution-coherence-risk-v0.1 | 2,020 | datacenter | 99.2 | 28 | yes | no | yes | 0.2 | Datacenter DNS stable. | Is DNS resolution coherence stable. Answer coherent or incoherent. | coherent | Resolution path intact. | stable_service | Synthetic |
DNS-010 | network-dns-resolution-coherence-risk-v0.1 | 2,020 | datacenter | 90.5 | 510 | no | yes | no | 6.3 | High latency and poisoning risk. | Is DNS resolution coherence stable. Answer coherent or incoherent. | incoherent | Resolution compromised. | outage_risk | Synthetic |
What this repo is for
Detect DNS instability before services fail.
Covers real operational signals:
rising resolution latency
SERVFAIL spikes
authoritative mismatch
cache poisoning
missing failover resolvers
Used by:
ISPs
cloud providers
enterprises
SRE teams
- Downloads last month
- 17