Unbound with nspawn #611
Unanswered
jasonhollis
asked this question in
Q&A
Replies: 1 comment
-
I have not used unbound, but cant you just install it in the container?
Or am I misunderstanding your question? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have the nsspawn core container setup and running fine. I have used simple networking e.g. it looks like my custom-delian is connected to all of the interfaces on the DMP-SE. hostname -I gives me: 203.XXX.XXX.XXX 192.168.90.1 192.168.90.2 192.168.3.1 2404:XXX:XXX This make sense to me in these are the external an internal addresses of the UDMP-SE the 3.1 address I guess is a new network that was spawned for the containers? I'm not sure why I would want to run a seperate VLAN and address space for the containers on the UDMP-SE or MAC-VLAN. All I really want to do is run Unbound via nsspawn on the UDMP-SE. I don't want or need pi-hole because I'm already running NextDNS. I just want Unbound running locally pointed upstream to NextDNS. I'm pretty bogged down at this point trying to figure out how to make this happen?
Beta Was this translation helpful? Give feedback.
All reactions