Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Resolve non ICANN registered TLDs through fallback resolver #184

Open
larena1 opened this issue Feb 26, 2023 · 0 comments
Open

Resolve non ICANN registered TLDs through fallback resolver #184

larena1 opened this issue Feb 26, 2023 · 0 comments

Comments

@larena1
Copy link

larena1 commented Feb 26, 2023

I have several hosts in my network that can be resolved only through the local resolver. These hosts can be "adguard.lan", "vpn.lan" or anything else. As "lan" is not an ICANN registered TLD, these hosts should be resolved through the local resolver. That works because "lan" is in the list of fallback domains by default.

What does not work with AdGuard enabled on Android is just opening "vpn" in the browser instead of "vpn.lan". With just "vpn", AdGuard on Android will try to resolve that domain through the upstream resolver, that obviously can't resolve that and also is not meant to. With AdGuard or just AdGuard DNS disabled, that works just fine.

Hosts like this should either be appended the configured DNS search domain or be resolved through the local / fallback resolver AND NEVER BE FORWARDED TO AN UPSTREAM RESOLVER ALSO FOR CONFIDENTIALITY REASONS.

@larena1 larena1 changed the title Resolve non ICANN registered TLD domains through fallback resolver Resolve non ICANN registered TLDs through fallback resolver Feb 26, 2023
@adguard-bot adguard-bot assigned sfionov and unassigned zzebrum Mar 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants