General questions.
-
ummeegge
- Community Developer

- Posts: 5001
- Joined: October 9th, 2010, 10:00 am
Post
by ummeegge » November 2nd, 2018, 1:53 pm
Hi all,
fast feedback from here with the usage of TimB´s configuration but with a little more/other "forward-addr"s. dns-over-tls.conf looks currently like this:
Code: Select all
forward-zone:
name: "."
forward-addr: 94.130.110.185@853
forward-addr: 89.233.43.71@853
forward-addr: 158.64.1.29@853
forward-addr: 145.100.185.18@853
forward-addr: 146.185.167.43@853
forward-addr: 80.67.188.188@853
forward-addr: 199.58.81.218@853
forward-tls-upstream: yes
which works regularily nice/fast and stable but i´ve recognized that unbound decides infrequent to change back to port 53 and to jump out of the forward-zone. A
Code: Select all
unbound-control stop
unbound-control start
changes the config back to the the "forward-zone". Did someone have the same issue ?
Greetings,
UE
-
ummeegge
- Community Developer

- Posts: 5001
- Joined: October 9th, 2010, 10:00 am
Post
by ummeegge » November 15th, 2018, 6:29 pm
Hi all,
just a fast feedback to the before written from my side. The before described configuration for DOT is currently not usable for me since it shreds my host.cgi entries, it do not survives reboots and/or it possibly ends in a "local recursor" mode.
Try to find a little more feedback in the german section since it seems that in here is not that much further interest...
Best,
UE
-
blaatenator
- Posts: 1
- Joined: December 30th, 2018, 8:36 am
Post
by blaatenator » December 30th, 2018, 8:59 am
Got it working with TimB's solution as well. My first attempt was to try to forward DNS from unbound to a cloudflared (Argo) instance running on localhost:5353 (with no luck) but this is even better!