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.

Sign up for GitHub

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

Jump to bottom

Unbound Stopped #1

Closed
wandersonwhcr opened this issue Oct 27, 2021 · 1 comment · Fixed by #4
Closed

Unbound Stopped #1

wandersonwhcr opened this issue Oct 27, 2021 · 1 comment · Fixed by #4

Comments

@wandersonwhcr
Copy link
Owner

wandersonwhcr commented Oct 27, 2021 •
edited
Loading

After a lack of energy my RPi restarted.

Unbound was not started on system initialization. I think that happened because of unbound priority on system startup.

And because we configured resolv.conf to use local unbound, apt-get upgrade on ansible playbook threw an error and stopped before systemctl start unbound task.
@wandersonwhcr
Copy link
Owner Author

wandersonwhcr commented Oct 28, 2021 •
edited
Loading

https://bugzilla.redhat.com/show_bug.cgi?id=1343126
https://nlnetlabs.nl/documentation/unbound/unbound.conf/#ip-freebind

@wandersonwhcr wandersonwhcr linked a pull request Oct 30, 2021 that will close this issue
Execute unbound after network is online #4
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Execute unbound after network is online wandersonwhcr/rpi-dns-home
1 participant
@wandersonwhcr