Adds SkyDNS (193.58.251.251) to api/data/dns-resolvers.js, giving
Russia a second public resolver alongside Yandex.DNS, as invited
in #390.
UDP entry only: SkyDNS's DoH endpoint serves RFC 8484 wire format
rather than the application/dns-json API this handler appends
name=&type= to (same call as Yandex.DNS and CZ.NIC ODVR).
Verified from outside RU: RA set, honest NXDOMAIN, non-truncated.
Add DNS.SB as a verified EU resolver with UDP and JSON DoH endpoints for #392.
OpenAI Codex assisted with issue review, verification, implementation, and tests.
Add Yandex.DNS (77.88.8.8), a reachable Russian public resolver, to the curated list. UDP-only: Yandex's DoH endpoint speaks RFC 8484 wire format rather than the application/dns-json API this endpoint queries.
Co-authored-by: OpenAI Codex <codex@openai.com>
Retarget the rescoped Europe-resolver issue (#392) to CZ.NIC's ODVR (193.17.47.1), a verified reachable European public resolver run by the .cz registry. UDP-only: its DoH endpoint does not serve the JSON API.
Co-authored-by: OpenAI Codex <codex@openai.com>
Replace the since-discontinued Quad101 with two verified Taiwan resolvers (issue #391 was rescoped to reachable public resolvers):
- HiNet (Chunghwa Telecom) 168.95.1.1
- GIGA (Taiwan Fixed Network) 203.133.1.6
Both are UDP-only (no JSON DoH endpoint). Also add a contributor rule to the data-file header requiring that a resolver actually answer with the ra flag before a PR, so future additions verify reachability instead of trusting published docs.
Co-authored-by: OpenAI Codex <codex@openai.com>
Move the resolver list into api/data/dns-resolvers.js as structured
per-country data so adding a resolver becomes a one-object PR, gated
by a new data-integrity test. The API returns one flat annotated list
and the UI grows badge-style region filter chips (flags + localized
names via Intl.DisplayNames) above the result table.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Thanut JongteerathanachoteandClaude Opus 5.5
jason5ng32
Aviraj Kumar
s4ge
fly1d
Jason Ng
