![]() I suppose what you are saying is why use OpenDNS at all? I believe what you are saying is throw away OpenDNS as the DNS IP set by DHCP. Then let OpenDNS content filter do it thing. While at the same time, bypass NXF by the majority of other users. So, my idea is to use NXF for the limited user group to block certain domains during working hours. (Btw, we are using the free version, OpenDNS). If it were, it would be applied to all users downstream from DNS IP set by DHCP. Ie, we want to set policy for employees not to view Youtube, FB, etc. As I have explained, I want to enforce a stronger policy for a select user group within our office. Good question on why to use two filtering DNS options. What do you recommend? Or what advice do you have? Though, if that is blocked by the system-block.txt then I guess we might have conflicts. I would prefer to change that to OpenDNS 208.67.222.222. I also saw the default dns was set to Google public DNS, 8.8.8.8 and 8.8.4.4. If I wanted to go around that block, could I delete that line in the system-block.txt? It appears NXF is blocking this services, is that correct? So, with that enabled, I am disabing my outboard dns traffic cause OpenDNS is blocked by NXF. In the conf folder I do see system-block.txt with a list of DNS services. We use this content dns filtering for our office. Maybe there was a delay in service changes or cache, I don't know.Īnyway, I did noticed in the Logging "" was Blocked by system. I changed it back to INFO and restart the NXF service and it seems to work. Anyway, I had to turn on DEBUG and then restart NXF and it seemed to work. We due have WSUS:8530 but I did have to remove the Default Site due to port 80 conflict. I was having trouble getting NXFilter to start due to IIS and Default Site.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |