Lithuania DNS Propagation Checker
Run a DNS lookup against 6 resolvers located in Lithuania — Kaunas · Kaunas · Kaunas · Vilnius · Šiauliai · Kaunas.
- Resolved
- No answer
- Checking
-
Kaunas
Lithuania
—
-
Kaunas
Lithuania
—
-
Kaunas
Lithuania
—
-
Vilnius
Lithuania
—
-
Šiauliai
Lithuania
—
-
Kaunas
Lithuania
—
What checking DNS from Lithuania 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 Lithuania 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 Lithuania until its cached copy expires. The check confirms the new value has reached the resolvers your Lithuania visitors depend on.
When Lithuania's Radio and Television Commission (LRTK) finds a fresh mirror of a sanctioned Russian channel or a pirate stream, it sends one instruction to every ISP and the domain is blocked nationwide. Since 2022 it has ordered blocks on Russian state media under EU sanctions, treating the list as national defence rather than copyright housekeeping.
It is not the only one. The Gaming Control Authority (Lošimų priežiūros tarnyba) keeps a list of unlicensed gambling sites — well over a thousand domains — and its resolver-level blocks redirect you to a blokuojama.lpt.lt notice page instead of the real record. Almost nobody here picks a resolver; households take whatever Telia, Tele2 or Bitė hands out, and those resolvers carry both lists.
Checking a record from inside Lithuania shows what those resolvers return, block pages included, not the clean answer 8.8.8.8 gives abroad. A domain that resolves on a public resolver but returns a block page or a dead IP on Telia is filtered, not lagging in propagation.
- Telia Lietuva Incumbent (ex-TEO/Omnitel); default resolver, carries state blocks
- Tele2 Large mobile network; default resolver, same mandated blocks
- Bitė Lietuva Third national operator; applies the same DNS blocks
- Google Public DNS8.8.8.8 Common escape hatch, but IP blocks still bite
Answers from Lithuanian ISP resolvers reflect state blocklists — unlicensed gambling (Gaming Control Authority) and EU-sanctioned Russian media and piracy (Radio and Television Commission) — so a blocked domain can return a block page or dead IP locally while resolving normally on a public resolver abroad.
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 Lithuania 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 Lithuania 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 Lithuania?
It depends on the record's time-to-live, not on the country.
Resolvers in Lithuania 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 Lithuania 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 Lithuania, 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 Lithuania specifically?
Because it shows what visitors in Lithuania actually resolve, which can differ from a global lookup.
If your audience is in Lithuania, 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 a site load on 8.8.8.8 but show a block page on my Lithuanian ISP?
Lithuania enforces official blocklists at the ISP resolver. The Gaming Control Authority's unlicensed-gambling domains are redirected to a blokuojama.lpt.lt notice page, and the Radio and Television Commission pushes its sanctions and piracy list to every provider. A public resolver like 8.8.8.8 or 1.1.1.1 does not carry those lists, so it returns the real record. One caveat: the commission also blocks by IP, and an IP block still bites whichever resolver you point at.
Who decides what gets blocked in Lithuania?
Several state bodies, each with its own list. The Gaming Control Authority (Lošimų priežiūros tarnyba) targets unlicensed gambling and publishes its blocklist openly, blocking administratively rather than case-by-case through the courts. The Radio and Television Commission (LRTK) handles EU-sanctioned Russian media and pirate streaming, blocking both by domain and by IP. ISPs apply all of it against the default resolvers most households never change, which is why an in-country check can disagree with a lookup from abroad.
