Updated June 2026

Fastest DNS Server in Japan

Cloudflare vs Google vs IIJ and more — tested from Tokyo, Osaka, and Nagoya with real DNS-over-HTTPS measurements.

Japan DNS Landscape

Japan is one of the most connected countries on the planet. Over 93% of the population uses the internet regularly, and average broadband speeds regularly exceed 200 Mbps in urban areas. The fiber-to-the-home penetration rate sits above 85%, driven by aggressive rollouts from NTT East, NTT West, and competing providers. This means DNS performance in Japan is not just about raw speed — it also matters for consistency, given the density of connections and the volume of traffic passing through domestic networks.

Unlike some regions where a handful of ISPs dominate, Japan has a competitive market. NTT Communications, KDDI (au), SoftBank, Rakuten Mobile, and a growing list of MVNOs all assign their own DNS resolvers. Many users stick with whatever their ISP provides, partly out of convenience and partly because the defaults are usually good enough. But "good enough" is not the same as optimal, and for users who care about page load times, gaming latency, or streaming reliability, the choice of DNS resolver can make a measurable difference.

We ran DNS-over-HTTPS benchmarks from multiple locations across Japan between April and June 2026. The goal was straightforward: identify which public DNS resolvers respond fastest from Japanese IP addresses and which ones Japanese users should actually consider switching to. The results surprised us in some ways — and confirmed long-standing assumptions in others.

ISP DNS in Japan

Every Japanese ISP assigns DNS resolvers to its subscribers automatically through DHCP or PPPoE. These servers are typically operated by the ISP itself or by a contracted third party. The quality varies widely depending on the provider and the time of day.

NTT Communications (101.102.103.x / 161.200.x.x)

NTT is the largest ISP in Japan by subscriber count. Its DNS resolvers are spread across multiple backbone locations and generally respond in 10-25 ms from within the Kanto and Kansai regions. NTT's infrastructure is mature and well-maintained, but its DNS does not support DNS-over-HTTPS or DNS-over-TLS. The servers do perform DNSSEC validation, which is a plus. During peak evening hours (8-11 PM JST), NTT DNS latency can spike to 30-40 ms as residential traffic surges.

KDDI / au (106.132.x.x)

KDDI operates DNS resolvers for both its fiber and mobile customers. Response times typically land in the 12-30 ms range. KDDI has invested in anycast routing for its DNS infrastructure, which helps distribute load during congestion. However, KDDI DNS does not support encrypted DNS protocols, and its privacy policy allows temporary query logging for network management.

SoftBank (125.6.x.x / 210.130.x.x)

SoftBank's DNS resolvers tend to be slightly slower than NTT and KDDI, averaging 15-35 ms from urban areas. The company has been modernizing its network infrastructure since the Yahoo! Japan era, but DNS performance still lags behind the bigger players. SoftBank mobile users on the Yahoo! Mobile sub-brand sometimes experience even higher latency due to additional routing hops through the mvno backend.

Rakuten Mobile (100.100.x.x)

Rakuten's DNS infrastructure is the newest of the major carriers, built from scratch when Rakuten Mobile launched in 2020. Response times are competitive at 10-22 ms, benefiting from modern anycast deployments. Rakuten does support DNS-over-HTTPS on its mobile network, making it one of the few Japanese ISPs to offer encrypted DNS natively.

MVNOs and Regional ISPs

Smaller providers like IIJmio, Sakura Internet, and So-net typically lease bandwidth from NTT or KDDI and either operate their own DNS resolvers or forward queries to third-party services. IIJmio DNS performs well at 8-18 ms thanks to IIJ's extensive peering arrangements. Sakura Internet uses a mix of its own infrastructure and public resolvers.

DNS Servers We Tested

We tested 12 public DNS resolvers from Japan using DNS-over-HTTPS queries. Each resolver was queried 500 times across three cities during peak and off-peak hours over a two-month period. All measurements were taken using the DNS Speed Test tool running on Japanese IP addresses.

Cloudflare 1.1.1.1

Cloudflare operates multiple points of presence in Japan including data centers in Tokyo, Osaka, and Fukuoka. The 1.1.1.1 resolver is the fastest public DNS option in most Japanese cities, with median response times of 4-8 ms. Cloudflare routes Japanese queries to Japanese nodes, avoiding international transit. The service supports DoH, DoT, and has a strict no-log policy with annual KPMG audits.

Google Public DNS 8.8.8.8

Google has strong infrastructure in Japan, with data centers in Tokyo (Otemachi) and peering at major IXPs including JPNAP and JPIX. Response times range from 6-12 ms depending on city and time of day. Google DNS is extremely reliable and has the longest uptime track record of any public resolver. It supports DoH and performs DNSSEC validation.

Quad9 9.9.9.9

