What a DNS server is, how to change DNS and what a VPN has to do with it

Before opening a website, a device asks a DNS server for the site’s address. If the server does not answer, the page will not open even though the internet is up. Below is what DNS is per the standard, who sees these questions, what DNS encryption gives and does not give, how to change the DNS server per Google’s help and what a connected VPN does to DNS.

In short. DNS is a naming system: it turns a site’s name into the address a request goes to. Per RFC 1034 it has three parts: the name space with its records, name servers, and “resolvers”, the programs that ask the servers. Ordinary DNS queries travel as plain text, and whoever carries them can see them; DNS over HTTPS (RFC 8484) shields them from eavesdropping and interference on the path but does not verify the data itself. You can change DNS in the network settings: write down the old values first, and set at least two addresses. Whose servers to pick, we do not advise.

We make Mayak, a private network with an Android app. We do not name or rate other people’s DNS servers; this article is about how DNS works and what we ourselves measured with a VPN on.

What DNS is in plain words

Websites are called by names, while the network works with addresses. DNS ties one to the other. Chrome’s help describes it with the browser as an example: when you visit a site, Chrome looks up the site’s server IP address. In Microsoft’s documentation ping is called the primary command for troubleshooting connectivity, reachability and name resolution, and nslookup a tool for diagnosing DNS (how to find a site’s address with a command we covered in the article about IP addresses).

Per RFC 1034, DNS has three components: the name space and the data tied to it (records); name servers, the programs that hold information about the name tree; and resolvers, the programs that extract information from name servers in response to client requests. User programs reach name servers through resolvers. In everyday speech a “DNS server” is the address your device sends its questions to.

Who gives you that address? Usually the same router that sets the rest of the network: per Microsoft’s help, with automatic setup (DHCP) the settings come from the router or another access point. Or you can enter your own: see below.

Who sees the queries and what encryption gives

Microsoft’s documentation on DNS over HTTPS (DoH) begins with this: with DoH on, queries between the client and the server pass over a secure HTTPS connection rather than in plain text and are protected from interception by untrusted third parties. So without encryption a query is visible along the path it takes. RFC 8484 itself agrees: among its goals is keeping on-path devices from interfering with DNS operations, and its privacy section says the encryption mitigates passive surveillance and attempts to divert DNS traffic to rogue servers.

RFC 8484 also has caveats worth knowing. The HTTPS connection “does not provide the response integrity of DNS data” that a separate mechanism, DNSSEC, provides; without it a server can still return invalid data. And encryption does not hide that an exchange took place: session-level encryption, as the document says, has well-known weaknesses with respect to traffic analysis. So DNS over HTTPS protects the path between you and the server; it is not anonymity.

Where it is switched on and what happens if the server does not answer is in the table.

WhereWhat you can chooseIf the server does not answerSource
Windows “Settings” → “Network & internet” → the network → DNS settings → “Edit” → “Manual”; the encryption choice appears if the server’s address is on Windows’ list of known DNS-over-HTTPS servers. Three options: encrypted only; encrypted preferred, unencrypted allowed; unencrypted only Encrypted only: names will not resolve. Encrypted preferred: the client falls back to plain queries, and Windows will not notify you Microsoft Learn’s documentation of the DNS-over-HTTPS client (for Windows Server 2022)
Chrome on Android “Privacy and security” → “Use secure DNS”; it is on in automatic mode by default Automatic mode: Chrome falls back to unencrypted. A custom provider: no fallback, so lookup errors are likelier Chrome’s help
Android’s system “Private DNS” Three modes: “Off”, “Automatic”, “Private DNS provider hostname” Only the third mode does not fall back to plain queries; our article explains it Our article on Private DNS (per Google’s Pixel help and the RFCs)

A caveat about Windows: the documentation was written for Windows Server 2022. In Windows 11 the path is similar, but we did not check it on a live machine. About Android: how the three Private DNS modes relate to the strict profile of RFC 8310 and why only the third produces the “unavailable” error is explained in detail in the article “Private DNS on Android is unavailable”.

How to change the DNS server: per Google’s help

Of the primary sources, the only step-by-step instructions we read are Google Public DNS’s (the “Get Started” page). We take them as an example of the order of actions, not as advice to pick those addresses: whose servers suit you, we do not rate.

The order per the help. Before changing anything, write down the old values so you can revert. Set at least two addresses: “for the most reliable DNS service” you need at least two, and the same address must not be entered as both primary and secondary.

Windows 10 (per Google’s help). Control Panel → Network and Internet → Network and Sharing Center → Change adapter settings; the connection’s Properties, IPv4 or IPv6 → Properties → Advanced → the DNS tab; note down and remove the old entries and choose “Use the following DNS server addresses”. In Microsoft’s documentation for Windows Server 2022 the path is different: “Settings” → “Network & internet” → the network → “DNS settings” → “Edit” → “Manual”.

Android 9 and later (per Google’s help). “Settings” → “Network & Internet” → “Advanced” → “Private DNS” → “Private DNS provider hostname”, enter the name and save. The modes and pitfalls are in our article on Private DNS.

