We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Hierdie gesprek is in die argief. Vra asseblief 'n nuwe vraag as jy hulp nodig het.

HTTP(S) proxy leaks DNS requests

  • 2 antwoorde
  • 1 het hierdie probleem
  • 2 views
  • Laaste antwoord deur klenamenis

klenamenis
klenamenis
more options

Hey,

I'm using a local DNS caching server called pdnsd to speed up my browsing and block unwanted sites like google, twitter, co. However, if I set up a HTTP and HTTPS proxy in Firefox blocked sites get accessible again, meaning Firefox does resolve DNS requests through those proxies.

"Remote DNS" is unchecked, it's the same behavior in normal mode with all my add-ons enabled, FoxyProxy en- or disabled and in safe mode, meaning this problem belongs to Firefox.

Any help would be appreciated as I dependent on my proxy sometimes, but DNS leaking makes this impossible for now.

Hey, I'm using a local DNS caching server called pdnsd to speed up my browsing and block unwanted sites like google, twitter, co. However, if I set up a HTTP and HTTPS proxy in Firefox blocked sites get accessible again, meaning Firefox does resolve DNS requests through those proxies. "Remote DNS" is unchecked, it's the same behavior in normal mode with all my add-ons enabled, FoxyProxy en- or disabled and in safe mode, meaning this problem belongs to Firefox. Any help would be appreciated as I dependent on my proxy sometimes, but DNS leaking makes this impossible for now.

All Replies (2)

philipp
philipp
  • Moderator
more options

hello, you might need to keep "remote dns" enabled in your situation: http://kb.mozillazine.org/Network.proxy.socks_remote_dns

klenamenis
klenamenis Vraag-eienaar
more options

Hey,

no, this option has no effect.

FYI, I'm using TOR by default via SOCKS5 localhost:9050. To solve my problem, did not configure Firefox to use the HTTP(S) proxy instead of TOR but added the following line to my TOR configuration in order to let TOR use the desired HTTP(S) proxy:

HTTPSProxy url-of-my.proxy:port