DNS is the internet's phone book. When you type a site name, your device asks a DNS server: what is its IP address? That answer is used to open the connection.
By default, that question is answered by your ISP's servers. Switching to another provider is advice that surfaces for all sorts of complaints, from slow internet to sites that will not open. Some of the claims have basis, some do not.
What happens when you open a site
The sequence runs roughly like this:
- The device checks its local cache. If the address was looked up recently, the process stops here.
- If not, the question goes to the configured DNS server, the ISP's default, or one you chose.
- That server answers, or asks a more authoritative server in turn.
- The device receives the IP address and starts opening a connection to it.
The whole process usually takes 10–80 milliseconds, and happens only once per domain until the cache expires. This matters for understanding the limits of the benefit.
On speed
The claim that "changing DNS makes the internet fly" needs putting in proportion. What changes is the address lookup time, not the data transfer rate.
| Activity | Effect of DNS |
|---|---|
| Opening a site with many third-party domains | Slightly noticeable |
| Moving between new sites | Slightly noticeable |
| Video streaming | Practically none |
| Downloading large files | Practically none |
| Video calls | Practically none |
A news page can load resources from twenty different domains. Saving 30 milliseconds per domain is genuinely noticeable. But if your complaint is stuttering video, DNS is not where to look, see the guide to slow Wi-Fi instead.
One exception: if your ISP's DNS servers are having trouble, the symptom is sites taking an age to open then suddenly appearing, or "server not found" messages that disappear on retry. In that case changing DNS genuinely helps.
On privacy
This is the most misunderstood part.
With ordinary DNS, queries are sent unencrypted. Anyone on the path, including your ISP and the Wi-Fi operator whose network you are using, can read them. Changing the DNS server does not alter this, the queries remain open, only their destination moves.
What does alter it is DNS over HTTPS (DoH) or DNS over TLS (DoT). Both wrap the query in an encrypted connection.
But there is a limit. Once the IP address is obtained, your device still opens a connection to it. The ISP sees that destination IP address. For many sites, the IP address alone is enough to reveal which site was opened.
So DoH hides the question, not the destination. If what you want is to hide where a connection is going from the network operator, a VPN is what answers that need.
Content filtering
Some DNS providers offer versions that block malicious domains, ads, or adult content. This is a real benefit and easy to apply to a whole household at once through the router's settings.
| Provider | Address | Notes |
|---|---|---|
| Cloudflare | 1.1.1.1 | No filtering |
| Cloudflare Family | 1.1.1.3 | Blocks malware and adult content |
| 8.8.8.8 | No filtering | |
| Quad9 | 9.9.9.9 | Blocks malicious domains |
| AdGuard DNS | 94.140.14.14 | Blocks ads and trackers |
DNS-based filtering works at the domain name level, so it cannot block ads served from the same domain as the content. Effectiveness varies.
On blocked sites
Changing DNS sometimes opens sites that were previously inaccessible. This works when the blocking is done the simplest way, by having the provider's DNS server answer with the address of a notice page.
Newer blocking methods no longer depend on DNS. If the filtering reads the domain name inside the connection or blocks the destination IP address, changing DNS makes no difference.
It is also worth noting that opening access to officially blocked services carries its own consequences. This article explains how the mechanism works; it does not recommend using it for any particular purpose.
What's different on Indonesian networks
Most DNS guides are written for countries whose networks don't intercept DNS traffic. Indonesia is different, and that explains why so many people feel they "changed DNS and nothing happened".
Plain DNS is often diverted to the ISP's server
Since 2015, the regulator has required home and mobile ISPs to redirect DNS traffic on port 53 for filtering purposes. As a result, typing 8.8.8.8 or 1.1.1.1 into your settings doesn't guarantee that Google or Cloudflare answers your queries. Plain, unencrypted DNS queries can be intercepted on the way and answered by the ISP's server. The setting still says 8.8.8.8; the server answering isn't.
What escapes this diversion is encrypted DNS, meaning DoH or DoT. But some ISPs also block the domain names of DoH and DoT services. When that happens, Private DNS on Android fails to connect, and the phone may decide the Wi-Fi has no internet. What follows is covered in phone keeps switching to mobile data.
Blocking no longer relies only on DNS
Since around 2022, filtering has also been done through packet inspection. For HTTPS sites on the block list, the connection is cut mid-way, whatever DNS you use. That's why DoH makes your queries more private but doesn't open blocked sites.
Checking a domain's status
The list of blocked sites is managed by Komdigi (formerly Kominfo) through TrustPositif at trustpositif.komdigi.go.id. There you can search for a domain, download the block list, and file a normalisation request. That last feature is useful for business owners whose site was blocked by mistake, for example because it shares an address on cheap hosting.
Making sure your chosen DNS is really in use
If you use Cloudflare, open one.one.one.one/help from the device you want to check. The page shows whether you are really connected to 1.1.1.1 and whether queries use DoH or DoT. Do it twice, over home Wi-Fi and over mobile data, because the results can differ.
| Check result | What it means |
|---|---|
| Connected to 1.1.1.1: no, even though you set it manually | Queries are being diverted by the ISP |
| Connected: yes, DoH or DoT: no | Using Cloudflare, but queries can still be read on the path |
| Connected: yes, DoH or DoT: yes | Queries are encrypted all the way to Cloudflare |
For families at home
The most sensible reason to change DNS in an Indonesian home is usually not speed but filtering for children. Because plain DNS can be diverted, setting family DNS in the router's DNS fields doesn't always behave as hoped. A more reliable option is Private DNS on the child's phone, using the provider's family hostname, together with parental controls on the router. On some ISP-supplied ONTs, the DNS fields also can't be changed from an ordinary user account. How to log in and what the limits are is in how to log in to the router admin page.
On privacy, remember too that public DNS providers are generally foreign companies. Indonesia's Personal Data Protection Law (UU 27/2022) gives you rights over your personal data, but enforcing those rights against a company abroad is much harder than against a local one. Read the privacy policy before you choose.
How to change it
On the router, applies to the whole house
Sign into the admin page, find the WAN or Internet menu, then fill in the "Primary DNS" and "Secondary DNS" fields. Every connected device follows, except those with their own setting.
On Windows
Settings › Network & Internet › select the adapter › Edit DNS server assignment › Manual › enter the addresses. There is an "Encrypted only" option to enable DoH.
On Android
Settings › Network & internet › Private DNS › enter a hostname, for
example one.one.one.one. This setting uses DoT and applies on every network, including
mobile data.
On iOS and macOS
For a single network: Settings › Wi-Fi › the (i) icon › Configure DNS › Manual. To apply it system-wide, providers usually supply a configuration profile that can be installed.
In the browser
Chrome and Firefox have their own DoH settings that ignore the system setting. This can be confusing: filtering you set up on the router then does not apply to browser traffic. If you rely on router-level filtering, turn DoH off in the browser.
In short
Changing DNS is a small change with a benefit that is also small but real: address lookups get slightly faster, and filtering of malicious domains can be added for the whole house at once.
What it does not do: speed up downloads, hide your activity from your ISP, or replace a VPN. Those are the claims that leave people disappointed after trying it.
Frequently asked questions
Does changing DNS make the internet faster?
The effect exists but is small, and only at the address lookup stage. The saving is usually tens of milliseconds per new domain and is not felt in downloads or streaming. If your internet is slow, DNS is most likely not the cause.
Does public DNS hide my activity from my ISP?
Not entirely. With ordinary DNS, the ISP can still read the queries because they are unencrypted. With DNS over HTTPS the query contents are hidden, but the ISP still sees the destination IP addresses you connect to. To hide where a connection is going, what you need is a VPN.
Is it safe to use free third-party DNS?
It depends on the provider. You are moving trust from your ISP to another company, which now sees every domain you open. Choose a provider that publishes its data retention policy clearly and has it audited externally.
Why do some sites still not open after changing DNS?
Because the blocking is not done at the DNS layer. If filtering works by inspecting the domain name inside the connection or by blocking destination IP addresses, changing DNS makes no difference.
Why did switching to 8.8.8.8 make no difference at all?
In Indonesia, home and mobile ISPs are required to redirect plain DNS traffic on port 53, so your queries may still be answered by the ISP's server even though the setting shows 8.8.8.8. Only encrypted DNS (DoH or DoT) escapes this diversion, and even that can fail if the ISP blocks the service's domain.