Latvia DNS Propagation Checker
Run a DNS lookup against 6 resolvers located in Latvia — Riga · Riga · Riga · Riga · Riga · Riga.
- Resolved
- No answer
- Checking
-
Riga
Latvia
—
-
Riga
Latvia
—
-
Riga
Latvia
—
-
Riga
Latvia
—
-
Riga
Latvia
—
-
Riga
Latvia
—
What checking DNS from Latvia 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 Latvia 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 Latvia until its cached copy expires. The check confirms the new value has reached the resolvers your Latvia visitors depend on.
Latvia's .lv zone has been run since 1993 by the Institute of Mathematics and Computer Science at the University of Latvia, trading as NIC.LV. The institute also runs a free public recursive resolver for the whole country, at 91.198.156.20 and 194.8.2.2, with DNSSEC validation and an RPZ firewall that redirects known phishing and fraud to a warning page — a national registry offering a filtered public resolver is a rare setup.
Most people never point at it. They use whatever their provider hands out: Tet on fixed lines (the former state operator, once Lattelekom), LMT or Bite on mobile. Checking a record from inside Latvia shows what those resolvers return, which is not always the raw record.
Two state lists shape those answers. The Lotteries and Gambling Supervision Inspection blacklists unlicensed gambling domains — well over 1,600 — that ISPs block under the Electronic Communications Law, and NEPLP orders blocks on EU-sanctioned Russian outlets like RT and Sputnik. Query one through Tet and you get a block; through 8.8.8.8, the real answer.
- NIC.LV (University of Latvia / IMCS)91.198.156.20 National registry's free public resolver, DNSSEC and RPZ filtering
- Tet Incumbent fixed-line ISP (ex-Lattelekom); most homes, with state blocks
- LMT (Latvijas Mobilais Telefons) Largest mobile network; carrier resolver enforces the same blocks
- Bite Latvija Mobile operator; default resolver applies the mandatory blocklists
Some answers from Latvian ISP resolvers are shaped by state blocking — unlicensed gambling domains (IAUI list) and EU-sanctioned Russian media (NEPLP) are filtered, so results can differ from public resolvers.
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 Latvia 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 Latvia 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 Latvia?
It depends on the record's time-to-live, not on the country.
Resolvers in Latvia 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 Latvia 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 Latvia, 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 Latvia specifically?
Because it shows what visitors in Latvia actually resolve, which can differ from a global lookup.
If your audience is in Latvia, or you have moved hosting or mail there, checking against in-country resolvers confirms the records have reached the servers those users rely on.
Does Latvia's national registry run a public DNS resolver I can use?
Yes. NIC.LV, run by the University of Latvia's Institute of Mathematics and Computer Science (which has managed the .lv zone since 1993), offers a free recursive resolver at 91.198.156.20 and 194.8.2.2, plus IPv6, DNS-over-HTTPS (https://doh.nic.lv/dns-query) and DNS-over-TLS. It does DNSSEC validation and runs a DNS firewall (RPZ) that redirects known phishing, malware and banking-fraud domains to a warning page, so it is a security-filtered resolver rather than a raw one.
Why does a domain resolve on 8.8.8.8 but get blocked on a Latvian ISP?
Latvian providers enforce two state block lists at the resolver. The Lotteries and Gambling Supervision Inspection (IAUI) keeps a blacklist of unlicensed gambling sites — well over 1,600 domains — that ISPs must block under the Electronic Communications Law, and NEPLP orders blocks on EU-sanctioned Russian media such as RT and Sputnik. Those blocks live in Tet, LMT and Bite's resolvers, not in the domain itself, so a public resolver like 8.8.8.8 or Quad9 returns the real record.
