Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deploy Unbound as recursive server - Clarification #163

Open
cmonty14 opened this issue Feb 3, 2024 · 1 comment
Open

Deploy Unbound as recursive server - Clarification #163

cmonty14 opened this issue Feb 3, 2024 · 1 comment

Comments

@cmonty14
Copy link

cmonty14 commented Feb 3, 2024

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?

@MatthewVance
Copy link
Owner

I think so. You can see how I set it up as recursive in #120 (comment) and https://github.com/MatthewVance/unbound-docker/blob/master/unbound.conf.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants