Over the last couple of BorderManager 3.8 service packs (notably 4 & 5)
I have noticed that we are having issues with DNS records getting
Specifically noticed mx records, and more specifically, it appears to
occur when some of the records are bumped down the priority list, and
new records are set at a higher priority.

To resolve the situation I need to unload the proxy and do a
proxy -cc

BorderManager 3.8sp5,
sitting on NW65sp6 + mm65sp6 + nwlib6j

Any suggestions on a resolution?