So, if you have another DNS server or webserver running on the same system, NxFilter will not start. This means NxFilter itself is a DNS server and a webserver. NxFilter uses UDP/53, TCP/80, TCP/443 at default. The other thing you might want to check would be port collision problem.
Thank you again if there's anything else please tell. You can find some information about the cause of your problem. My problem is that we use static IPs inside the ORG(I don't know Why) and to make each PC connect to the server statically is a pain in the a**. If you have a firewall you can force your users to use NxFilter as their DNS server by blocking outgoing traffic on UDP/53, TCP/53 port. If your router doesn't support DHCP, you can use a freeware DHCP server. Ok ok, I understand what you said, no I can't do that, yes one DNS server is for the ORG's private usage the other DNS server I'm trying to use is a website content filtering, and there's a reporting service with it but the client IP was always the router's IP, I was wondering if there's a bypass for such problem. Most routers support DHCP feature these days. The only way to make the DNS server see the addresses of its clients is to make them its clients: move all static entries to DNS server and let it be the only one DNS resolver in your network.Īlternatively you could reverse the situation completely: make it Clients -> DNS Server -> Router -> Public DNSīut I guess you use separate DNS Server for a reason, and using Router to connect to upstream DNS is not an option? That was the solution to make NAT work, not for your initial problem.
I changed the IP of the DNS server to 10.10.10.1 and then used that address in the NAT it forwarded the request to that DNS server, but the IP entering the DNS server is still the IP of the router rather than the client's actual ip
0 kommentar(er)
