Israel

Israel DNS Propagation Checker

Run a DNS lookup against 6 resolvers located in Israel — Jerusalem · Jerusalem · Ramat HaSharon · Ramat HaSharon · Regba · Tel Aviv.

Please enter a valid domain name.

Checking from 6 locations
  • Resolved
  • No answer
  • Checking
Jerusalem31.79° N, 35.19° EJerusalem31.79° N, 35.19° ERamat HaSharon32.14° N, 34.85° ERamat HaSharon32.14° N, 34.85° ERegba32.97° N, 35.10° ETel Aviv32.08° N, 34.78° E
  • IL Jerusalem Israel
  • IL Jerusalem Israel
  • IL Ramat HaSharon Israel
  • IL Ramat HaSharon Israel
  • IL Regba Israel
  • IL Tel Aviv Israel

What checking DNS from Israel tells you

Caching is local

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.

The in-country view

Checking from Israel 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.

When it matters

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 Israel until its cached copy expires. The check confirms the new value has reached the resolvers your Israel visitors depend on.

Field notes

Israel's consumer internet grew up around NetVision, one of the country's first ISPs, which sold dial-up accounts from 1994 and still answers DNS on 194.90.1.5 — Cellcom bought the company in 2011 and kept the resolver running. Alongside it sit Bezeq International and the cable operator HOT. Between them, most Israeli homes get whatever resolver their provider hands out rather than one they chose.

That makes checking a record from inside Israel worth doing: you see what these ISP resolvers actually return, not what 8.8.8.8 reports from abroad. Since a 2017 law, Israeli courts can order ISPs to block domains tied to unlicensed gambling and other offenses, and providers apply those orders at the resolver. A name that resolves cleanly on Cloudflare can come back empty or point to a block notice here.

Local resolvers
  • NetVision (Cellcom)194.90.1.5 Among Israel's first ISPs; resolver now run by Cellcom
  • Bezeq International Largest fixed-line ISP group; carries court-ordered blocks
  • HOT (Hot-Net) Main cable ISP; default resolver for its broadband base

Some domains, mainly unlicensed gambling and other court-flagged illegal content, are blocked at the ISP resolver level in Israel, so answers for those names can differ from a global public resolver.

How DNS propagation works

The TTL timer

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.

Staggered expiry

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 Israel 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 Israel 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 Israel?

It depends on the record's time-to-live, not on the country.

Resolvers in Israel 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 Israel 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 Israel, 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 Israel specifically?

Because it shows what visitors in Israel actually resolve, which can differ from a global lookup.

If your audience is in Israel, or you have moved hosting or mail there, checking against in-country resolvers confirms the records have reached the servers those users rely on.

Do Israeli ISPs block websites through DNS?

Yes. Under the 2017 'Powers to Prevent Offenses Through an Internet Site' law, courts can order ISPs to block domains tied to unlicensed gambling, drugs, prostitution, and similar offenses, and providers carry those orders out at the resolver. A blocked domain returns nothing or a notice page from an Israeli ISP resolver while resolving normally on a foreign public resolver like 8.8.8.8, which is why checking from inside the country and from outside can disagree.

Who runs the .il domain and Israel's internet exchange?

The Israel Internet Association (ISOC-IL) manages the .il registry and operates the Israel Internet Exchange (IIX) in Petah Tikva, where local ISPs peer with each other. It also hosts a copy of a DNS root server, so root lookups from Israeli networks can be answered domestically instead of crossing overseas links.