| 1 |
Source: dnsproxy |
| 2 |
Section: net |
| 3 |
Priority: optional |
| 4 |
Maintainer: Marcos Talau <[email protected]> |
| 5 |
Build-Depends: |
| 6 |
debhelper-compat (= 13), |
| 7 |
groff-base, |
| 8 |
libevent-dev, |
| 9 |
Standards-Version: 4.6.2 |
| 10 |
Homepage: https://wolfermann.org/dnsproxy.html |
| 11 |
Vcs-Git: https://salsa.debian.org/debian/dnsproxy.git |
| 12 |
Vcs-Browser: https://salsa.debian.org/debian/dnsproxy |
| 13 |
Rules-Requires-Root: no |
| 14 |
|
| 15 |
Package: dnsproxy |
| 16 |
Architecture: any |
| 17 |
Depends: |
| 18 |
adduser, |
| 19 |
passwd, |
| 20 |
sysvinit-utils (>= 3.07-1), |
| 21 |
${misc:Depends}, |
| 22 |
${shlibs:Depends}, |
| 23 |
Pre-Depends: |
| 24 |
${misc:Pre-Depends}, |
| 25 |
Description: proxy for DNS queries |
| 26 |
dnsproxy forwards DNS queries to two previously configured nameservers: |
| 27 |
one for authoritative queries and another for recursive queries. |
| 28 |
The received answers are sent back to the client unchanged. |
| 29 |
No local caching is done. |
| 30 |
. |
| 31 |
Primary motivation for this project was the need to replace Bind servers with |
| 32 |
djbdns in an ISP environment. These servers get recursive queries from |
| 33 |
customers and authoritative queries from outside at the same IP address. |
| 34 |
Now it is possible to run dnscache and tinydns on the same machine with |
| 35 |
queries dispatched by dnsproxy. |
| 36 |
. |
| 37 |
Another possible scenario is a firewall where proxy queries should be |
| 38 |
forwarded to the real server in a DMZ. |