The main issue that bind doesrCOt provide an authentication method. So in
any case you somehow should manage the access to the DNS server vice
versa it will became open resolver and will be used for DDoS attacks.
On May 10, 2020, at 23:26, Daniel Stirnimann <daniel.stirnimann@switch.ch> wrote:
On 11.05.20 08:18, Vadim Pavlov via bind-users wrote:
The main issue that bind doesrCOt provide an authentication method. So in
any case you somehow should manage the access to the DNS server vice
versa it will became open resolver and will be used for DDoS attacks.
If you were to use DoH, you could use Basic Authentication. The DoH URL
you could configure on your client systems could be something like this:
https://username:password@doh.example.com/dns-query
Daniel--- Synchronet 3.21d-Linux NewsLink 1.2
Am 11.05.20 um 06:14 schrieb Blason R:
I am seeking solution for our below problem and wanted to know if any
open source option can help us here?
We have our internal DNS RPZ firewall built on BIND9. Due to the current situation since all users are working from home we are not able to route their queries to internal DNS servers. Well, when they are on VPN definitely queries are then passed through internal DNS server but they left open when not connected to VPN.
Is there any solution using -
* API by which we can route the queries for user who are on Internet
* Or any client utility which can be installed on user's
desktop/laptop where we can embed our BIND RPZ server and then route
the queries to internal one using NAT?
* Or any other alternative community can suggest?
when you are in the position to use something like this you can also
tell your users they have to configure their machines for using a public
dns you are hosting and you are done
On 11.05.20 08:18, Vadim Pavlov via bind-users wrote:d. So in
The main issue that bind does=E2=80=99t provide an authentication metho=
any case you somehow should manage the access to the DNS server vice
versa it will became open resolver and will be used for DDoS attacks.
If you were to use DoH, you could use Basic Authentication. The DoH URL
you could configure on your client systems could be something like this:
https://username:password@doh.example.com/dns-query
Daniel
Hmm- Any docs on configuring DOH Proxy?
On Mon, May 11, 2020 at 11:56 AM Daniel Stirnimann < daniel.stirnimann@switch.ch> wrote:
On 11.05.20 08:18, Vadim Pavlov via bind-users wrote:
The main issue that bind does=E2=80=99t provide an authentication meth= od. So in
any case you somehow should manage the access to the DNS server vice
versa it will became open resolver and will be used for DDoS attacks.
If you were to use DoH, you could use Basic Authentication. The DoH URL
you could configure on your client systems could be something like this:
https://username:password@doh.example.com/dns-query
Daniel
I am seeking solution for our below problem and wanted to know if any
open source option can help us here?
We have our internal DNS RPZ firewall built on BIND9. Due to the current situation since all users are working from home we are not able to route their queries to internal DNS servers. Well, when they are on VPN
definitely queries are then passed through internal DNS server but they
left open when not connected to VPN.
Is there any solution using -
* API by which we can route the queries for user who are on Internet
* Or any client utility which can be installed on user's
desktop/laptop where we can embed our BIND RPZ server and then route
the queries to internal one using NAT?
* Or any other alternative community can suggest?
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 65 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 03:50:30 |
| Calls: | 862 |
| Files: | 1,311 |
| D/L today: |
673 files (6,429M bytes) |
| Messages: | 264,528 |