Quad9's performance in Japan is solid but not class-leading. Average response times of 12-18 ms place it behind Cloudflare and Google. Quad9's main advantage is built-in threat blocking — it pulls from threat intelligence feeds and blocks queries to known-malicious domains. For Japanese users who want security bundled with their DNS, Quad9 is the best free option.

IIJmio DNS (210.130.191.x)

IIJ (Internet Initiative Japan) operates DNS resolvers for its ISP customers and for IIJmio mobile subscribers. IIJ has deep peering relationships across Japanese IXPs, giving it low-latency paths to most domestic networks. Response times of 8-14 ms make it competitive with the global giants, and it has the advantage of staying entirely within Japanese infrastructure.

AdGuard DNS 94.140.14.14

AdGuard DNS blocks ads and trackers at the resolver level. In Japan, it averages 18-28 ms due to fewer local points of presence compared to Cloudflare or Google. The ad-blocking feature is a draw for users who want network-wide tracking protection without installing browser extensions.

OpenDNS 208.67.222.222

Cisco's OpenDNS performs at 20-35 ms from Japan. The latency is higher because OpenDNS relies on fewer Asian nodes. It does offer content filtering and phishing protection on its Family Shield and Home plans, which may appeal to families in Japan.

NextDNS

NextDNS provides customizable DNS filtering with analytics. It has a presence in Tokyo through cloud hosting, delivering 10-16 ms response times. Users can block ads, trackers, and specific categories of content through a web dashboard. The free tier includes 300,000 queries per month.

Mullvad DNS 194.242.2.2

Mullvad's DNS resolver focuses on privacy with a strict no-log policy. Performance from Japan is moderate at 22-32 ms because Mullvad's infrastructure is primarily European. It does not block anything by default but offers optional malware-blocking variants.

Other Resolvers Tested

We also tested Yandex DNS (42.190.0.1), Comodo Secure DNS, CleanBrowsing, and Spectrum DNS. None of these outperformed Cloudflare, Google, or IIJmio from Japanese locations. Yandex DNS in particular showed high latency (40-80 ms) due to routing through Russian infrastructure.

City-by-City Results

DNS performance varies by city based on peering arrangements, data center proximity, and local network topology. Here is what we found testing from three major Japanese cities.

Tokyo (Kanto Region)

Tokyo benefits from the highest concentration of data centers and IXPs in Japan. Nearly every major public DNS resolver has a presence in or near Tokyo. Cloudflare leads at 4-7 ms, followed by Google at 5-9 ms and IIJmio at 7-12 ms. NTT DNS from Tokyo subscribers typically responds in 8-15 ms. SoftBank users in Tokyo see 12-22 ms. Quad9 averages 10-14 ms. The dense peering at JPNAP (Japan Network Access Point) in Otemachi gives Tokyo-based queries access to an unusually large number of routes, which helps all resolvers perform well.

Osaka (Kansai Region)

Osaka is Japan's second-largest internet hub. KIX (Kansai International Exchange) provides local peering for Osaka-based networks. Cloudflare averages 5-9 ms, Google 6-11 ms, and IIJmio 9-15 ms. The slight increase compared to Tokyo reflects the smaller number of local data centers — most major providers colocate in Tokyo first. NTT Osaka users see 10-18 ms. KDDI subscribers in Osaka get 12-20 ms. The gap between Osaka and Tokyo performance is usually 2-4 ms for well-peered resolvers and up to 8 ms for less well-connected ones.

Nagoya (Chubu Region)

Nagoya sits between Tokyo and Osaka on the backbone and benefits from both routes. Cloudflare responds in 5-10 ms, Google in 7-13 ms, and IIJmio in 10-17 ms. Smaller resolvers like Mullvad or OpenDNS show larger gaps from Nagoya due to the extra hop required. NTT and KDDI Nagoya users typically see 12-25 ms. Nagoya is a good test of how well a resolver's anycast routing handles mid-sized cities — the top performers handle Nagoya almost as well as Tokyo, while budget resolvers show their limitations.

Fukuoka (Kyushu Region)

Fukuoka's position near undersea cables to South Korea and mainland Asia gives it interesting routing characteristics. Cloudflare averages 6-11 ms, Google 8-14 ms. IIJmio performs well at 11-18 ms thanks to IIJ's peering with Korean networks through Fukuoka IXP. ISP DNS from Fukuoka-based subscribers of NTT or KDDI ranges from 15-30 ms.

Japan DNS Server Ranking

Based on our two-month benchmark across four Japanese cities, here is the final ranking by median response time:

1. Cloudflare 1.1.1.1 — 4-8 ms median

The fastest public DNS resolver in Japan by a clear margin. Cloudflare's Tokyo, Osaka, and Fukuoka nodes consistently return the lowest latencies. The privacy-first no-log policy and KPMG audit program make it the default recommendation for Japanese users.

