You may come across a problem where after adding ipV6 address to DNS, MW-DISP replication stops working.
Reviewing the trace log (when 'set trace=all;') is enabled, you will see something similar to what is outlined below as an example.
e.g. dsa_1_name DSA will report the following:
?  20221017.093902.478 WARN : Entry 'dsa_2_name x -1' not found in DISP file
*  20221017.093902.479 DSA_W2650 Cannot get Multiwrite last update time for 'dsa_2_name'
!  Send MW-DISP Bind request
!  Creating Bind request
>  -> #10000029 [dsa_2_name] MWDISP BIND-REQ
>  invoke-id = 0 credit = -5
>  User:
>  <countryName "US">
>  <commonName "dsa_1_name">
>  Password: (masked)
>  Remote address:
>  psap = "$MWDISP$"
>  nsap = [2610:30:201c:791:0:0:0:99]:22235
!  Connecting to TCP [2610:30:201c:791:0:0:0:99]:22235
?  20221017.093902.479 WARN : comms_recv: Connection refused
Release : 14.1
Even though ipV6 protocol is supported there is a change required for this to work.
There are two options:
1) Do not use ipV6 protocol. i.e. remove it from your DNS.
2) Modify the KNOWLEDGE .dxc file where you currently may have 'tcp' or 'ipv4' defined in "address" line , to explicitly add 'ipv6' in the same line and restart the DSAs.
e.g. you may have one of the following in all KNOWLEDGE .dxc files.
address = tcp "hostname or ip" port 19389
address = ipv4 "hostname or ip" port 19389
Change the above to:
address = tcp "hostname or ip" port 19389, ipv6 "hostname or ip" port 19389
address = ipv4 "hostname or ip" port 19389, ipv6 "hostname or ip" port 19389
Once done, restart all DSAs and after that MW-DISP replication will work over ipV6 protocol as well.