🐳 Run NxFilter in Docker!
Branch: nxfilter-latest
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.
Dockerfile Update to JRE8 Jan 18, 2019
LICENSE Create LICENSE Jun 11, 2018
README.md Update README.md Jan 22, 2019


Docker Stars Docker Pulls


NxFilter - An easy to use DNS server with configurable filters and user controls.

This image is based on 1science/java for the slimmed down Java and overall container footprint.

Supported Tags


For a single persistent container:

docker run -it \
  --name nxfilter \
  -p 80:80 -p 443:443\
  -p 53:53/udp \

-it starts the container in Interactive mode with a TTY. -p forwards a port into the container, other ports are needed to utilize all features of nxfilter. 53 UDP is to accept DNS queries coming in, 80 is for the WebUI. The interactive console can be sent to the background with CTRL-P + CTRL-Q.

For a transient container with a persistent data volumes

docker run -dt \
  --name nxfilter \
  -v nxfilter-conf:/nxfilter/conf \
  -v nxfilter-log:/nxfilter/log \
  -v nxfilter-db:/nxfilter/db \
  -p 80:80 -p 443:443 -p 53:53/udp \
  -p 19002-19004:19002-19004 \

This will run the container in the background like a service, with a persistent data volume mounted for each folder that nxfilter modifies data in. Ports 80 and 53 are forwarded to the container for accessing NxFilter admin interface and accepting DNS queries. You may add --rm so the container will be removed after stopping. All changes will be saved in volumes.

To Do

  • Fully test running in an automated encironment like Shipyard or TravisCI


  • Create Docker file for both images. Shouldn't be too hard.
  • Set up automated builds of the images.
  • Finish testing automated builds and webhooks to completely automate the process.