Guide · DNS

Fastest public DNS servers in India

No public DNS is fastest for every connection in India. Cloudflare, Google, and Quad9 are the resolvers people compare, and the winner is whichever anycast site your ISP reaches with the least delay. Measure from your own line. A filtered resolver such as Quad9 also blocks some malware names, which is a different goal from raw speed.
A man in a navy polo tapes a cardboard box beside an open laptop in a stock room.

Which public DNS is fastest from India?

There is no single fastest public DNS for India. Cloudflare at 1.1.1.1, Google at 8.8.8.8, and Quad9 at 9.9.9.9 answer from the anycast site your ISP reaches. A resolver that is quick on one line can be slower on another. Time the lookup on the connection you use, and treat a national ranking you did not measure as a rumour.

WebJi® does not publish one national winner, because the anycast hop differs by ISP. Measure your own line with a ping test, then read the answer path with a DNS lookup. A low ping to an address is not the same thing as a fast name lookup, so use both.

How do Google, Cloudflare, Quad9, and the others compare?

Cloudflare, Google, Quad9, and OpenDNS answer public names, but the extras differ. Quad9's default addresses block known malware domains. The default Google and Cloudflare pairs do not. OpenDNS can filter categories. Use the filtered pair when you want that block list, and the unfiltered pair when a block would break an application.

ResolverIPv4What is different
Cloudflare1.1.1.1 and 1.0.0.1Default pair is not a malware filter
Google Public DNS8.8.8.8 and 8.8.4.4Default pair is not a malware filter
Quad99.9.9.9 and 149.112.112.112Blocks known malware domains
Quad9, unfiltered9.9.9.10 and 149.112.112.10Same network, no block list
Cisco OpenDNS208.67.222.222 and 208.67.220.220Home product can filter categories

Pick two addresses from one row. Mixing a primary from one company with a secondary from another makes failures harder to explain.

How do you change DNS on Windows, Mac, Android, and a router?

Changing DNS tells the computer or the router which resolver to ask. Write the current addresses down first. Enter two addresses from the same provider. Apply the change, flush the cache, and look up a name you know. A router change covers devices on that router. A laptop change covers only that laptop.

DeviceWhere the setting lives
Windows 10 and 11Network adapter, IPv4 or IPv6, DNS server addresses
macOSSystem Settings, Network, the active service, DNS
AndroidPrivate DNS as a hostname, or the Wi-Fi network IP settings
RouterDHCP or WAN DNS, so every client inherits the pair
  1. Write down the addresses you have now.
  2. Enter the two addresses from one resolver.
  3. Apply, then flush the local cache.
  4. Look up a name you already know and confirm the answer.

How is a public resolver different from your domain name servers?

The resolver on your computer finds names for you. The name servers on a domain are the published source for that domain. Changing 1.1.1.1 on a laptop does not move your website. Changing name servers at the registrar does. This page stops at that split. The nameserver guide owns the authoritative side, and the DNS guide owns the definition.

If the website moved and the rest of the world still sees the old host, the name servers or the records are the place to look. Changing the resolver on a laptop will not fix that. This page does not walk through authoritative records.

How do you fix DNS server not responding?

DNS server not responding usually means this computer cannot reach a resolver, not that the website was deleted. Try a phone hotspot to see whether the fault follows the PC. Set a known public pair, flush the cache, and restart the router. If only one domain fails, stop editing your resolver and check that domain's name servers instead.

  1. Try a phone hotspot. If the error vanishes, the fault is the first network.
  2. Set a known public pair from the table, temporarily.
  3. Flush the cache and restart the router.
  4. If every site works except one domain, put the old resolver back and check that domain's name servers.

Need help with this?

WebJi® support does it for you — free. Talk to our Jaipur team →