Monday, August 1, 2022
HomeHackerDNSd - Passive-Recursive DNS Daemon

DNSd – Passive-Recursive DNS Daemon




Passive-Recursive DNS daemon.

Quickstart

nameserver 127.0.0.1 | sudo tee /and many others/resolv.conf dig google.com dig -x $(dig +quick google.com)”>

go get github.com/korc/PR-DNSd
sudo setcap cap_net_bind_service,cap_sys_chroot=ep go/bin/PR-DNSd
go/bin/PR-DNSd -upstream 9.9.9.9:53 -listen 127.0.0.1:53
echo nameserver 127.0.0.1 | sudo tee /and many others/resolv.conf
dig google.com
dig -x $(dig +quick google.com)

If you cannot use setcap, you need to use -chroot "" and -listen :<high_port> choices, or run as root.

Use circumstances

Working as your individual personal server for Android9’s Non-public DNS settings

After acceptable setcap, run:

PR-DNSd -tlslisten :853 -cert YOUR_SERVER_CRT_KEY_PEM -upstream 1.1.1.1:53 -store pr-dnsd

Choices

-cert string
TCP-TLS listener certificates (required for tls listener)
-chroot string
chroot to listing after begin (default "/var/tmp")
-count int
Rely of replies allowed earlier than debounce delay is utilized (default 100)
-ctmout string
Shopper timeout for upstream queries
-debounce string
Required time period between UDP replies to single IP to stop DoS (default "200ms")
-key string
TCP-TLS certificates key (default similar as -cert worth)
-listen string
hear deal with (default ":53")
-silent
Do not report regular knowledge
-store string
Retailer PTR knowledge to specified file
-tlslisten string
TCP-TLS listener deal with (default ":853")
-upstream string
upstream DNS serv er (tcp-tls:// prefix for DoT) (default "1.1.1.1:53")
(with tls and chroot, guarantee ca-certificates and resolv.conf in chroot are correctly arrange)



RELATED ARTICLES

LEAVE A REPLY

Please enter your comment!
Please enter your name here

- Advertisment -
Google search engine

Most Popular

Recent Comments