Return the intended destination-DNS policy with the SOCKS route from your existing Firefox extension listener:

{
  type: "socks",
  host: "proxy.example",
  port: 1080,
  proxyDNS: true
}

In this API, type: "socks" identifies SOCKS5. For public-site requests permitted through a public intermediary, a candidate from the SOCKS5 proxy list can supply this route's host and port. The fragment assumes the extension already has its permitted routing listener; it is not a complete extension. A type name from an old proposal or another browser's API is not interchangeable.

Mozilla's current reference gives proxyDNS a default of false for the supported SOCKS types. Set it explicitly when this route needs proxy-side resolution instead of relying on the browser's manual-proxy dialog to supply the extension's choice.

Apply the intended policy to every applicable fallback object too. Another object returned after the first route fails may have a different DNS choice or select a different path.

The field controls certain queries associated with that route. It does not move every operating-system or application lookup to the proxy.

Artihkkalat mat laktásit