Testing and reverting. Google’s help suggests loading a site by name, closing and reopening the browser, then typing a numeric address into the address bar. If the page opens by the numeric address but not by the name, the problem is in the DNS setup. If neither works, roll back and test again; if that does not help, contact your provider or network administrator. To revert, the help says to enable automatic DNS server addresses and/or delete the addresses you entered.

If nothing opens after changing DNS, see the article about browser error codes: it covers DNS_PROBE_FINISHED_NXDOMAIN, ERR_NAME_NOT_RESOLVED and the order of checks.

Want to check DNS with protection on? Connect and open any public DNS-leak check: the list should contain only servers of the country you connected to. We do not ask for payment details for the trial. 3 days free once you sign up with your email.

What happens next.

  1. Create an account in the dashboard: an email and a password, no card needed.
  2. Install the app: from Google Play or as a file from our site. On the first connection Android shows a connection-request window: that is expected.
  3. Press one button, wait for “Protected” and open a DNS-leak check: the procedure is in the article “How to check that your VPN works”.

DNS and a VPN

Google Public DNS’s help warns: on Android 9 the Private DNS setting has no effect while a VPN or a third-party DNS app is active; the help says this is fixed in Android 10. So with a VPN on, the setting from the menu may have no effect: where DNS questions go is decided by the VPN.

What we know about Mayak. The article “How to check that your VPN works” says: our name queries go to public resolvers through the tunnel, not straight to your provider’s servers. We advise checking this yourself: if a public DNS-leak check shows your home provider among the servers, there is a leak, and the provider sees the whole list of sites you visit although the content stays encrypted. Those are words from the same article.

And our measurement (7 November 2026, an Android 36 emulator, app version 1.0.25, five connection modes; in two of them Private DNS was set to “hostname” mode with dns.google): in all five, in the steady state of the tunnel, not one DNS query went outside the tunnel. Each mode is one run of about a minute, on an emulator, not a phone; the details and caveats are in the article on Private DNS.

When DNS breaks

Microsoft’s Wi-Fi troubleshooting help, under “connected to Wi-Fi but no internet connection is detected”, suggests checking the DNS server: verify that one is listed and that you can ping it. Microsoft’s ipconfig reference adds that ipconfig /flushdns flushes the DNS client’s resolver cache and, during DNS troubleshooting, discards negative cache entries (when a name once failed to resolve) and entries added dynamically. The full order of checks on a computer is in the article “Connected, no internet access”.

What we do not promise

That another DNS server will speed up the internet or open a site: we did not measure it and Google’s help does not promise it. That DNS encryption makes you anonymous: RFC 8484 does not say so. That your version of Windows and Android has the same menu items as the help. That with any VPN DNS goes as it does for Mayak on our emulator.

What we checked

  • RFC 1034 (section 2.4, the three components of DNS) and RFC 8484 (the abstract, the goals, the security and privacy sections) — read on 21 November 2026.
  • Microsoft Learn’s “Secure DNS Client over HTTPS (DoH) on Windows Server 2022”, the ipconfig, nslookup and ping references and Microsoft’s help “Fix Wi-Fi connection issues in Windows” — 21 November 2026.
  • Chrome’s help on secure DNS (the page “Manage Chrome safety and security”) — 21 November 2026.
  • Google Public DNS’s “Get Started” (steps for Windows 10 and Android 9+, testing, reverting, the VPN caveat) — 21 November 2026.
  • Our articles “Private DNS on Android is unavailable” (the measurement of 7 November 2026) and “How to check that your VPN works”.

What we do not know

  • How all this looks on a live Windows machine and phone: we changed no settings.
  • How DNS over HTTPS is switched on in Windows 11: Microsoft’s documentation is for Windows Server 2022.
  • How to change DNS on a router, Mac, Linux and iPhone: we read no help for them.
  • Which DNS server is faster or more reliable: we did not measure and do not rate servers.
  • How other VPNs treat DNS: we have only Mayak’s measurement on an emulator.

Short answers

What is a DNS server? A server that answers the question “what is the address of this name”. Your device asks it before opening a site.

Who sees my DNS queries? Whoever they pass through, if they are not encrypted: per Microsoft’s documentation, DoH protects them from interception by third parties.

What is DNS over HTTPS? Per RFC 8484, a way of sending DNS queries and getting DNS responses over HTTPS. It protects the path but does not verify the data itself (that takes DNSSEC).

How do I change DNS? Write down the current values, set at least two addresses in the network settings, test by opening a site by name and by numeric address; to revert, enable automatic DNS addresses.

What does a VPN do to DNS? It decides where the queries go. For Mayak, per our article and the emulator measurement, they go through the tunnel; it is worth checking that yourself.

Try Mayak

A secure connection for Android, and articles where other people’s words come with a publication and a date, and our own numbers come with a measurement. 3 days free, no card needed.

The account is created right in the app. 3 free days once you sign up with your email.