I have no way of testing
IPv6, so not sure how to explain it.
I suggest you try
'unbound_manager' v2.05 with the updated
'unbound.conf' v1.02.
Clearly there is the
IPv6 'dns64' tweak so it may be that a directive in
'unbound.conf' is the culprit?
By design,
'i = Update' does just that, so (as explained on GitHub) you can add options, i.e. the
'i' doesn't remove
existing options.
To be honest, I don't even bother to REBOOT (between the hundred or so installs I've had to do) so using
Code:
A:Option ==> z
IMPORTANT: It is recommended to REBOOT in order to complete the removal of unbound
You will be asked to confirm BEFORE proceeding with the REBOOT
Press Y to REMOVE unbound or press [Enter] to CANCEL
Option ==> Y
then skipping the reboot, then (until
unbound is added to
amtm ) whilst it is tedious to manually retrieve the cURL installation command, it isn't too painful if you use the (advanced) shortcuts to reinstall unbound
e.g. only install unbound logging
Code:
e = Exit Script
A:Option ==> i 1
then later you can opt for the tuning tweak
Code:
e = Exit Script[/COLOR][/FONT][/LEFT]
[FONT=Georgia][COLOR=rgb(20, 20, 20)]
[LEFT]
A:Option ==> i 4
etc.
NOTE: As documented on Github, you can also specify
or
to save time by replying (or not) manually to the option prompts.