India DNS Propagation Checker
Run a DNS lookup against 3 resolvers located in India — Bhavnagar · Pune · Mumbai.
- Resolved
- No answer
- Checking
-
Bhavnagar
India
—
-
Pune
India
—
-
Mumbai
India
—
What checking DNS from India tells you
A DNS resolver keeps a cached copy of each record for as long as its time-to-live allows, and does so separately in every location. A change you have published can be live on one resolver while another still serves the old answer.
Checking from India looks up the record on servers inside the country, so you see what people there actually get rather than what a resolver on another continent returns.
This matters most right after you edit a record: an update visible on a global resolver like 8.8.8.8 can still be stale at a local ISP in India until its cached copy expires. The check confirms the new value has reached the resolvers your India visitors depend on.
India's DNS answers vary by provider more than almost anywhere else, because website blocking here is ordered by courts and ministries but implemented separately by each ISP. One provider nulls a domain, another redirects it, a third has not gotten around to it, so the same lookup can succeed on Hathway and fail on a rival network the same afternoon.
The government runs its own public resolver too: Bharat Public DNS at 1.10.10.10, operated by the National Informatics Centre.
For anyone serving Indian users, and there are more of them on mobile alone than most countries have people, a check from inside India is the only realistic way to see this patchwork: which resolvers hold your current records, and whether any of them treat your domain differently.
- Bharat Public DNS1.10.10.10 Run by the government's National Informatics Centre
- CtrlS Hyderabad data-center operator's resolvers
- Hathway Big cable ISP serving millions of households
How DNS propagation works
Every DNS record carries a time-to-live: the seconds a resolver may keep its cached answer before asking again. Change a record and resolvers holding the old value keep serving it until that timer runs out.
Propagation is this expiry playing out across many independent resolvers, so a lower time-to-live set ahead of a change makes it take effect sooner. There is no fixed waiting period — each record's time-to-live decides how long the old answer lingers.
Frequently Asked Questions
Why do DNS servers in India return different results than 8.8.8.8?
Two things cause it. Each resolver caches independently, so one can hold an older answer than another.
And content delivery networks reply based on where the asking resolver is, steering a resolver in India toward a nearby edge node.
Both answers can be correct at the same time for their own location.
How long until a DNS change is visible in India?
It depends on the record's time-to-live, not on the country.
Resolvers in India keep the previous answer until their cached copy expires, then pick up the new one.
If you lowered the time-to-live before making the change, it appears sooner; otherwise the old value can persist until the original timer elapses.
Which DNS server should users in India use?
For most people the resolver their internet provider assigns is fine and usually the lowest latency.
Anyone who wants an alternative can point to a public resolver reachable from India, such as Cloudflare (1.1.1.1) or Google (8.8.8.8); the right choice depends on whether you value speed, privacy, or filtering.
Why check DNS from India specifically?
Because it shows what visitors in India actually resolve, which can differ from a global lookup.
If your audience is in India, or you have moved hosting or mail there, checking against in-country resolvers confirms the records have reached the servers those users rely on.
Why does my domain resolve on one Indian ISP but not another?
Blocking orders in India go to each ISP individually, and each implements them with different tools and different lag. If your domain is not the target of an order, differences between Indian ISPs are ordinary cache lag and expire with the TTL. Persistent failure on a single provider is worth investigating as a filtering false positive.
What is 1.10.10.10?
Bharat Public DNS, a free public resolver operated by the National Informatics Centre, the agency that runs most Indian government IT. It is pitched on queries staying within India. For a propagation check it is useful as a government-run test point alongside the commercial ISPs.
