TW
Interesting. Would you like to make a PR and fix this?
This issue tracker is about https://nsupdate.info/ software, not about the `nsupdate` commandline tool.
Glad to help! :-) Our docs for server installation are by far not complete and this is partly intended, because we do not want to document stuff that is not...
https://www.nsupdate.info/custom/site.html did you read that? Maybe solves your own-ns-updating issue.
You don't even need v6 yourself, just use the right way to enter the right v6 address into nsupdate.info instance, see URL.
your v6 addr is wrong. read the the text again at the url i gave. On December 22, 2019 3:08:04 PM GMT+01:00, abclution wrote: >Ok, yeah I figured that part...
ping6 works: ``` (env) nsupdate@web:~$ ping6 64:ff9b::46.4.91.85 PING 64:ff9b::46.4.91.85(64:ff9b::2e04:5b55) 56 data bytes 64 bytes from 64:ff9b::2e04:5b55: icmp_seq=1 ttl=57 time=3.53 ms ```
OK, so this is not really in the scope of nsupdate-info docs, it is bind docs. Can you find it there? We could maybe add some links to the relevant...
As you already noted: the "embed v4 in v6" address part is specific to that server, it is not generally true for the software. So make sure this is made...
Guess we can close this?