non fqdn dns http exclude
Categories
(Core :: Networking: DNS, enhancement, P3)
Tracking
()
People
(Reporter: herbert, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [necko-triaged])
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Firefox/91.0
Steps to reproduce:
Enable DNS over HTTPS
Set network.trr.excluded-domains = mydomainexample.com
Browse to https://inside-non-fqdn-host/
Actual results:
DNS over HTTPS resolves from external DNS and obviously fails.
Expected results:
When using non-fqdn I would expect that the internal DNS is used to resolve inside-non-fqdn-host.mydomainexample.com.
I would suggest to add an option to resolve non-fqdn as an excluded domains for DNS over HTTPS
|
||
Comment 1•4 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Networking: DNS' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
|
||
Comment 2•4 years ago
|
||
I am not sure I fully understand.
if you want that inside-non-fqdn-host.mydomainexample.com is resolved by the native resolver you can add "*.mydomainexample.com" to the exclusion list. You need to type https://inside-non-fqdn-host.mydomainexample.com/ into the address bar.
If you want to connect to https://inside-non-fqdn-host/ using the native resolver you need to add "inside-non-fqdn-host" to the exclusion list. Firefox will try to resolve "inside-non-fqdn-host" and not "inside-non-fqdn-host.mydomainexample.com" in this case.
non-fqdn-host should be treated as internal network (intranet) and as such resolved by native resolver
we cannot add all the non-fqdn-hosts to exclusion list and expected to daily maintain that
Cheers
simmilarily as is preference network.automatic-ntlm-auth.allow-non-fqdn=true for intranet auth
|
|
||
Comment 5•4 years ago
|
||
Ok. Thank you for the explanation.
Description
•