Home Reviews About
Twenty of Time

Encrypted DNS to Block Ads and Trackers in Australia

Encrypted DNS gives browsers and devices a more private way to look up website addresses, while a filtering resolver can reject many advertising and tracking domains before a connection is made. It is a practical layer for Australian households, yet it is easy to mistake it for complete anonymity. The useful question is not whether encrypted DNS makes someone invisible, but which unwanted network requests it can remove and which parties still receive the data.

Two main protocols carry the change. DNS over HTTPS sends lookups inside an encrypted HTTPS connection, while DNS over TLS wraps them in a separate encrypted channel. Both stop an ordinary internet service provider or café Wi-Fi operator from reading the queries in transit. The resolver on the other end still needs to see them in order to answer, and a resolver that filters unwanted domains adds another party to the trust chain.

This guide explains how to choose a filtering resolver, configure encrypted DNS in major browsers and on Australian mobile networks, and test the result without breaking ordinary browsing. It also sets firm boundaries around the technique. Encrypted DNS can reduce domain-based advertising and telemetry, but it cannot erase cookies, defeat browser fingerprinting, or conceal every action once a page has loaded.

What encrypted DNS actually does

Plain DNS is the internet’s address book. When a page requests an image, script or advertising service, the device usually asks a resolver for the matching internet protocol address. Without encryption, that request can be read by the network operator, and the destination reveals which service is being contacted. HTTPS protects the page traffic itself, but it does not automatically protect the earlier DNS lookup.

Encrypted DNS changes that first exchange. DNS over HTTPS uses HTTPS as its transport; DNS over TLS uses a dedicated TLS session. A client validates the resolver’s certificate or public key, so an impostor cannot quietly collect lookups and return false addresses. Filtering resolvers apply maintained domain lists before answering. An ad hostname may be blocked or pointed to a harmless sink address, preventing the request from reaching the advertising server.

The distinction between blocking a domain and tracking a person matters. DNS filtering is effective against banner ads, tracking pixels hosted on separate domains, and telemetry sent to known analytics providers. It is less effective against ads delivered from the same domain as the site, identifiers stored in cookies, fingerprinting scripts, and campaigns whose addresses are already cached or bundled into an app. A blocked lookup may also reveal that a tracker was present, even though no connection to it follows.

Why the Australian context matters

Australian connections make the choice of resolver particularly relevant. Many fixed-line and fixed-wireless services arrive through a small set of large providers, including Telstra, Optus, TPG and Aussie Broadband, with the supplied router often pointing DNS at the provider’s own service. In Sydney, Melbourne, Brisbane and Perth, latency to a filtered overseas resolver can vary with the route and time of day, so performance is worth testing rather than assuming every endpoint is local.

The privacy gain is mostly about limiting routine observation and unwanted contact, not creating a new legal shield. Australia’s Privacy Act 1988 and the Australian Privacy Principles still govern many organisations, and OAIC guidance continues to treat online tracking as a significant privacy issue. If an Australian service uses a resolver established elsewhere, the legal location of that resolver can matter. The Schrems II analysis offers a useful account of why transfer safeguards and the recipient’s actual practices are examined, although that European ruling does not set Australian privacy law.

This is also where local safeguards deserve attention. ACMA can require internet service providers to block access to certain material under the Online Safety Act, and replacing the ISP’s DNS service may bypass some network-level blocking. Users can select a resolver with suitable safety filters, but should understand the trade-off rather than disabling protective controls accidentally. At the Australian border, Customs and Border Force officers may ask travellers to unlock devices; encrypted DNS does not hide files, browser history or unlocked accounts.

Choosing a resolver that fits

There are three broad ways to arrange filtering. A public filtering resolver is the quickest option and requires little configuration. A privacy-focused paid service may provide better filters, detailed controls and stronger guarantees about retention. Running a local resolver, often with software such as Pi-hole or Unbound, gives the household more control but shifts the work of updates, uptime and troubleshooting to whoever maintains it.

