bring back resolvconf and unbound DNS

bd9c664b1a tried to remove it and use
the system resolver. However, we found that debian has a quirk that it adds
it adds the fqdn as 127.0.1.1. This means that the docker containers
resolve the my.example.com domain to that and can't connect.

This affects any apps doing a turn test (CLOUDRON_TURN/STUN_SERVER)
and also apps like SOGo which use the mail server hostname directly (since
they require proper certs).

https://www.debian.org/doc/manuals/debian-reference/ch05.en.html#_the_hostname_resolution

So, the solution is to go back to unbound, now that port 53 binding is specially
handled anyway in docker.js

This commit is contained in:

Girish Ramakrishnan

2020-11-25 10:02:43 -08:00

parent 25cc60e648

commit e511b70d8f

9 changed files with 39 additions and 16 deletions

setup/start/unbound.conf

+1 -1

View File

@@ -1,5 +1,5 @@
 server:
         port: 533
         port: 53
         interface: 127.0.0.1
         interface: 172.18.0.1
         do-ip6: no