Error after intalling nxfilter on Mint

[Hector Blansec]

Cannot access admin console with address http://<my_ip>/admin

Error reported in logfile:

UdpServer started.
ERROR [06-13 12:02:22] - UdpServer: java.net.BindException: Address already in use
 INFO [06-13 12:02:22] - Couldn't bind UDP 53. You might want to check your permission!

Any idea of what might be wrong?
Thanks !

[Jinhee]

You have another DNS server on your system.

[Noah Gregory]

I am having the same issue. Can you elaborate on a fix?

[Jinhee]

You need to find which program is using UDP 53 on your system. If it's a Ubuntu read these,

  http://askubuntu.com/questions/227161/how-can-we-find-which-process-is-using-a-particular-port
  http://www.commandlinefu.com/commands/view/241/show-which-programs-are-listening-on-tcp-and-udp-ports

[gduro...@gmail.com]

I thought it was supposed to be a DNS server? I have Windows Server 2012 r2 and the NXFILTER service continues to stop running after starting it. In the log I get that same issue, I created a new IP Address and still the same. I thought the server had to be a designated DNS server prior to installation. How then does it know where to get updates?

[Jinhee]

You already have a DNS server running on your Windows server. Right? Install NxFilter on another system or on a VM on your server.

[gduro...@gmail.com]

Ok, I will remove the role of DNS and try again, so it acts as a DNS server or a secondary zone in order to operate properly. My question would be if there are static IP servers do I still use the primary DNS for the servers or also point it to the NXFILTER? And if I do, how does the DNS suffix get added to the primary server for update? 

[Jinhee]

I think you are talking about dynamic host update or DDNS in Active Directory. NxFilter is supposed to
do this automatically. When you import your users from your AD DC. Now NxFilter thinks you run your
MS DNS server on your DC. It means it knows the IP address of your MS DNS server and your AD domain.
Based on these information it will try to bypass the DDNS queries for your AD domain to your MS DNS.

However some users say that they still have a problem. In that case your can try to use 'local_dns'
and 'local_domain' on /nxfilter/conf/cfg.properties file. It bypasses all the queries to your AD domain
to a designated DNS server.

  http://www.nxfilter.org/tutorial.html#bypass_local

* You might need to allow nonsecure dynamic update for NxFilter on your MS DNS zone properties.

With v3.1.3 we will have an imporoved auto-bypass for AD domain to MS DNS server.