Compare services on more than their blocklist size. Check whether queries are logged, where processing occurs, whether the operator sells data, whether independent audits exist, and whether IPv6 and encrypted-DNS endpoints are supported. Families may also need category controls, per-device exceptions and a way to allow a blocked service. V. Heissu’s encrypted DNS reference is a useful technical reference for checking protocol support and understanding deployment details beyond a provider’s marketing page.

The resolver must be able to handle both DNS over HTTPS and DNS over TLS if it is to serve several kinds of device. Confirm the exact hostname and endpoint before entering them, because a web address and a private-DNS hostname are not interchangeable. Keep a note of the provider’s privacy policy and incident history, and avoid “free” services that publish detailed individual query logs. A larger blocklist is not automatically the safer or more useful setting.

A practical setup for home and mobile

Start with a browser because it is the least disruptive place to test the idea. In Firefox, open Settings, then Privacy & Security, Security and the settings button beside DNS over HTTPS. Enable the option and choose a listed provider or enter a custom endpoint where offered. Chrome users can find Use secure DNS under Privacy and security, Security. As a filtering example, AdGuard publishes the DNS-over-HTTPS endpoint https://dns.adguard-dns.com/dns-query; entering that address does not itself endorse every filter category in the service.

On Android, the Private DNS setting accepts a DNS-over-TLS hostname such as dns.adguard-dns.com. This covers apps that use the system resolver, although an app with an embedded resolver may still bypass it. Recent iPhone and iPad versions and Mac desktops can accept a custom DNS profile with an encrypted-DNS URL, but the profile process is less convenient than Firefox’s controls. Start with one browser, confirm that ordinary sites resolve, and only then apply the same endpoint to the wider device.

A router-level setup is the most comprehensive option when it supports DNS over HTTPS or DNS over TLS directly. Some Australian ISP-supplied routers expose neither setting, while compatible models or software such as OpenWrt can forward queries to an encrypted upstream resolver. Connected televisions, cameras and doorbells add another layer; the IoT data rights review explains why access to data generated by a device is separate from the network filter that blocks an unwanted lookup. Blocking one connection never grants ownership of everything the device records.

Limits, testing and safe defaults

Test the arrangement rather than judging it by the disappearance of one banner. Open several Australian news, retail and government sites, then use the browser’s network tools to see whether requests to known ad domains fail at DNS. A privacy dashboard can show which third-party hosts remain. If a bank, state service or work portal fails, check the filter’s category or domain list first; broad lists can catch shared hosting addresses and cause false positives. Captive portals, split-horizon corporate domains and some VPNs also need special handling.

Encrypted DNS is not a virtual private network, and it does not replace HTTPS, tracker protection in the browser, or sensible account security. It hides the lookup from the local network, while the chosen resolver still receives enough information to identify the requested domain. It also cannot block first-party analytics or a tracker whose address is embedded directly in software. Before changing a shared family or work setup, a structured privacy and security review helps separate the benefits of private lookups from assumptions about complete anonymity.

For households, a combination of controls usually works best: encrypted and filtered DNS at the router or system level, a browser that blocks third-party cookies, an ad blocker for pages that still serve same-site ads, and separate browser profiles for shopping, work and personal activity. None of these layers is perfect, and each introduces trade-offs. The important point is to know which company or network can observe each stage, rather than treating one setting as a universal shield.


Encrypted DNS works best when it is treated as a focused privacy control rather than a magic invisibility cloak. It can reduce the number of companies contacted by routine page loads, remove many domain-based ads and trackers, and limit what an untrusted local network can read in transit. Its effectiveness depends on the filter, the protocol, the resolver’s conduct and the websites being visited.

The lasting lesson is that private browsing is a chain of separate decisions. Encrypted DNS protects one valuable part of that chain: the questions a device asks to find its way around the web. The reader should remember that the resolver becomes a trusted intermediary, filtering can occasionally break useful services, and successful protection comes from combining narrow controls with a clear understanding of their limits.