FR: dns.resolve() should provide option to interface any other DNS resolver available in browser (eg. other proxy addons)
Categories
(WebExtensions :: General, defect)
Tracking
(Not tracked)
People
(Reporter: gokulakrishnaks, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:65.0) Gecko/20100101 Firefox/65.0
Steps to reproduce:
dns.resolve() at https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/dns/resolve uses systems' DNS resolver. There's no option in the API as per MDN documentation that lets API consumer to pass DNS server info to have the extension with DNS permission use it instead of Local system's DNS resolver.
This will also help when user has another proxy-ing addon installed. If there's another addon that uses dns.resolve(), perhaps the localhost:port exposed in the OTHER proxy addon can be hit to have DNS resolutions happen over the proxy.
This will help as the extension that actually does dns.resolve() can remain entirely offline and need not make a network call from within itself to resolve DNS.
Actual results:
DNS.resolve() happens on local system's DNS resolver.
Expected results:
This is a feature request as detailed above in Steps to Reproduce section.
|
Reporter | |
Updated•5 years ago
|
|
||
Comment 1•5 years ago
|
||
At most we'll expose some functionality for dns-over-https per bug 1455425, which may include some flags in dns.resolve, but we wont expose a way for an extension to choose a dns server in this fashion.
dns over proxy is only supported for socks connections, if you're specifically using that and dns.resolve doesn't go through the socks proxy, file a bug specific to that.
Description
•