Deploy Unbound as recursive server - Clarification

[cmonty14]

Hi, I want to deploy Unbound as a recursive server; this is recommended in Rspamd documenation: Therefore, it is strongly advised to employ your own recursive resolver when using Rspamd or any other email-related technology. Our recommended choice is to set up Unbound or, for more advanced setups, the Knot Resolver. You can find basic setup information for Unbound here.

According to documentation the configuration must be different compared to default deployment.

Comparing the config provided by unbound.sh with this example file there's basically this section missing:

    ###########################################################################
    # FORWARD ZONE
    ###########################################################################

    include: /opt/unbound/etc/unbound/forward-records.conf

Is it correct that only this section makes the difference of forwarding (default) vs. recursive?

[agittins]

This query is about configuring unbound, so it does not pertain to the docker-mailserver project. I suggest you raise this in the proper support channels for unbound (or MatthewVance's container for it).

[jeboehm]

I've already added unbound to the Kubernetes Helm charts and will add unbound as a default in an upcoming release.

[jeboehm]

unbound is part of docker-mailserver as of 6.0