I wasn't sure if this should go in ports or in installing because it is included with a base install. Anyway, the disclaimer---I've been searching online for the answer and found only a couple of things with the same issue, so I figure I'm missing something.
When installing, say on test vm, I choose to include unbound. I had expected it to work out of the box, but it seems, that at first, at least, I have to include another nameserver or unbound doesn't work--in other words, I install, then say, try to add rsync. I do pkg install rsync and it can't locate the pkg repos. If I then add a working nameserver, everything is fine. After awhile, I can comment out the second nameserver and just use unbound.
My question is, Is this normal? Or does unbound work for most people on first boot after install after running local-unbound-setup. If that is the case, what am I missing as far as necessary configuration?
When installing, say on test vm, I choose to include unbound. I had expected it to work out of the box, but it seems, that at first, at least, I have to include another nameserver or unbound doesn't work--in other words, I install, then say, try to add rsync. I do pkg install rsync and it can't locate the pkg repos. If I then add a working nameserver, everything is fine. After awhile, I can comment out the second nameserver and just use unbound.
My question is, Is this normal? Or does unbound work for most people on first boot after install after running local-unbound-setup. If that is the case, what am I missing as far as necessary configuration?
