Your Browser’s SOCKS Setting Does Not Configure nslookup
Interpret a system DNS lookup separately from a proxied browser request when evaluating remote hostname resolution.
The browser uses a SOCKS proxy, then nslookup contacts the machine's usual resolver. That is not enough to conclude that the browser ignored its remote-DNS option.
The utility made another query through its own DNS interface. It did not ask the browser which route to use. Conversely, a browser sending destination hostnames to SOCKS does not reconfigure every resolver client on the device.
An SSH dynamic forward adds another useful distinction. It accepts SOCKS-aware application connections. It is not an automatic system-wide UDP DNS relay. A destination hostname carried in a SOCKS request can still be resolved remotely without forwarding the system's ordinary DNS queries through that listener.
Evaluate the operation you care about. Identify the browser's effective proxy type and destination-resolution policy, then inspect evidence associated with that browser request. A separate utility outside that path is a comparison, not a measurement of the browser's internal lookup.
If the requirement is system-wide name-resolution routing, state it separately. It needs an appropriate supported design covering the resolver traffic in scope. A single application proxy setting establishes a narrower arrangement.