Skip to content
This repository has been archived by the owner on Jul 16, 2023. It is now read-only.

Unbound should always be enabled #15

Closed
pvandervelde opened this issue Feb 5, 2018 · 0 comments
Closed

Unbound should always be enabled #15

pvandervelde opened this issue Feb 5, 2018 · 0 comments
Assignees
@pvandervelde
Labels
bug
Projects
base.linux - backlog
Milestone
0.2.0

Comments

@pvandervelde
Copy link
Member

Because enabling unbound during a Packer run is error prone for some reason.
@pvandervelde pvandervelde added this to the 0.2.0 milestone Feb 5, 2018
@pvandervelde pvandervelde self-assigned this Feb 5, 2018
@pvandervelde pvandervelde added this to InProgress in base.linux - backlog Feb 6, 2018
pvandervelde added a commit that referenced this issue Feb 6, 2018
@pvandervelde
Always have unbound enabled and have a default empty unbound_zones.co…
18a5bf7 
…nf file. This way we can simply replace the

zones file and restart which should be less troublesome than trying to enable, start and then disable unbound.

references #15
@pvandervelde pvandervelde moved this from InProgress to Release in base.linux - backlog Mar 7, 2018
@pvandervelde pvandervelde moved this from Release to Done in base.linux - backlog Mar 7, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@pvandervelde pvandervelde

Labels
bug
Projects
base.linux - backlog
  
Done
Milestone
0.2.0
Development

No branches or pull requests
1 participant
@pvandervelde