DNS AdBlock, GeoDNS and Custom Exit address different parts of a Lisar connection. They can be used together where the plan and configuration support them. Their effects still depend on which DNS resolver and network route the device actually uses.
Three features, three questions
- DNS AdBlock: can the DNS path filter selected advertising or tracking domains?
- GeoDNS / Auto Entry: what supported DNS and entry-selection behavior is available for this profile?
- Custom Exit: which eligible exit route is configured for traffic leaving the VPN?
Check the current plan matrix. Basic includes GeoDNS / Auto Entry. Pro adds DNS AdBlock. Enterprise also includes Custom Exit eligibility. Custom arrangements require review. Free does not include these three features.
Start with the actual profile
Open the profile in the Lisar Panel and check its plan, status and available settings. Plan eligibility is not proof that every device is using the expected resolver or route. A browser with its own secure-DNS configuration, a device-specific route or a different saved profile can change the observed result.
DNS AdBlock filters domains
DNS filtering applies when a relevant lookup reaches the filtering resolver. It can prevent requests to selected domains. It cannot select individual ads within an allowed domain or remove content already downloaded. Cached DNS answers or an application using a different resolver may also affect what you observe.
Use the DNS and browser blocker comparison to understand the different scopes. Lisar DNS AdBlock is not a browser extension or a replacement for device security controls.
GeoDNS concerns DNS and entry behavior
GeoDNS can influence supported name-resolution and entry-selection behavior according to the profile's capabilities. It is separate from choosing the exit route. DNS behavior alone does not establish which public address a website sees, change the device's GPS location or change an account's country.
Custom Exit concerns the outgoing route
Where eligible, Custom Exit allows the documented exit-routing options for a profile. Router capability and route availability matter. A tailored business requirement may need review, and several users on the same plan do not automatically inherit one shared exit configuration.
The features can interact
These are different functions, but they are not isolated from one another. Changing a route can change which resolver or network path a request reaches; changing DNS behavior can change the destination selected for a domain. Do not assume that enabling a feature leaves every other observed result unchanged.
When troubleshooting, change one supported setting at a time. Record the same device, client, profile, network and destination before and after the change. Confirm the connection state separately from DNS and routing observations.
Choose by the result you need
For fewer requests to selected ad domains, review DNS AdBlock. For DNS and automatic-entry behavior, review GeoDNS. For a specific eligible outgoing route, review Custom Exit. Read the corresponding feature page and check the active profile before relying on any of them.
No combination guarantees a particular speed, complete ad removal or access to a third-party service. Those outcomes depend on factors beyond these profile features.
Frequently asked questions
Are all three included in every plan?No. Availability differs by plan; use the pricing matrix and the active profile's entitlements.
Can one feature replace another?No. Domain filtering, DNS/entry behavior and exit routing solve different problems.
Can their effects interact?Yes. DNS results and routes can affect which destination and resolver a request uses. Compare changes under controlled conditions.
Does Custom Exit configure every team member automatically?No. Verify the configured route of each participating profile and review tailored requirements with Lisar.
Related guidance: GeoDNS in a VPN: What It Changes and What It Does Not and Custom Exit in a VPN: What It Means and When It Helps.