Problem: A fully-specified IPv6 address entered into a field on a Domain Time II v5.x dialog is not parsed or saved correctly. The actual address used may appear truncated or have nodes missing.
This article applies to Domain Time II.
Last Updated: 9 March 2011
A fully-specified IPv6 address entered into a field on a Domain Time II v5.x dialog is not parsed or saved correctly. The actual address used may appear truncated or have nodes missing.
For example, using 2001:410:1:1:2a0:69ff:fe01:b0f4 will result in Domain Time trying to use address 2001:410:1:1:2a0:69ff or 2001:410:1:1:2a0:69ff:fe01 depending on the context.
Domain Time versions prior to 5.2.b.20110308 incorrectly parsed fully-qualified IPv6 addresses, using the last node of the address as the
port number to use for the connection (both IPv4 and IPv6 addresses allow :number to be appended to a numeric address to override the
default port number for a connection. IPv6 requires [address]:port, whereas IPv4 allows address:port).
Domain Time incorrectly assumed that any address that did not use a double-colon (::) must be an IPv4 address, and therefore interpreted the last colon to be specifying the connection port.
Upgrade to the latest version of Domain Time II.
If you are unable to upgrade immediately, you may use the following workarounds:
- IPv6 addresses using the double-colon notation do not have this problem. Specify the address with an elided node if possible, i.e. use 2001:db8:85a3::8a2e:370:7334 instead of 2001:db8:85a3:0:0:8a2e:370:7334.
- Specify a DNS name that resolves to the IPv6 address instead of using the address itself. The results returned from DNS lookup do not suffer the parsing error. To use a DNS name, your DNS server must return a valid address when queried.