DNS proxy
A service that intervenes at the name-lookup stage rather than carrying your traffic, covering everything from router DNS forwarding to smart DNS unblocking.
The phrase names several quite different arrangements, which is exactly why it needs an entry. What they share is the layer they work at: instead of relaying your traffic the way a proxy server does, a DNS proxy stands in the path of your name lookups, the questions that turn hostnames into addresses, and does something useful with the questions themselves.
The infrastructure sense is the humble one. A router or resolver that accepts your DNS queries and forwards them upstream is acting as a DNS proxy, which is what the setting of that name on home routers means, and filtering resolvers extend the same position into policy: answer most lookups honestly, and answer the ones on a blocklist with nothing, which is how ad-blocking resolvers make advertising domains simply fail to resolve for every device on the network at once.
The commercial sense, usually sold as smart DNS, uses the same position for geography. The service answers lookups normally except for a curated set of streaming and media hostnames, where it returns the address of its own relay instead; traffic to those specific services then flows through infrastructure in the licensed region while everything else you do goes direct. Its selling points are real: nothing to install, works on televisions and consoles that cannot run proxy or VPN software, and no speed penalty on the traffic that never touches the relay.
Its limits follow from the same design, and they are the part the marketing omits. Nothing is encrypted. Your visible address is unchanged for everything outside the curated list, so it hides nothing about you. Only destinations the service chose to cover are affected, and the coverage breaks whenever the target service updates its detection, since a shared relay's addresses are exactly as catalogueable as any VPN range. And because the whole trick depends on your device asking the right resolver, anything that pins its own DNS, which modern devices increasingly do, walks straight past it.
Placed against the neighbours: a proxy server relays traffic and changes your visible address per application. A VPN does it for the whole device with encryption. A DNS proxy changes the answers to lookups, which redirects a chosen slice of traffic and nothing more. For watching a regional catalogue on a television, it is a reasonable tool. For scraping, geo-testing, or anything needing a genuine local address across arbitrary sites, it is the wrong layer entirely.
Frequently asked questions
What is the difference between a DNS proxy and a normal proxy?
The layer it works at. A proxy server carries your actual traffic and substitutes its address for yours at the destination. A DNS proxy intervenes only in name lookups, redirecting selected hostnames by answering them differently, while your traffic to everything else flows direct from your real address. One relays connections; the other edits the address book.
Is smart DNS better than a VPN for streaming?
It is more convenient and less protective, which for a television is often the right trade. It needs no client software, runs on devices that cannot install one, and only slows the specific services it relays. It also encrypts nothing and hides nothing. Whether it works at all depends on an ongoing cat-and-mouse with each target service, so treat coverage claims as perishable.
Does a DNS proxy hide my IP address?
No, and this is the misunderstanding the name invites. For every destination outside the service's curated list, sites see your real address exactly as before. Even for covered services, what changed is which infrastructure your traffic reached, not any general property of your connection. Anything privacy-shaped needs a layer that actually carries your traffic.
Why does my smart DNS stop working sometimes?
Usually one of two causes. The target service identified and blocked the relay's addresses, which is the standing arms race any shared unblocking infrastructure lives in. Or your device stopped asking the service's resolver, because an app or operating system pinned its own encrypted DNS, which bypasses the redirection entirely. The first needs the provider to rotate; the second is a setting on your side.
Back to the full glossary.