sure I'm happy to explain.
my customer's R81 ClusterXL is running multistack ipv4/ipv6.
I used to rise that concerns with R&D some year ago or so but killall wsdnsd is the only way to bring the name-resolution on multistack back to normal. otherwise you end up with Alerts all over the logs (CLM logging) and in terms of a need - well I'm well aware we've had such cases in the past but apparently it wasn't fixed nor DNS resolution due to the complexity of the design changed hence that process 2 time per day is the really a "work around" at the moment. That's all 🙂
That Gateway isn't used as proxy at all. It is a SG which uses both FWD DNS resolutions - IPv4 & IPv6 at the very same time but DNS servers supporting both back to the SG gives such errors (alerts) every day when only killing the wsdnsd helps for literally the period of 8h no more. 3 times a day killing that process (restarting effectively) helps to eliminate such huge hunger for logging saving a lot of space on the CLM.
Hope it clears up the situation mate.
J.
Jerry