The unbound.conf.add is working great. Thank you.
I noticed that the added parameters do not appear in the unbound config but they are working. [emoji106]
Sent from my Pixel 4 XL using Tapatalk
I have to add the line to unbound config. I put in server section right under local port list described in this post. https://www.snbforums.com/index.php?posts/544318
I also have to add the line Dave mentions in the next post down.
I have 2 Plex servers on local lan. One only gets to internet...
I saw that earlier. I was just thinking that other items may change in the new version config that I may not want to overwrite. For the time, I will just stick to adding private-domain: "plex.direct" to the server section. It is no big deal really but I get yelled at if I forget :)
Doh.....well , I guess the files I just created will not work.....I was just thinking about how the config add lines were going to survive.
Sent from my Pixel 4 XL using Tapatalk
Is there a way to have a specific line always added to the unbound config every time it is built without a old config restore ? I ask this for the Plex local domain line.
Sent from my Pixel 4 XL using Tapatalk
I added the line with dnsmasq.conf.add. I then no longer have wan access from any device on the network. In my attempt to remove the line from dnsmasq.conf , I screwed something up because I lost all gui router access. I then wiped router and started fresh again.
I am a novice when it comes to...
I also run a Plex server that is on a machine not running through a VPN for wan. This one worked just fine with nothing added to unbound. Will these config changes mess it up ? Or should I add the config lines twice with both lan ip addresses ?
Sent from my Pixel 4 XL using Tapatalk
I have a Plex media server running on a machine that only gets to wan through a VPN. With unbound installed , I can no longer access Plex on local lan. If I go back to regular dns with dot , all access is normal again.vI suspect there is a way to make it all work but have no idea where to start...