domain in "network.trr.excluded-domains" not respected (outbound connections still made)
Categories
(Core :: Networking: DNS, defect, P2)
Tracking
()
People
(Reporter: candita, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [necko-triaged])
Steps to reproduce:
set "network.trr.mode" to "3"
enter domains in "network.trr.excluded-domains"
Actual results:
Outbound connection to bootstrapped doh service IP address is made
Expected results:
No connection should have been made. No connections were made in Firefox 105.x (expected). Tested working incorrectly in Firefox 108.x and 109.0.
Comment 1•2 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.
An amendment to steps to reproduce:
"network.trr.exclude-etc-hosts" is set to true and address is one word or incomplete. Also said address is in hosts file set to 0.0.0.0
Comment 3•2 years ago
|
||
Could you capture some logs of this happening?
https://firefox-source-docs.mozilla.org/networking/http/logging.html
Outbound connection to bootstrapped doh service IP address is made
Just to clarify:
You put a hostname in the excluded domains, but it still ended up connecting the the IP returned by DoH, instead of the one coming from /etc/hosts?
(In reply to Valentin Gosu [:valentin] (he/him) from comment #3)
Could you capture some logs of this happening?
https://firefox-source-docs.mozilla.org/networking/http/logging.htmlOutbound connection to bootstrapped doh service IP address is made
Just to clarify:
You put a hostname in the excluded domains, but it still ended up connecting the the IP returned by DoH, instead of the one coming from /etc/hosts?
*Hostname put in excluded domains
*Hostname was included in Hosts file directing to 0.0.0.0
*Hostname was one word
In the past no outbound connection to the doh IP address would be made. Now it does.
I would rather not post logs.
Comment 5•2 years ago
|
||
Are you sure there isn't another host that has the same IP address?
Note that resolving test.
is unfortunately different from resolving test
, so you consider adding both.
Without logs I can't really confirm if there is a problem or not.
(In reply to Valentin Gosu [:valentin] (he/him) from comment #5)
Are you sure there isn't another host that has the same IP address?
Note that resolvingtest.
is unfortunately different from resolvingtest
, so you consider adding both.Without logs I can't really confirm if there is a problem or not.
in the excluded domains I have entered as follows using "clown" as an example: clown, www.clown
And in the hosts file have included entries for both. As I said, there were no outbound connections with Firefox 105.x
Comment 7•2 years ago
|
||
(In reply to candita from comment #6)
And in the hosts file have included entries for both. As I said, there were no outbound connections with Firefox 105.x
You can find out the regressing bug yourself using mozregression:
https://mozilla.github.io/mozregression/quickstart.html
Thanks!
Comment 8•11 months ago
|
||
A needinfo is requested from the reporter, however, the reporter is inactive on Bugzilla. Given that the bug is still UNCONFIRMED
, closing the bug as incomplete.
For more information, please visit BugBot documentation.
Description
•