This is really not that important because at this rate I'll be dead before IPV6 really takes off. Anyway, for years we've had an unbound caching DNS server working flawlessly for our network. I thought maybe it would be worth future proofing it and running it on IPV6 as well.
Maybe this is more of a general IPV6 question than an Unbound question: For those interfaces on your DNS server that only face the LAN what type of IPV6 address do you have the listen on? The interfaces facing my LANs don't have to go out to the internet, they just have to service DNS for my lan clients, while the interface facing the internet though obviously will need a global unicast address. Those who have set up unbound in IPV6, do you have the interfaces on your lan side listening on just their link local address? Their global unicast address? Or both? I tried searching for a couple hours to find the best practice on this but couldn't really find a straight answer.
Thank you in advance!
Maybe this is more of a general IPV6 question than an Unbound question: For those interfaces on your DNS server that only face the LAN what type of IPV6 address do you have the listen on? The interfaces facing my LANs don't have to go out to the internet, they just have to service DNS for my lan clients, while the interface facing the internet though obviously will need a global unicast address. Those who have set up unbound in IPV6, do you have the interfaces on your lan side listening on just their link local address? Their global unicast address? Or both? I tried searching for a couple hours to find the best practice on this but couldn't really find a straight answer.
Thank you in advance!