What I did was configure the local domain in the OpenVPN settings and specify that domain in the 'Local Domain' configuration of NXPROXY. Our OpenVPN policy dictates that we use a different DNS server due to DNS splits and other reasons irrelevant to the topic. Under Policy -> NXPROXY, what should be put in 'Local Domain'? Is this for the 'Connection-specific DNS suffix' of a network connection in Windows? Or is this also the active directory domain? 5. The following are the challenges that I am currently having: 4. I am evaluating NxProxy client on a Windows 10 PC and installed the nxproxy-1.1.4-win.exe. Is this correct? I was under the impression that each user will be needing his/her own token to differentiate each user in the logs. I understand that in order for NxProxy to work, authentication needs to be enabled, correct? I am confused with the example of GPO deployment with AD wherein there is only a single TOKEN specified:

The document states that NxProxy needs the NxFilter server to open TCP/80 and TCP/443 ports:ĭoes this mean NxProxy only uses ports 80 and 443 to submit DNS queries from the remote client to the NxFilter server? Does the remote client need to connect to the NxFilter via DNS UDP/53 as well? The feature of NXFilter that we are very interested in is its ability to do remote filtering via NxProxy. I am currently testing and evaluating NxFilter for a company with around 600 users, so please bear with my questions which I found vague or totally missed in the documentation.

Nxfilter pfsense