nslookup gets SERVFAIL but not in Windows

There's a nameserver 10.92.131.26 on my work VPN, and it appears to get configured on my machine when I connect to our anyconnect VPN server. When I run nslookup server on my Linux workstation, I get a SERVFAIL for it:

;; Got SERVFAIL reply from 10.92.131.26, trying next server
Server:		10.50.177.208
Address:	10.50.177.208#53

** server can't find server: SERVFAIL

But when I open a Windows VM within my workstation run and run nslookup, it succeeds for the very same nameserver.

Default Server:  a.company.domain
Address: 10.92.131.26

Why is this? --- **TMI: Why do I care?** At work, our MFA system applies extra restrictions when I attempt to access certain of the company websites using my Linux workstation, but I don't experience these restrictions when I boot to Windows, nor when I attempt from a Windows VM from within my Linux system. (And I can't satisfy these extra restrictions because I.T. appears not to have planned on anyone actually encountering them legitimately.) I.T. tells me: > Normally this is due to an issue with the VPN routing to [our] servers... Try it in Google Chrome if it still doesn't work as Firefox sometimes uses its own DNS to resolve addresses so it can cause this error where Chrome will just work. ...And indeed, their assertion seems well founded: in the Windows VM, my connection attempts through Chrome succeed, and my attempts through FF do not. Still, my attempts on my Linux host do not work at all. I wonder if my attempts from Linux will succeed if I can get my Linux machine to use 10.92.131.26 for its nameserver. --- **Outputs** **Update:** as requested, here are the outputs to netstat -rn on each machine. They're pretty long, so I'm just linking pastebins: [on Linux](https://pastebin.com/H2GZQhxU) , [on Windows](https://pastebin.com/rdhrjWfV) Here's a tracert 10.92.131.26 from the Windows VM:

Tracing route to 10.92.131.26 over a maximum of 30 hops

  1    29 ms    27 ms    25 ms  192.168.100.1 
  2    35 ms    31 ms    33 ms  173.36.212.117 
  3    35 ms    34 ms    29 ms  50.216.158.108 
  4    41 ms    35 ms    37 ms  10.92.131.26 

Trace complete.