What DNS-over-HTTPS is and why YamYam sends DNS through the tunnel

DNS is the internet’s directory

People remember names such as example.com while networks connect to IP addresses. A resolver answers the name-to-address question and the device may cache it. DNS is not the page content; it is one early step. A browser can make separate lookups for login, images and notifications, so one page may involve several names.

What DoH changes

Traditional DNS can be readable on the local network. DNS-over-HTTPS sends the same question inside HTTPS, making it harder for a local observer to read the text. It does not encrypt all internet content or make you anonymous to the resolver or destination. DoH changes the channel for the question; HTTPS for the site and account security remain separate concerns.

Why route DNS in the tunnel?

If a VPN tunnels the main traffic but leaves DNS outside, the local network or default resolver may still see names and return a different answer. YamYam sends DNS through its encrypted tunnel to a relay, which forwards the question to a public resolver without your IP address. The relay still has to process a question to answer it, so this is a routing design, not an absolute no-retention promise; see the privacy policy for details.

DNS is not the whole privacy story

A DNS answer does not encrypt HTTP content, cookies or an account you use. A VPN also cannot hide you from a destination where you sign in. Keep HTTPS, unique passwords and two-step verification in place. Treat DNS as one layer that coordinates a connection, not a guarantee of anonymity.

If a site fails

Test a known domain, reconnect once and check split-tunneling rules. Start with Smart and change one setting at a time. A single-app failure is more likely to be a local rule, browser cache or destination issue than a tunnel-wide DNS problem. Send support your app and Android versions, not tokens or passwords.