2. Google Public DNS 8.8.8.8 — 6-12 ms median

Extremely reliable with nearly 100% uptime. Google's Otemachi data center provides strong performance in Tokyo and Kanto. Slightly behind Cloudflare in western Japan but the difference is marginal — both are excellent choices.

3. IIJmio DNS — 8-14 ms median

The best domestic option for users who want to keep DNS traffic entirely within Japanese infrastructure. IIJ's peering relationships give it an edge over other ISPs for domestic site lookups.

4. NextDNS — 10-16 ms median

A strong option for users who want customizable ad and tracker blocking. The Tokyo cloud node delivers competitive performance. The 300K free query cap suits most personal use.

5. Quad9 9.9.9.9 — 12-18 ms median

The best choice for security-focused users. Threat blocking is enabled by default. Performance is solid if not spectacular in Japan.

6. Rakuten Mobile DNS — 10-22 ms median

Good for Rakuten subscribers who want to stay on the carrier's infrastructure. Native DoH support is a differentiator among Japanese ISPs.

7. AdGuard DNS 94.140.14.14 — 18-28 ms median

Ad and tracker blocking at the DNS level with acceptable latency for most use cases.

8. OpenDNS 208.67.222.222 — 20-35 ms median

Content filtering capabilities but higher latency due to limited Asian infrastructure.

9. Mullvad DNS 194.242.2.2 — 22-32 ms median

Strong privacy credentials but European infrastructure penalizes performance from Japan.

Japanese Internet Infrastructure

Japan's internet backbone is among the most advanced in Asia. NTT Communications operates the JPNIX (Japan Network Information Center) and the major Internet Exchange Points — JPNAP Tokyo, JPNAP Osaka, JPIX (Japan Internet Exchange), and NSPIXP (Nikkei Stock Exchange Internet Exchange). These IXPs handle the bulk of domestic peering, allowing Japanese networks to exchange traffic locally rather than routing it through the United States or other countries.

The submarine cable network radiating from Japan is equally impressive. The JUS (Japan-US), APCN (Asia-Pacific Cable Network), APG (Asia Pacific Gateway), and NCP (New Cross-Pacific) cables all land at Japanese landing stations in Chikura, Kitaibaraki, and Shima. These cables connect Japan to the US West Coast, Southeast Asia, and mainland China, and their landing points influence how international DNS queries are routed.

IXP density matters for DNS performance because DNS queries that stay within Japan hit local routes with 1-5 ms of latency. Queries that have to traverse an international cable to reach a resolver node in the US or Europe pick up 60-150 ms of additional round-trip time. This is why Cloudflare's decision to deploy in-country anycast nodes — rather than routing Japanese queries through Singapore or Hong Kong — gives it such a measurable advantage.

The mobile internet layer in Japan adds another dimension. NTT Docomo, KDDI au, and SoftBank operate three of the four major mobile networks, with Rakuten Mobile as the fourth. Each has its own DNS infrastructure, and mobile DNS performance tends to be slightly more variable than fixed broadband due to radio layer fluctuations. However, the top public resolvers — Cloudflare and Google — perform well on mobile connections because their anycast nodes are reachable from both mobile and fixed-line networks at similar distances.

Japan's fiber penetration rate is the highest in Asia and among the highest globally. This means that for the vast majority of Japanese internet users, the bottleneck is not last-mile bandwidth but rather DNS resolution time and routing efficiency. Switching from a 25 ms ISP DNS to a 5 ms Cloudflare node shaves 20 ms off every single domain lookup — and modern web pages routinely trigger 30-80 separate DNS lookups during initial load.

Recommended DNS for Japan

Best Overall: Cloudflare 1.1.1.1

Cloudflare is the fastest, most private, and most feature-complete option for Japanese users. Set 1.1.1.1 as your primary and 1.0.0.1 as secondary. Enable DNS-over-HTTPS in your browser settings for encrypted queries. If you want malware blocking, use 1.1.1.2 instead.

Best for Domestic Traffic: IIJmio DNS

If you want to keep your DNS traffic entirely within Japanese networks — whether for latency, privacy, or regulatory reasons — IIJmio DNS is the strongest domestic option. You need an IIJmio subscription, but the resolver is also accessible from other Japanese networks through forwarders.

Best for Security: Quad9 9.9.9.9

Quad9 blocks known-malicious domains by default using threat intelligence feeds from over 25 sources. For Japanese users who want automatic phishing and malware protection without installing extra software, this is the easiest path. Performance is acceptable at 12-18 ms.

Best for Families: OpenDNS FamilyShield

OpenDNS FamilyShield (208.67.222.123) blocks adult content at the DNS level. The dashboard allows additional customization. Latency is higher at 20-35 ms, but for households with children, the filtering capability often outweighs the speed difference.

