grimd

> 编程语言

Open source

:zap: fast dns proxy that can run anywhere, built to black-hole internet advertisements and malware servers

1.4K stars0 likes0 views

Website GitHub

About

:zap: fast dns proxy that can run anywhere, built to black-hole internet advertisements and malware servers

grimd

:zap: Fast dns proxy that can run anywhere, built to black-hole internet advertisements and malware servers.

Based on kenshinx/godns and miekg/dns.

Installation

go install github.com/looterz/grimd@latest

You can also download one of the releases or docker images. Detailed guides and resources can be found on the wiki.

Docker Installation

To quickly get grimd up and running with docker, run

bash

docker run -d -p 53:53/udp -p 53:53/tcp -p 8080:8080/tcp ghcr.io/looterz/grimd:latest

Alternatively, download the docker-compose.yml file and launch it using docker-compose.

docker-compose up -d

Configuration

If grimd.toml is not found, it will be generated for you, below is the default configuration.

…

Building

Requires golang 1.7 or higher, you build grimd like any other golang application, for example to build for linux x64

bash

env GOOS=linux GOARCH=amd64 go build -v github.com/looterz/grimd

Building Docker

Run container and test

bash

mkdir sources
docker build -t grimd:latest -f docker/Dockerfile . && \
docker run -v $PWD/sources:/sources --rm -it -P --name grimd-test grimd:latest --config /sources/grimd.toml --update

By default, if the program runs in a docker, it will automatically replace 127.0.0.1 in the default configuration with 0.0.0.0 to ensure that the API interface is available.

bash

curl -H "Accept: application/json" http://127.0.0.1:55006/application/active

Web API

A restful json api is exposed by default on the local interface, allowing you to build web applications that visualize requests, blocks and the cache. reaper is the default grimd web frontend.

If you want to enable the default dashboard, make sure the configuration file contains the following:

toml

dashboard = true

Speed

Incoming requests spawn a goroutine and are served concurrently, and the block cache resides in-memory to allow for rapid lookups, while answered queries are cached allowing grimd to serve thousands of queries at once while maintaining a memory footprint of under 15mb for 100,000 blocked domains!