The process to running DPS is basically the same for all platforms:
Download the latest release for your platform, if no binary available use the jar (requires JRE 19+)
Start DPS (you need to run as administrator/sudo so DPS can set itself as the default DNS)
sudo ./dns-proxy-server
Then you can solve from pre-configured entries (conf/config.json):
$ ping dps-sample.dev
PING dps-sample.dev (192.168.0.254) 56(84) bytes of data.
Also solve Docker containers*:
$ docker run --rm --hostname nginx.dev nginx
$ ping nginx.dev
PING nginx.dev (172.17.0.4) 56(84) bytes of data.
64 bytes from 172.17.0.4 (172.17.0.4): icmp_seq=1 ttl=64 time=0.043 ms
64 bytes from 172.17.0.4 (172.17.0.4): icmp_seq=2 ttl=64 time=0.022 ms
*Not supported on Windows
You probably want to check on specific running instructions to configure all DPS features when running on docker, set as default DNS and docker container solving have different docker run options for each platform.
Despite on this, the standalone way to run DPS on docker can be done by following:
$ docker run --rm --hostname dns.mageddo -p 5380:5380 -p 53:53/udp defreitas/dns-proxy-server
If you get something like 0.0.0.0:53: bind: address already in use then probably there is some other DNS server like
systemd-resolved, so you can try to bind DPS to a specific network interface like 127.0.0.1 or 192.168.x.x, check
your local interfaces for the best fit.
$ docker run --rm --hostname dns.mageddo -p 5380:5380 -p 127.0.0.1:53:53/udp defreitas/dns-proxy-server
Runining on docker limitations: