New TCP High Water setting looks incorrect on a newly-started server

Quoting verbatim from Support ticket #15820:

Our operations noticed high tcp high-water counter after named come up

version: BIND 9.11.13-S1 (Supported Preview Version) <id:2fa124e> (version.bind/txt/ch disabled)
running on <<hostname redacted>>: SunOS sun4v 5.10 Generic_147440-09
boot time: Mon, 25 Nov 2019 19:23:03 GMT
last configured: Mon, 25 Nov 2019 19:23:03 GMT
configuration file: <<path redacted>>/etc/named.conf
CPUs found: 16
worker threads: 12
UDP listeners per interface: 12
number of zones: 133 (71 automatic)
debug level: 0
xfers running: 0
xfers deferred: 0
soa queries in progress: 0
query logging is OFF
recursive clients: 0/6900/7000
tcp clients: 7/100
TCP high-water: 4299804416
server is up and running


to my understanding, this TCP high-water is a counter to keep historically highest simultaneous TCP connections. This high setting does not make sense for a server just starting up. Is it possible it's an uninitialized counter? Since the counter does not update unless there is higher value, an unusually high setting render the feature useless.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information