What the built-in AdGuard Home does
AdGuard Home is network-wide software for blocking ads and tracking. The project describes it as a DNS server that sends tracking domains to a black hole, so devices never reach those servers, and it needs no software on each device. [3] On a GL.iNet router it ships as an application. Turn it on under Applications, AdGuard Home, toggle the switch and click Apply. The page then shows statistics such as DNS queries and blocked domains, and a Settings Page button opens the full AdGuard Home interface for advanced filter rules. [1]
The benefit is coverage. A smart TV, games console or work laptop you cannot install software on still gets filtering because its DNS lookups pass through the router. The project notes that DNS blocking reaches devices like smart TVs and smart speakers, where traditional blockers cannot run. [3]
Which models support it
GL.iNet publishes supported and unsupported lists. The relevant split for travel and home buyers is below. GL.iNet does not publish memory requirements on the AdGuard Home page, so treat the model list as the deciding factor rather than guessing from specifications. [1] The app also needs Router mode: GL.iNet lists AdGuard Home among features unavailable in Access Point, Extender, WDS and Bridge modes. [5]
How it interacts with VPN and DNS settings
The key option is Handle Client Requests. When enabled, DNS queries from your devices go directly to AdGuard Home. GL.iNet warns that this makes domain-based VPN policies and parental control rules ineffective. [1] If you route only some websites through the VPN by domain, you have to choose between that and AdGuard Home handling client requests.
GL.iNet DNS settings add a second layer. By default, DNS queries for traffic that matches the VPN policy use the DNS servers provided by the VPN tunnel, while other queries use the DNS servers from the active WAN connection. Enabling Apply Manual DNS to VPN tunnels makes your custom manual DNS apply to traffic through the tunnel instead. [2] GL.iNet does not document exactly how these settings combine with AdGuard Home. Test it: connect the VPN, browse for a minute, and check that the AdGuard Home query counter on the router page is rising. [1]
Hotel login pages and DNS rebinding protection
Captive portals rely on DNS behaving in a particular way, and filtering can get in the way. GL.iNet says DNS Rebinding Attack Protection may cause private DNS lookups to fail and should be disabled on networks that use a captive portal. [2] Its Repeater page adds that Auto-Enable Login Mode switches DNS to automatic and suspends some services while you sign in. [4]
A practical routine on the road is to sign in to the hotel network first, then confirm AdGuard Home is filtering again. If the sign-in page never appears, pause AdGuard Home, sign in, and turn it back on. Our captive portal guide covers the sign-in side in more detail.
What DNS blocking cannot do
The AdGuard Home project is direct about the ceiling. DNS sinkholing can block a big share of ads but lacks the flexibility of traditional blockers. Any advertising that shares a domain with the content cannot be blocked at the DNS level. It names YouTube and Twitch ads and sponsored posts on Facebook, Twitter and Instagram as examples. [3]
So AdGuard Home on the router complements, rather than replaces, a browser extension on your laptop. Set expectations with anyone sharing the network: fewer trackers and banner ads, not an ad-free streaming service.
When a VPN app blocker is the better choice
If most of your browsing happens on one or two devices that already run a VPN app, the provider blocker may be enough. Proton VPN NetShield, included on paid plans, uses Proton DNS servers to block malware domains and, at its Block ads, trackers, and malware level, ads and trackers too. Proton's own article is inconsistent about which level is the default on each platform, so check the setting in your app. [6] It travels with the device on any network, without depending on the router.
NetShield has its own limits. It does not work with Tor over VPN, and on Android 10 and later the Private DNS setting overrides it unless set to Off or Automatic. Proton's article covers its apps, not routers or manual WireGuard configurations. [6] Use the router for coverage of devices without apps, and the VPN app for devices that leave the house.
| Your situation | Better fit | Why |
|---|---|---|
| Smart TV, console and guests at home | AdGuard Home on a supported router | Covers devices that cannot run blockers [3] |
| You rely on domain-based VPN routing | Leave Handle Client Requests off, or use the VPN app blocker | That option breaks domain-based VPN policies [1] |
| One laptop and phone, always on a VPN app | VPN provider blocker such as NetShield | Follows the device on every network [6] |
| Opal or another unsupported model | VPN app blocker or encrypted DNS with filtering | AdGuard Home is not supported there [1] |
| Router in Access Point or Extender mode | Run blocking on the main router instead | AdGuard Home is unavailable outside Router mode [5] |
Setup and troubleshooting checklist
Run through this once at home before relying on the router while travelling.
- Confirm the model is on GL.iNet supported list and the router is in Router mode [1][5]
- Enable under Applications, AdGuard Home, then Apply [1]
- Decide on Handle Client Requests based on whether you use domain-based VPN rules [1]
- Open the Settings Page and review filter lists before adding more [1]
- With the VPN connected, check that the query counter still rises [1][2]
- If a hotel login page fails, check DNS Rebinding Attack Protection and pause filtering to sign in [2][4]
- If something breaks, turn AdGuard Home off first to see whether it is the cause
Questions before you decide
Does AdGuard Home run on the GL.iNet Opal?
No. GL.iNet lists GL-SFT1200 (Opal) among unsupported models for AdGuard Home. Beryl AX (GL-MT3000) and Flint 2 (GL-MT6000) are on the supported list.
Will AdGuard Home block YouTube ads?
Not reliably. The AdGuard Home project says advertising that shares a domain with the content cannot be blocked by a DNS-level blocker, and names YouTube and Twitch ads and sponsored social posts as examples.
Why did my domain-based VPN rules stop working after I enabled AdGuard Home?
GL.iNet warns that enabling Handle Client Requests, which sends client DNS queries straight to AdGuard Home, renders domain-based VPN policies and parental control rules ineffective. Turn that option off if you depend on those rules.
Sources & verification
Product details and prices can change. Check the linked provider before buying.
- GL.iNet Router Docs 4: AdGuard Home Accessed 30 Oct 2026
- GL.iNet Router Docs 4: DNS (firmware v4.11) Accessed 30 Oct 2026
- AdGuard Home project README (GitHub) Accessed 30 Oct 2026
- GL.iNet Router Docs 4: Repeater Accessed 30 Oct 2026
- GL.iNet Router Docs 4: Network Mode Accessed 30 Oct 2026
- Proton VPN Support: NetShield Accessed 30 Oct 2026
Sources link directly to providers. Product buttons may use separately labeled affiliate links. Read our disclosure.