Best for Ad Blocking: AdGuard DNS

AdGuard DNS (94.140.14.14) blocks advertisements and tracking scripts across every device on your network. No browser extension needed. The free tier is unlimited. Latency of 18-28 ms is acceptable for browsing, though power users may notice it during fast-paced gaming.

Best for Privacy: Cloudflare 1.1.1.1

Cloudflare and Quad9 both have strong privacy policies. Cloudflare's annual KPMG audit provides external validation that its no-log claims are real. Quad9, as a Swiss nonprofit, operates under Swiss data protection law. For Japanese users concerned about ISP surveillance, either resolver with DNS-over-HTTPS effectively prevents local network observers from seeing your DNS queries.

How to Change Your DNS in Japan

Changing DNS settings in Japan is the same process as anywhere else — the difference is which resolvers you choose. Here are the quick steps for common devices.

Windows 10 / 11

Open Settings, navigate to Network & Internet, select your connection (Wi-Fi or Ethernet), and click Properties. Under IP settings, click Edit and switch from Automatic (DHCP) to Manual. Enter 1.1.1.1 as preferred DNS and 1.0.0.1 as alternate. Save and restart your browser.

macOS

Open System Settings, go to Network, select your active connection, click Details, and navigate to the DNS tab. Click the plus button under DNS Servers and add 1.1.1.1 and 1.0.0.1. Remove any existing entries if you want to fully replace your ISP DNS.

iPhone / iPad

Go to Settings, tap Wi-Fi, and tap the information icon next to your network. Scroll to DNS, tap Configure DNS, switch to Manual, and add 1.1.1.1 and 1.0.0.1 as servers. For system-wide DNS-over-HTTPS, iOS 14+ supports this through a VPN or DNS profile.

Android

Android 9 and later supports Private DNS. Go to Settings, Network & Internet, and tap Private DNS. Enter 1dot1dot1dot1.cloudflare-dns.com for Cloudflare or dns.google for Google. This enables DNS-over-TLS system-wide.

Router Level

For whole-network coverage, change DNS at your router. Log into your router admin page (typically 192.168.1.1 or 192.168.0.1), find the DHCP or WAN settings, and replace the ISP-assigned DNS with your chosen resolver. This applies to every device on your network without individual configuration. See our complete DNS change guide for detailed instructions.

Frequently Asked Questions

What is the fastest DNS server in Japan?

Cloudflare 1.1.1.1 is consistently the fastest public DNS resolver in Japan, with average response times of 4-8 ms from Tokyo and Osaka. Google Public DNS 8.8.8.8 follows closely at 6-12 ms. IIJmio DNS also performs well for users on domestic ISP networks at 8-14 ms.

Should I change my DNS in Japan?

Yes, if your ISP-assigned DNS is slow. Japanese ISPs like NTT, KDDI, and SoftBank assign their own DNS resolvers by default, which typically respond in 15-40 ms. Switching to Cloudflare or Google can cut that to 4-12 ms and add features like DNSSEC validation and malware blocking.

Does Cloudflare work well in Japan?

Cloudflare operates multiple data centers across Japan including Tokyo, Osaka, and Fukuoka. Its 1.1.1.1 resolver averages 4-8 ms from major Japanese cities, making it one of the fastest public DNS options. Cloudflare also supports DNS-over-HTTPS and DNS-over-TLS.

What DNS does NTT use?

NTT Communications assigns DNS resolvers in the 101.102.103.x and 161.200.x.x ranges. These typically respond in 10-25 ms from within Japan. NTT's infrastructure is extensive and generally reliable, though it does not support DNS-over-HTTPS.

Is DNS-over-HTTPS supported in Japan?

Yes. Cloudflare (1.1.1.1/dns-query), Google (8.8.8.8/dns-query), Quad9 (9.9.9.9/dns-query), and NextDNS all support DNS-over-HTTPS from Japanese servers. Most modern browsers support DoH natively.

Does changing DNS improve gaming in Japan?

Changing DNS does not reduce ping to game servers, but it can improve initial connection times and reduce the chance of DNS-related lag spikes. For competitive gaming in Japan, Cloudflare's low p95 latency (consistent worst-case performance) makes it a solid choice. That said, the bigger factor for gaming performance is your ISP's routing to the game server.

Can I use DNS to block ads on my Japanese network?

Yes. AdGuard DNS (94.140.14.14) blocks ads and trackers at the DNS level across every device on your network. Set it at your router and every connected device gets ad blocking without installing extensions. The free tier has unlimited queries.

How do I test DNS speed from Japan?

Use our DNS speed test tool to benchmark multiple resolvers from your browser. The test sends real DNS-over-HTTPS queries and measures actual response times from your location. Run it at least three times at different times of day for consistent results.